vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Limitations](https://cloud.ibm.com/docs/containers?topic=containers-cbrcbr-limitations)



[Example context-based restrictions scenarios](https://cloud.ibm.com/docs/containers?topic=containers-cbr-tutorialcbr-tutorial)



* [Understanding the scenario](https://cloud.ibm.com/docs/containers?topic=containers-cbr-tutorialcbr-tutorial-scenario)
* [Prerequisites](https://cloud.ibm.com/docs/containers?topic=containers-cbr-tutorialcbr-tutorial-prereqs)
* [Creating your network zone](https://cloud.ibm.com/docs/containers?topic=containers-cbr-tutorialcbr-tutorial-create-zone)
* [Creating your CBR rule](https://cloud.ibm.com/docs/containers?topic=containers-cbr-tutorialcbr-tutorial-create-rule)
* [Testing your context-based restrictions](https://cloud.ibm.com/docs/containers?topic=containers-cbr-tutorialcbr-tutorial-create-test)
* [Additional scenarios](https://cloud.ibm.com/docs/containers?topic=containers-cbr-tutorialcbr-tutorial-create-additional-scenarios)



* [Allowing different IPs to access the public and private service endpoints](https://cloud.ibm.com/docs/containers?topic=containers-cbr-tutorialcbr-tutorial-scenarios-pub-priv-one-ip)
* [Allowing different IPs to access different API types over the public and private service endpoints](https://cloud.ibm.com/docs/containers?topic=containers-cbr-tutorialcbr-tutorial-scenarios-pub-priv-api-types)









 Managing access control 

[Understanding access control for clusters](https://cloud.ibm.com/docs/containers?topic=containers-access-overviewaccess-overview)
: Optional: Skip [the check for infrastructure permissions](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cliinfra_permissions_get) before creating the cluster. Note that if you don't have the correct infrastructure permissions, the cluster creation might only partially succeed, such as the master provisioning but the worker nodes unable to provision. You might skip the permissions check if you want to continue an otherwise blocked operation, such as when you use multiple infrastructure accounts and can handle the infrastructure resources separately from the master, if needed later.

--kms-account-id ID
: Optional: The ID of the account that contains the KMS instance you want to use for local disk or secret encryption.

--kms-instance KMS_INSTANCE_ID
: Optional: Include the ID of a key management service (KMS) instance to use to encrypt the local disk on the worker nodes in the default worker pool. To list available KMS instances, run ibmcloud ks kms instance ls. If you include this option, you must also include the --crk option. Before you can use KMS encryption, you must create a KMS instance and set up the required service authorization in IAM. See [Managing encryption for the worker nodes in your cluster](https://cloud.ibm.com/docs/containers?topic=containers-encryptionworker-encryption).

--crk ROOT_KEY
: Optional: Include the ID of the root key in the KMS instance to use to encrypt the local disk on the worker nodes in the default worker pool. To list available root keys, run ibmcloud ks kms crk ls --instance-id. If you include this option, you must also include the --kms-instance option. Before you can use KMS encryption, you must create a KMS instance and set up the required service authorization in IAM. See [Managing encryption for the worker nodes in your cluster](https://cloud.ibm.com/docs/containers?topic=containers-encryptionworker-encryption).

--sm-group GROUP
Adding, viewing, and deleting clusters for vCenter Server with Hybridity Bundle instances 

The VMware ESXi™ servers that you configured when you ordered an instance are grouped as cluster1 by default.

You can add clusters to your VMware vCenter Server® with Hybridity Bundle instance to expand the compute and storage capacity. Within a cluster, manage the ESXi servers for better resource allocation and high availability. When no longer needed, delete the added clusters from your instance.



 Adding clusters to vCenter Server with Hybridity Bundle instances 

Adding clusters to instances with VMware vSphere® 6.5 is not supported.



 Before you add clusters 



* Whenever possible, add clusters by using the IBM Cloud® for VMware Solutions console and not the VMware vSphere® Web Client. Changes that you make on the vSphere Web Client are not synchronized with the VMware Solutions console. If you want to add clusters to vCenter Server instances by using the vSphere Web Client, do so only for on-premises clusters or clusters that you don't manage in the VMware Solutions console.
* The number of clusters, hosts, and VMs determines the maximum number of clusters that you can add. You must remain within the VMware® sizing guidelines and limits for your deployment. For more information, see [VMware Configuration Maximums](https://configmax.vmware.com/home).







 System settings 

When you add a cluster for a vCenter Server with Hybridity Bundle instance, you must specify the following settings.



 Cluster name 

The cluster name must meet the following requirements:



* Only alphanumeric and dash (-) characters are allowed.
* The cluster name must start and end with an alphanumeric character.
* The maximum length of the cluster name is 30 characters.
* The cluster name must be unique within the vCenter Server with Hybridity Bundle instance.







 Data center location 

The IBM Cloud data center location of the cluster is set to the IBM Cloud data center of the vCenter Server instance by default. You can deploy the cluster to a different IBM Cloud data center than the deployed instance.
2. Select the zones to create your cluster in. For more information about cluster availability, see [Planning your cluster for high availability](https://cloud.ibm.com/docs/containers?topic=containers-ha_clusters).



* The zones are filtered based on the VPC that you selected, and include the VPC subnets that you previously created.
* To create a single zone cluster, select one zone only. You can [add zones to your cluster](https://cloud.ibm.com/docs/containers?topic=containers-add_workersadd_zone) later.
* To create a multizone cluster, select multiple zones.





8. In the Worker pool section, choose your worker node flavor and number. You can add more worker pools to your cluster later. To change worker node operating systems, size, or storage, click Change flavor.



* Default: The default flavor comes with 4 vCPUs of computing power and 16 GB of memory. This virtual flavor is billed hourly. Other types of flavors include the following.
* Bare metal: Bare metal servers are provisioned manually by IBM Cloud infrastructure after you order, and can take more than one business day to complete. Bare metal is best suited for high-performance applications that need more resources and host control. Be sure that you want to provision a bare metal machine. Because it is billed monthly, if you cancel it immediately after an order by mistake, you are still charged the full month.
* Virtual - shared: Infrastructure resources, such as the hypervisor and physical hardware, are shared across you and other IBM customers, but each worker node is accessible only by you. Although this option is usually less expensive and sufficient, you might want to verify your performance and infrastructure requirements with your company policies. Virtual machines are billed hourly.
* Virtual - dedicated: Your worker nodes are hosted on infrastructure that is devoted to your account. Your physical resources are completely isolated. Virtual machines are billed hourly.



9. Optional: If the flavor that you want to use has a configurable secondary disk, you can modify the secondary disk by clicking the Edit icon !
Note the minimum required Kubernetes version of 1.21.

A minimal cluster with one (1) zone, one (1) worker node and the smallest available size (Flavor) is sufficient for this tutorial. A minimum Kubernetes version of 1.21 is required. Make sure to select an appropriate version when creating the cluster.

Open the [Kubernetes clusters](https://cloud.ibm.com/kubernetes/clusters) and click Create cluster. See the documentation referenced below for more details based on the cluster type. Summary:



* Click Standard tier cluster
* For Kubernetes on VPC infrastructure see the reference documentation [Creating VPC clusters](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-vpc-gen2&interface=ui).



* Click Create VPC:



* Enter a name for the VPC.
* Chose the same resource group as the cluster.
* Click Create.



* Attach a Public Gateway to each of the subnets that you create:



* Navigate to the [Virtual private clouds](https://cloud.ibm.com/vpc-ext/network/vpcs).
* Click the previously created VPC used for the cluster.
* Scroll down to subnets section and click a subnet.
* In the Public Gateway section, click Detached to change the state to Attached.
* Click the browser back button to return to the VPC details page.
* Repeat the previous three steps to attach a public gateway to each subnet.





* For Kubernetes on Classic infrastructure see reference documentation [Creating classic cluster](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-classic&interface=ui).
* Choose a resource group.
* Uncheck all zones except one.
* Scale down to 1 Worker nodes per zone.
* Choose the smallest Worker Pool flavor.
* Enter a Cluster namemycluster-tpcr.
* Click Create.



When the cluster is provisioned, leave the browser (cluster overview) tab open and available for later.
Use these commands to view the storage resources that run in clusters that are registered with [Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig).

The ibmcloud sat storage assignment group of commands are available in beta.

Before working with your Satellite storage assignments and configurations, be sure to target the Managed from region of your Satellite by running ibmcloud sat location ls then ibmcloud target -r <region>.



 ibmcloud sat storage assignment create 

Create a Satellite storage assignment to deploy storage drivers to your clusters.

ibmcloud sat storage assignment create --config CONFIG (--cluster CLUSTER_ID | --group GROUP [--group GROUP ...] | --service-cluster-id CLUSTER_ID) [--name NAME] [-q]



 Minimum required permissions 

IBM Cloud IAM Editor platform role for the Resource resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--config CONFIG
: Required. The name of the storage configuration that you want to assign to your cluster group. To list Satellite storage configurations, run ibmcloud sat storage config ls.

--cluster CLUSTER_ID
: The ID of a Satellite cluster. To list Satellite clusters, run ibmcloud oc cluster ls --provider satellite. To assign the storage configuration to multiple clusters at once, create a cluster group or run this command with this option multiple times. If you do not include this option, you must specify the --group or the --service-cluster-id option.

--group GROUP
: The ID of the cluster group. To list Satellite cluster groups, run ibmcloud sat group ls. To assign the storage configuration to multiple cluster groups at the same time, repeat this option. If you do not include this option, you must specify the --cluster or the --service-cluster-id option.

--service-cluster-id CLUSTER_ID
* [Delete failed](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-delete-failed)
* [Deleted](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-deleted)
* [Deleting](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-deleting)
* [Deploy failed](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-deploy-failed)
* [Deploying](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-deploying)
* [Normal](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-normal)
* [Pending](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-pending)
* [Requested](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-requested)
* [Updating](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-updating)
* [Unsupported](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-unsupported)
* [Warning](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-referencecluster-state-warning)
discovery.content-miner-export.download Download exported documents from a Content Mining project. 
 discovery.content-miner-export.search List sets of exported documents from a Content Mining project. 
 discovery.content-miner-report.create Create a report from a Content Mining project. 
 discovery.content-miner-report.delete Delete a report from a Content Mining project. 
 discovery.content-miner-report.read Get report content from a Content Mining project. 
 discovery.content-miner-report.update Update report content from a Content Mining project. 
 discovery.credential.create Create a credential. 
 discovery.credential.delete Delete a credential. 
 discovery.credential.read Get a credential, Salesforce objects, or a list of Cloud Object Storage buckets. 
 discovery.credential.update Update a credential. 
 discovery.curations.create Create a curated query. 
 discovery.curations.delete Delete specified curation. 
 discovery.curations.read List currently configured curation queries. 
 discovery.curations.update Update existing curated results documents for a specified query. 
 discovery.dataset.create Create a data set. 
 discovery.dataset.update Update a data set. 
 discovery.dataset-notices.read Get notices for a data set. 
 discovery.dictionary.create Create a dictionary. 
 discovery.dictionary.delete Delete a dictionary. 
 discovery.dictionary.read Read a dictionary. 
 discovery.dictionary.update Update a dictionary. 
 discovery.document.add Add one document. 
 discovery.document.create Create a document. 
 discovery.document.delete Delete a document by ID. 
 discovery.document.read Download a PDF version of a document. 
 discovery.document.update Update one document by ingesting new or modified content for a document given a document ID, or by changing the label for a specified document ID. 
 discovery.document-annotation.read Read document annotations. 
 discovery.document-results.read Search collections for relevant documents. 
 discovery.entity-extractor.create Create an entity extractor. 
 discovery.entity-extractor.delete Delete an entity extractor.
"resource_group": "Default",
"location": "us-south",
"tags": [
"schematics-api"
],
"created_at": "2021-10-15T15:19:12.631624491Z",
"created_by": “xxxxxx”,
"status": "DRAFT",
"failure_reason": "",
"workspace_status_msg": {
"status_code": "",
"status_msg": ""
},
"workspace_status": {
"frozen": false,
"locked": false
},
"template_repo": {
"url": "https://github.ibm.com/workload-eng-services/hpc-cluster-slurm”,
"commit_id": "",
"full_url": "https://github.ibm.com/workload-eng-services/hpc-cluster-slurm",
"has_uploadedgitrepotar": false
},
"template_data": [
{
"id": "369f3505-906f-45",
"folder": "",
"compact": false,
"type": "terraform_v0.14",
"values_url": "https://us.schematics.cloud.ibm.com/v1/workspaces/us-south.workspace.Sample-Schematic-API-workspace.0f4b9089/template_data/369f3505-906f-45/values",
"values": "",
"variablestore":
{
"name": "ssh_key_name",
"secure": false,
"value": "hpcc-slurm-key",
"type": "",
"description": ""
Minimum required permissions
: Operator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster. To list your clusters, use the ibmcloud ks cluster ls[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_clusters).

--size SIZE
: The number of IP addresses that you want to create in the portable subnet. Accepted values are 8, 16, 32, or 64. When you add portable IP addresses for your subnet, three IP addresses are used to establish cluster-internal networking. You can't use these three IP addresses for your Ingress application load balancers (ALBs) or to create network load balancer (NLB) services. For example, if you request eight portable public IP addresses, you can use five of them to expose your apps to the public.

--vlan VLAN_ID
: The ID of the public or private VLAN on which you want to create the subnet. You must select a public or private VLAN that an existing worker node is connected to. To review the public or private VLANs that your worker nodes are connected to, run ibmcloud ks cluster get --cluster <cluster> --show-resources and look for the Subnet VLANs section in the output. The subnet is provisioned in the same zone that the VLAN is in.

-q
: Optional: Do not show the message of the day or update reminders.



 Example cluster subnet create command 

ibmcloud ks cluster subnet create --cluster my_cluster --size 8 --vlan 1764905







 ibmcloud ks cluster subnet detach 

Classic infrastructure

Detach a public or private portable classic subnet in an IBM Cloud infrastructure account from a cluster. The subnet remains available in your IBM Cloud infrastructure account. Note: Any services that were deployed to an IP address from the subnet remain active after the subnet is removed.
: [Update any clusters](https://cloud.ibm.com/docs/containers?topic=containers-update) that run [Kubernetes 1.11](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsk8s_version_archive) before they become unsupported.

Permissions
: Added an FAQ, [What access policies do I give my cluster users?](https://cloud.ibm.com/docs/containers?topic=containers-faqsfaq_access)

Worker pools
: Added instructions for how to [apply labels](https://cloud.ibm.com/docs/containers?topic=containers-add_workersworker_pool_labels) to existing worker pools.

Reference topics
: To support new features such as Kubernetes 1.14, [change log reference](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionscs_versions_available) pages are updated.





 1 May 2019 

Assigning infrastructure access
: Revised the [steps](https://cloud.ibm.com/docs/containers?topic=containers-access-credsinfra_access) to assign IAM permissions for opening support cases.
- list
- watch
- apiGroups:
- ""
resources:
- events
verbs:
- list
- watch
- create
- update
- patch
- apiGroups:
- snapshot.storage.k8s.io
resources:
- volumesnapshots
verbs:
- get
- list
- apiGroups:
- snapshot.storage.k8s.io
resources:
- volumesnapshotcontents
verbs:
- get
- list
- apiGroups:
- storage.k8s.io
resources:
- csinodes
verbs:
- get
- list
- watch
- apiGroups:
- ""
resources:
- nodes
verbs:
- get
- list
- watch
- apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
name: vpc-block-provisioner-binding
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: vpc-block-provisioner-role
subjects:
- kind: ServiceAccount
name: ibm-vpc-block-controller-sa
namespace: kube-system
- apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
name: vpc-block-external-attacher-role
rules:
- apiGroups:
- ""
resources:
* [Resources in a single zone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zonesregions_single_zone)
* [Resources in a multizone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zonesregions_multizone)



* [Satellite regions](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zonessat-regions-openshift)
* [Accessing the global endpoint](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zonesendpoint)



* [Logging in to IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneslogin-ic)
* [Logging in to Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneslogin-iks)









 Supported IBM Cloud and third-party integrations 

[Supported IBM Cloud and third-party integrations](https://cloud.ibm.com/docs/openshift?topic=openshift-supported_integrationssupported_integrations)





 Default service settings for Red Hat OpenShift components 

[Default service settings for Red Hat OpenShift components](https://cloud.ibm.com/docs/openshift?topic=openshift-service-settingsservice-settings)



* [Feature gates](https://cloud.ibm.com/docs/openshift?topic=openshift-service-settingsfeature-gates)
* [Global settings](https://cloud.ibm.com/docs/openshift?topic=openshift-service-settingsglobal-settings)







 Related links 

[OpenShift Container Platform documentation](https://docs.openshift.com/)
[Cluster commands](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clicluster) Create, view, and modify clusters and cluster settings, such as add-on, subnet, and master settings. 
 [Worker commands](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cliworker_node_commands) View and modify worker nodes for a cluster. 
 [Worker-pool commands](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cliworker-pool) View and modify worker pools for a cluster. 
 [Zone commands](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clizone) List availability zones and modify the zones attached to a worker pool. 
 [Ingress commands](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clialb-commands) View and modify Ingress services and settings. 
 [Logging commands](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clilogging_commands) Forward logs from your cluster. 
 [NLB-DNS commands](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clinlb-dns) Create and manage host names for network load balancer (NLB) IP addresses in a cluster and health check monitors for host names. 
 [Webhook-create commands](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_webhook_create) Register a webhook in a cluster. 
 [API-key commands](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cliapi_key-commands) View information about the API key for a cluster or reset it to a new key.