vania-janet/multiturn-rag-retrieval-data huggingface dataset:
tags: "<tags>"
encrypted: <true_or_false>
resourceGroup: "<resource_group>"
data
encryptionKey: <encryption_key>

name
: Enter a name for your Kubernetes secret.

namespace
: Enter the namespace where you want to create your secret. To reference the secret in your PVC, the PVC must be created in the same namespace.

iops
: In the string data section, enter the range of IOPS that you want to allow for your Block Storage for Classic instance. The range that you enter must match the Block Storage for VPC tier that you plan to use.

zone
: In the string data section, enter the VPC zone where you want to create the Block Storage for Classic instance. Make sure that you use a zone that your worker nodes are connected to. To list VPC zones that your worker nodes use, run ibmcloud oc cluster get --cluster <cluster_name_or_ID> and look at the Worker Zones field in your CLI output. If you don't specify a zone, one of the worker node zones is automatically selected for your Block Storage for Classic instance.

tags
: In the string data section, enter a comma-separated list of tags to use when the PVC is created. Tags can help you find your storage instance after it is created.

resourceGroup
: In the string data section, enter the resource group that you want your Block Storage for Classic instance to get access to. If you don't enter a resource group, the instance is automatically authorized to access resources of the resource group that your cluster belongs to.

encrypted
: In the string data section, enter true to create a secret that sets up encryption for Block Storage for Classic volumes. If you set this option to true, you must provide the root key CRN of your Key Protect service instance that you want to use in parameters.encryptionKey.
Click the storage configuration that you want to assign to a cluster group.
5. On the Configuration details page, click Create storage assignment.
6. In the Create an assignment pane, enter a name for your assignment.
7. From the Version drop-down list, select the storage configuration version that you want to assign.
8. From the Cluster group drop-down list, select the cluster group that you want to assign to the storage configuration. Note that the clusters in your cluster group where you want to assign storage must all be in the same Satellite location.
9. Click Create to create the assignment.
10. Verify that your storage configuration is deployed to your cluster.



1. From the [Satellite console](https://cloud.ibm.com/satellite/locations), navigate to your Location and select Storage
2. Click the storage configuration that you created and review the Assignments tab.
3. Click the Assignment that you created and review the Rollout status for your configuration.









 Creating an assignment in the CLI 



1. List your storage configurations and make a note of the storage configuration that you want to assign to your clusters.

ibmcloud sat storage config ls
2. Get the ID of the cluster, cluster group, or service that you want to assign storage to.

To make sure that your cluster is registered with Satellite Config or to create groups, see [Setting up clusters to use with Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig).

Example command to list cluster groups.

ibmcloud sat group ls

Example command to list clusters.

ibmcloud oc cluster ls --provider satellite

Example command to list Satellite services.

ibmcloud sat service ls --location <location>
3. Assign your storage configuration to the cluster, group, or service that you retrieved earlier.
When you initiate cluster management actions, such as running ibmcloud ks commands, basic information about the cluster such as name, ID, user, the command is routed through a regional endpoint and the global endpoint.





 Resources in a multizone cluster 

In a multizone cluster, your cluster's resources are spread across multiple zones for higher availability.

Worker nodes are spread across multiple zones in the metro location to provide more availability for your cluster. The Kubernetes master replicas are also spread across zones. When you initiate local container orchestration actions, such as kubectl commands, the information is exchanged between your master and worker nodes through the global endpoint.

Other cluster resources, such as storage, networking, compute, or apps running in pods, vary in how they deploy to the zones in your multizone cluster. For more information, review these topics:



* Setting up [file storage](https://cloud.ibm.com/docs/containers?topic=containers-file_storageadd_file) and [block storage](https://cloud.ibm.com/docs/containers?topic=containers-block_storageadd_block) in multizone clusters, or [choosing a multizone persistent storage solution](https://cloud.ibm.com/docs/containers?topic=containers-storage-plan).
* [Enabling public or private access to an app by using a network load balancer (NLB) service in a multizone cluster](https://cloud.ibm.com/docs/containers?topic=containers-loadbalancermulti_zone_config).
* [Managing network traffic by using Ingress](https://cloud.ibm.com/docs/containers?topic=containers-managed-ingress-about).
* [Increasing the availability of your app](https://cloud.ibm.com/docs/containers?topic=containers-app).
containers-kubernetes.storage-volume.delete A volume is deleted. 
 containers-kubernetes.storage-volume.list Volumes in the IBM Cloud account or as filtered by provider are retrieved. 
 containers-kubernetes.storage-volume.read A volume is retrieved 
 containers-kubernetes.storage-volume.update A volume is updated. 
 containers-kubernetes.storage-attachment.create A volume attachment is created. 
 containers-kubernetes.storage-attachment.delete A volume attachment is deleted. 
 containers-kubernetes.storage-attachment.list Volume attachments are retrieved. 
 containers-kubernetes.storage-attachment.read A volume attachment is retrieved. 







 Worker node and worker pool events 

The following list of worker node and worker pool events are sent to IBM Cloud Activity Tracker.



Worker node and worker pool events

 Action Description 

 containers-kubernetes.cluster-worker.add A worker node is added to the cluster. Note: Adding stand-alone worker nodes is deprecated. 
 containers-kubernetes.cluster-worker.list The worker nodes for a cluster are listed. 
 containers-kubernetes.cluster-worker-pool.create A worker pool is created in the cluster. 
 containers-kubernetes.cluster-worker-pool.delete A worker pool is deleted from a cluster. 
 containers-kubernetes.cluster-worker-pool.get The details of a worker pool in the cluster are returned. 
 containers-kubernetes.cluster-worker-pool.list The worker pools for a cluster are listed. 
 containers-kubernetes.cluster-worker-pool.rebalance A worker pool is rebalanced. 
 containers-kubernetes.cluster-worker-pool.resize A worker pool is resized, to add or decrease the number of worker nodes in the pool. 
 containers-kubernetes.cluster-worker-pool-autoscale.disable Autoscaling the worker pool is disabled. 
 containers-kubernetes.cluster-worker-pool-autoscale.enable Autoscaling the worker pool is enabled.
* [Deploying](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-deploying)
* [Normal](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-normal)
* [Pending](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-pending)
* [Requested](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-requested)
* [Updating](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-updating)
* [Unsupported](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-unsupported)
* [Warning](https://cloud.ibm.com/docs/containers?topic=containers-cluster-states-referencecluster-state-warning)



[Debugging common CLI issues with clusters](https://cloud.ibm.com/docs/containers?topic=containers-ts_clists_clis)



* [Firewall prevents running CLI commands](https://cloud.ibm.com/docs/containers?topic=containers-ts_clists_firewall_clis)
* [kubectl commands don't work](https://cloud.ibm.com/docs/containers?topic=containers-ts_cliskubectl_fails)
* [kubectl commands time out](https://cloud.ibm.com/docs/containers?topic=containers-ts_clisexec_logs_fail)



[Why can't I create or delete clusters or worker nodes?](https://cloud.ibm.com/docs/containers?topic=containers-cluster_infra_errorscluster_infra_errors)
Verify that storage configuration and service cluster both must be on same Satellite location, if not create a configuration and then retry.





 ST0009 error message 

CLUSTER-ID cluster is not a service Satellite cluster.

Error type: Bad request

Response code: 400

How to fix it: Verify your service clusters by running ibmcloud sat services --location <location-ID> command.





 ST0010 error message 

User doesn't have access to perform this operation.

Error type: Authorization,

How to fix it: login as location or service admin and then perform this operation,

Response code: 400





 ST0013 error message 

The cluster ID is not specified in the query. To list cluster IDs, run ibmcloud ks cluster ls.

Error type: General,

Response code: 400





 ST0014 error message 

The required input parameter PARAMETER in the request body is either missing or unsupported. The specified value is PARAMETER. The expected value(s) is(are) VALUE.

Error type: Bad request

Response code: 404





 ST0015 error message 

The required input parameter PARAMETER-NAME in the request body is missing.

Error type: Bad request

Response code: 404





 ST0016 error message 

Failed to update the tags for the volume with CRN VOLUMECRN. BackendError: BACKEND-ERROR

Error type: Services

Response code: 400





 ST0017 error message 

Failed to retrieve resource details.

Error type: Services

Response code: 400





 ST0018 error message 

Result limit reached.

Error type: Services

Response code: 404





 ST0019 error message 

OBJECT-TYPE not found with the identifier: IDENTIFIER.

Error type: Services

Response code: 404





 ST0020 error message 

The request parameter with name PARAMETER-NAME is not supported.

Error type: Services

Response code: 404





 ST0021 error message 

OBJECT-TYPE with the identifier OBJECT-IDENTIFIER already exists.

Error type: Services

Response code: 404





 ST0022 error message
Related links 



* [Procedure to order Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_orderinginstance-order-procedure)
* [Adding clusters to Cyber Recovery instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_addingclusters)
* [Adding ESXi servers to Cyber Recovery instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_addingservers)
* [Deleting Cyber Recovery instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_deletinginstance)
: Updated getting started and task topics for the updated process for the [Kubernetes cluster creation console](https://cloud.ibm.com/kubernetes/catalog/create).





 24 July 2020 

Minimum cluster size
: Added an FAQ about [the smallest size cluster that you can make](https://cloud.ibm.com/docs/containers?topic=containers-faqssmallest_cluster).

Versions
: Master fix pack update change log documentation is available.
: Kubernetes version [1.18.6_1522](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog1186_1522), [1.17.9_1534](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog1179_1534), [1.16.13_1541](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog11613_1541), and [1.15.12_1548](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog11512_1548).

Worker node replacement
: Added a troubleshooting topic for when [replacing a worker node does not create a worker node](https://cloud.ibm.com/docs/containers?topic=containers-auto-rebalance-off).





 20 July 2020 

Master versions
: Master fix pack update change log documentation is available.
[Kubernetes labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) are key:value pairs that can be used as selectors for the resources that are in your cluster, such as [adding a label to worker pool](https://cloud.ibm.com/docs/containers?topic=containers-add_workersworker_pool_labels) to [deploy an app to only certain worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-deploy_appnode_affinity). Tags are an IBM Cloud tool that you can use to filter your IBM Cloud resources, such as clusters, storage devices, or Watson services.

Do not include personal information in your tags. Learn more about [securing your personal information](https://cloud.ibm.com/docs/containers?topic=containers-securitypi) when you work with Kubernetes resources.

Choose among the following options:



* [Create a cluster in the console](https://cloud.ibm.com/docs/containers?topic=containers-clusters) with a tag. You can't create a cluster with a tag in the CLI.
* Add tags to an existing cluster in the console or CLI.





 Adding tags to clusters with the console 



1. Log in to the [IBM Cloud clusters console](https://cloud.ibm.com/kubernetes/clusters).
2. Select a cluster with existing tags.
3. Next to the cluster name and status, click the Edit tags pencil icon. If your cluster does not have any existing tags, you don't have an Edit tags pencil icon. Instead, use the [resource list](https://cloud.ibm.com/docs/account?topic=account-tag) or CLI.
4. Enter the tag that you want to add to your cluster. To assign a key-value pair, use a colon such as costctr:1234.







 Adding tags to clusters with the CLI 



1.
kubectl get ocscluster

Example output:

NAME AGE
ocscluster-vpc 71d
2. Describe the storage cluster and review the Events section of the output for any error messages.

kubectl describe ocscluster <ocscluster-name>
3. List the pods in the kube-system namespace and verify that they are Running.

kubectl get pods -n kube-system
4. Describe the ibm-ocs-operator-controller-manager pod and review the Events section in the output for any error messages.

kubectl describe pod <ibm-ocs-operator-controller-manager-a1a1a1a> -n kube-system
5. Review the logs of the ibm-ocs-operator-controller-manager.

kubectl logs <ibm-ocs-operator-controller-manager-a1a1a1a> -n kube-system
6. Describe NooBaa and review the Events section of the output for any error messages.

kubectl describe noobaa -n openshift-storage
* [What if I want to set up multiple clusters across regions?](https://cloud.ibm.com/docs/containers?topic=containers-ha_clustersmultiple-regions-setup)
* [What options do I have to load balance workloads across multiple clusters?](https://cloud.ibm.com/docs/containers?topic=containers-ha_clustersmultiple-cluster-lb-options)
* [Setting up a CIS global load balancer](https://cloud.ibm.com/docs/containers?topic=containers-ha_clusterscis-global-lb-setup)
* [Setting up your own global load balancer](https://cloud.ibm.com/docs/containers?topic=containers-ha_clustersbyo-global-lb-setup)
* [What if I want to load balance workloads on the private network?](https://cloud.ibm.com/docs/containers?topic=containers-ha_clustersglb-private)





[Planning your worker node setup](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodesplanning_worker_nodes)



* [Available hardware for worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodesshared_dedicated_node)



* [What flavors are available to me?](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodesavailable-flavors)
* [Can I combine different flavors in a cluster?](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodescombine-flavors)
* [How can I change worker node flavors?](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodeschange-flavors)
* [Are the worker nodes encrypted?]
allowVolumeExpansion: true
Show more
4. Create the storage class in your cluster.

oc apply -f sc.yaml
5. Verify that the storage class is created.

oc get sc
6. Create a PVC that references the storage class that you created earlier.

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: demo-pvc-file
spec:
volumeMode: Filesystem
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
storageClassName: demo-storageclass
7. Create the PVC in your cluster.

oc apply -f pvc.yaml
8. Verify that the PVC is created and the status is Bound.

oc get pvc
9. Create a YAML configuration file for a stateful set that mounts the PVC that you created.

kind: StatefulSet
apiVersion: apps/v1
metadata:
name: demo-statefulset-file-system
spec:
selector:
matchLabels:
app: demo-statefulset
serviceName: demo-statefulset
replicas: 1
template:
metadata:
labels:
app: demo-statefulset
spec:
containers:
- name: demo-container
image: registry.access.redhat.com/ubi8/ubi:latest
command: [ "/bin/sh", "-c", "--" ]
args: [ "while true; do sleep 30; done;" ]
volumeMounts:
- name: demo-volume-file-system
mountPath: "/data"
volumes:
- name: demo-volume-file-system
persistentVolumeClaim:
claimName: demo-pvc-file
Show more
10. Create the pod in your cluster.

oc apply -f <stateful-set>.yaml
11.
* [Subscription service access roles](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-service-accessservice-access-subscription)
* [Cluster service access roles](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-service-accessservice-access-cluster)
* [Cluster group service access roles](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-service-accessservice-access-cluster-grp)
* [Resources service access roles](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-service-accessservice-access-cluster-roles)



[API keys in IBM Cloud](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-api-keyiam-api-key)



* [Satellite API key](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-api-keyapi-key-satellite)
* [Container service API key](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-api-keyapi-keys-containers)
* [Infrastructure provider credentials](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-api-keyapi-keys-templates)



[Common permissions in other cloud providers](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-commoniam-common)



* [AWS permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-commonpermissions-aws)



* [Manually creating a Satellite location in AWS](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-commonpermissions-aws-manual)
Example context-based restrictions scenarios 

With context-based restrictions, account owners and administrators can define and enforce access restrictions for IBM Cloud® resources, based on the context of access requests. Access to IBM Cloud Kubernetes Service resources can be controlled with context-based restrictions and identity and access management policies. For more information, see [Protecting IBM Cloud Kubernetes Service resources with context-based restrictions](https://cloud.ibm.com/docs/containers?topic=containers-cbr).

Applications running on IBM Cloud Kubernetes Service clusters, for example web servers exposed by a Kubernetes LoadBalancer, are not restricted by CBR rules.



 Understanding the scenario 

In this example scenario, you use context-based restrictions to restrict traffic to your cluster by allowing only an individual IP address to connect to the cluster APIs over the public network while still allowing all private traffic.

In the following steps, you start by creating a network zone, or allowlist, that includes a single IP address. Then, you create a context-based restrictions rule for your cluster that allows all private network access and allowlists the network zone that contains the individual IP address. When you create the rule, you associate it with the network zone that contains the individual IP address.





 Prerequisites 

Before beginning this tutorial, make sure you have created or installed the following resources and tools.



* An IBM Cloud account. For more information, see [Creating an account](https://cloud.ibm.com/docs/account?topic=account-account-getting-started).
* The CLI tools including the IBM Cloud CLI, the Containers service CLI plug-in, and the CBR plug-in. For more information, see [Getting started with the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).
* An IBM Cloud Kubernetes Service cluster. For more information, see [Creating clusters](https://cloud.ibm.com/docs/containers?topic=containers-clusters).
* [IBM Cloud service creation](https://cloud.ibm.com/kubernetes/landing)
* [Documentation](https://cloud.ibm.com/docs/containers)



* [Benefits and service offerings](https://cloud.ibm.com/docs/containers?topic=containers-cs_ov)
* [Learning path for administrators](https://cloud.ibm.com/docs/containers?topic=containers-learning-path-admin)
* [Learning path for developers](https://cloud.ibm.com/docs/containers?topic=containers-learning-path-dev)
* [Tutorial library](https://cloud.ibm.com/docs/openshift?topic=openshift-learning-path-dev)



* Application migration resources



* [Moving your environment to the IBM Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-strategy)
* [How to Migrate Cloud Foundry Applications to Docker Containers on a Kubernetes Cluster](https://www.ibm.com/cloud/blog/migrate-cloud-foundry-applications-to-docker-containers-on-a-kubernetes-cluster)
* [Kubernetes for CloudFoundry users](https://cloudnative101.dev/electives/cf-to-k8s)
* [Migrating Cloud Foundry applications to IBM Kubernetes Service](https://cloudnative101.dev/electives/cf-to-k8s/iks-migration)
* [Slack](https://cloud.ibm.com/kubernetes/slack)
3. Click the Locations tab, then click Storage.
4. Click the storage configuration that you want to assign to a cluster group.
5. On the Configuration details page, click Create storage assignment.
6. In the Create an assignment pane, enter a name for your assignment.
7. From the Version drop-down list, select the storage configuration version that you want to assign.
8. From the Cluster group drop-down list, select the cluster group that you want to assign to the storage configuration. Note that the clusters in your cluster group where you want to assign storage must all be in the same Satellite location.
9. Click Create to create the assignment.
10. Verify that your storage configuration is deployed to your cluster.



1. From the [Satellite console](https://cloud.ibm.com/satellite/locations), navigate to your Location and select Storage
2. Click the storage configuration that you created and review the Assignments tab.
3. Click the Assignment that you created and review the Rollout status for your configuration.









 Creating an assignment in the CLI 



1. List your storage configurations and make a note of the storage configuration that you want to assign to your clusters.

ibmcloud sat storage config ls
2. Get the ID of the cluster, cluster group, or service that you want to assign storage to.

To make sure that your cluster is registered with Satellite Config or to create groups, see [Setting up clusters to use with Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig).

Example command to list cluster groups.

ibmcloud sat group ls

Example command to list clusters.

ibmcloud oc cluster ls --provider satellite

Example command to list Satellite services.

ibmcloud sat service ls --location <location>
3. Assign your storage configuration to the cluster, group, or service that you retrieved earlier.