vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see the ibmcloud sat storage assignment create[command](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-storage-assign-create).

Example command to assign a configuration to a cluster group.

ibmcloud sat storage assignment create --group GROUP --config CONFIG --name NAME

Example command to assign a configuration to a cluster.

ibmcloud sat storage assignment create --cluster CLUSTER --config CONFIG --name NAME

Example command to assign a configuration to a service cluster.

ibmcloud sat storage assignment create --service-cluster-id CLUSTER --config CONFIG --name NAME
4. Verify that your assignment is created.

ibmcloud sat storage assignment ls (--cluster CLUSTER | --config CONFIG | --location LOCATION | --service-cluster-id CLUSTER)







 Creating a storage assignment in the API 



1. Copy one of the following example requests.

Example request to assign a [configuration to a cluster](https://containers.cloud.ibm.com/global/swagger-global-api//satellite/createAssignmentByCluster).

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createAssignmentByCluster" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d "{ "channelName": "CONFIGURATION-NAME", "cluster": "CLUSTER-ID", "controller": "LOCATION-ID", "name": "ASSIGNMENT-NAME"}"

Example request to [assign configuration to a cluster group](https://containers.cloud.ibm.com/global/swagger-global-api//satellite/createAssignment).
ibmcloud ks cluster create vpc-gen2 --name <cluster-name> --zone <zone> --vpc-id <vpc-id> --subnet-id <subnet-id> --cluster-security-group cluster --cluster-security-group <group-id-1> --cluster-security-group <group-id-2> --cluster-security-group <group-id-3>

The following security groups are applied:



* kube-<cluster-id>
* Up to four of your own additional security groups, for a maximum of five total security groups.







 If you only want your own security groups 

Your own security groups

When you create the cluster, specify up to five security groups that you own. You must include a separate --cluster-security-group option for each individual security group you want to add.

Example command to create a VPC cluster with only your own security groups:

ibmcloud ks cluster create vpc-gen2 --name <cluster-name> --zone <zone> --vpc-id <vpc-id> --subnet-id <subnet-id> --cluster-security-group <group-id-1> --cluster-security-group <group-id-2> --cluster-security-group <group-id-3>

Up to five of your own security groups are applied to the workers on the cluster.







 Adding security groups to worker pools at worker pool create time 

By default, the security groups applied to a worker pool are the same security groups that are indicated at cluster create time. However, you can specify additional security groups to apply to a worker pool. If you apply additional security groups to the worker pool, then the security group applied to the workers on the cluster is a combination of the [security groups applied at cluster create](https://cloud.ibm.com/docs/containers?topic=containers-vpc-security-groupvpc-sg-cluster) and the security groups applied to the worker pool.

A maximum of five security groups can be applied to a worker, including the security groups applied by default.

The security groups applied to a worker pool cannot be changed once the worker pool is created.
The description includes how you can assign the permission in the IBM Cloud IAM Classic infrastructure console or the ibmcloud sl command. For more information, see the instructions for the [console](https://cloud.ibm.com/docs/containers?topic=containers-access-credsinfra_console) or [CLI](https://cloud.ibm.com/docs/containers?topic=containers-access-credsinfra_cli).

Create clusters
: Classic infrastructure permissions that you must have to create a cluster. When you run ibmcloud ks infra-permissions get, these permissions are listed as Required. For other service permissions that you must have in IBM Cloud IAM to create clusters, see [Permissions to create a cluster](https://cloud.ibm.com/docs/containers?topic=containers-access_reference).

Other common use cases
: Classic infrastructure permissions that you must have for other common scenarios. Even if you have permission to create a cluster, some limitations might apply. For example, you might not be able to create or work with a cluster with bare metal worker nodes or a public IP address. After cluster creation, further steps to add networking or storage resources might fail. When you run ibmcloud ks infra-permissions get, these permissions are listed as Suggested.



 Required classic infrastructure permissions 



Table 1: Required classic infrastructure permissions

 Permission Description IAM Assign Policy Console CLI 

 IPMI Remote Management Manage worker nodes. Classic infrastructure > Permissions > Devices ibmcloud sl user permission-edit <user_id> --permission REMOTE_MANAGEMENT --enable true 
 Add Server Add worker nodes.<br><br>Note: For worker nodes that have public IP addresses, you also need the Add Compute with Public Network Port permission in the Network category.
curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createAssignmentByCluster" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d "{ "channelName": "CONFIGURATION-NAME", "cluster": "CLUSTER-ID", "controller": "LOCATION-ID", "name": "ASSIGNMENT-NAME"}"

Example request to [assign configuration to a cluster group](https://containers.cloud.ibm.com/global/swagger-global-api//satellite/createAssignment).

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createAssignment" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d "{ "channelName": "CONFIGURATION-NAME", "cluster": "string", "groups": [ "CLUSTER-GROUP" ], "name": "ASSIGNMENT-NAME"}"
2. Replace the variables with your details and run the request.
3. Verify the assignment was created by listing your assignments.

curl -X GET "https://containers.cloud.ibm.com/global/v2/storage/satellite/getAssignments" -H "accept: application/json" -H "Authorization: Bearer TOKEN"





 Optional: Adding additional worker nodes to your ODF configuration 



1. Add more worker nodes to your ODF configuration.

ibmcloud sat storage config param set --config <config-name> -p "worker-nodes=<comma-separated values of new worker-nodes followed by list of old worker-nodes>" --apply
2. Verify that the storage configuration resources are deployed.



1. Get the storagecluster that you deployed and verify that the phase is Ready.

oc get storagecluster -n openshift-storage

Example output

NAME AGE PHASE EXTERNAL CREATED AT VERSION
ibmcloud oc cluster create vpc-gen2 --name <cluster-name> --zone <zone> --vpc-id <vpc-id> --subnet-id <subnet-id> --cluster-security-group cluster --cluster-security-group <group-id-1> --cluster-security-group <group-id-2> --cluster-security-group <group-id-3>

The following security groups are applied:



* kube-<cluster-id>
* Up to four of your own additional security groups, for a maximum of five total security groups.







 If you only want your own security groups 

Your own security groups

When you create the cluster, specify up to five security groups that you own. You must include a separate --cluster-security-group option for each individual security group you want to add.

Example command to create a VPC cluster with only your own security groups:

ibmcloud oc cluster create vpc-gen2 --name <cluster-name> --zone <zone> --vpc-id <vpc-id> --subnet-id <subnet-id> --cluster-security-group <group-id-1> --cluster-security-group <group-id-2> --cluster-security-group <group-id-3>

Up to five of your own security groups are applied to the workers on the cluster.







 Adding security groups to worker pools at worker pool create time 

By default, the security groups applied to a worker pool are the same security groups that are indicated at cluster create time. However, you can specify additional security groups to apply to a worker pool. If you apply additional security groups to the worker pool, then the security group applied to the workers on the cluster is a combination of the [security groups applied at cluster create](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-security-groupvpc-sg-cluster) and the security groups applied to the worker pool.

A maximum of five security groups can be applied to a worker, including the security groups applied by default.
Enable [boot volume encryption](https://cloud.ibm.com/docs/containers?topic=containers-encryptionworker-encryption-vpc). From the drop down menus, select a key management service (KMS) instance and root key to encrypt the local disk for each worker node in the default worker pool. If you choose not to enable this option when you create your cluster, you can enable it later.
14. Configure your cluster with a private or a public and a private cloud service endpoint by setting the Master service endpoint. For more information about what setup is required to run internet-facing apps, or to keep your cluster private, see [Planning your cluster network setup](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_vpc_basicsvpc-workeruser-master).
15. Configure [Secrets Manager](https://cloud.ibm.com/docs/containers?topic=containers-secrets-mgr&interface=ui) for your cluster's Ingress instance. From the Secrets Manager instance drop down menu, choose an existing instance that you want to register to the cluster. If no instances are available, [create one](https://cloud.ibm.com/docs/containers?topic=containers-secrets-mgr). If you want to apply a secret group, choose one from the Secrets Manager group drop down menu. If you choose not to enable this option when creating your cluster, you can enable it later.
16. If you don't have the required infrastructure permissions to create a cluster, the Infrastructure permissions checker lists the missing permissions. Ask your account owner to [set up the API key](https://cloud.ibm.com/docs/openshift?topic=openshift-access-creds) with the required permissions.
17. Complete the Resource details to customize the unique cluster name and any [tags](https://cloud.ibm.com/docs/account?topic=account-tag) that you want to use to organize your IBM Cloud resources, such as the team or billing department.
* [Understanding responsibilities for your enterprise and your clients](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelresponsibilities-tenancy)
* [Setting up your account](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelaccount-setup-tenancy)



* [Creating an enterprise account](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelcreate-enterprise-tenancy)
* [Setting up client accounts](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelcreate-account-tenancy)



* [Setting up the client location](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelsetting-up-locations-tenancy)



* [Sizing and creating the client location](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelcreate-provision-tenancy)
* [Attaching hosts to the location](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelattach-hosts-tenancy)
* [Assigning hosts to the control plane](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelassign-hosts-tenancy)



* [Creating a cluster, API key, and cluster roles](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelcreate-cluster-key-tenancy)



* [Creating a Satellite cluster](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelcreate-cluster-tenancy)
* [Creating an API key](https://cloud.ibm.com/docs/satellite?topic=satellite-tenancy-modelcreate-api-tenancy)
ibmcloud sat group attach 

Add a Red Hat OpenShift on IBM Cloud cluster to your cluster group. The cluster can run in your Satellite location or in IBM Cloud. To add a cluster that runs in IBM Cloud, you must first [register the cluster](https://cloud.ibm.com/docs/cli?topic=cli-satellite-cli-referencecli-cluster-register) with the Satellite Config component.

ibmcloud sat group attach --cluster CLUSTER [--cluster CLUSTER] --group GROUP [-q]



 Minimum required permissions 

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





 Command options 

--cluster, -c CLUSTER
: Required. The cluster that you want to add to the cluster group. To list registered clusters, run ibmcloud sat cluster ls.

--group, -g GROUP
: Required. The name or ID of the cluster group where you want to add the cluster. To list available cluster groups, run ibmcloud sat group ls.

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





 Example 

ibmcloud sat group attach --cluster mycluster --group mygroup







 ibmcloud sat group create 

Create a cluster group. After you created the cluster group, you can subscribe the cluster group to a Satellite configuration.

ibmcloud sat group create --name NAME [--cluster CLUSTER] [-q]



 Minimum required permissions 

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





 Command options 

--name NAME
: Required. The name for the cluster group.

--cluster, -c CLUSTER
: Optional.
curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createAssignmentByCluster" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d "{ "channelName": "CONFIGURATION-NAME", "cluster": "CLUSTER-ID", "controller": "LOCATION-ID", "name": "ASSIGNMENT-NAME"}"

Example request to [assign configuration to a cluster group](https://containers.cloud.ibm.com/global/swagger-global-api//satellite/createAssignment).

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createAssignment" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d "{ "channelName": "CONFIGURATION-NAME", "cluster": "string", "groups": [ "CLUSTER-GROUP" ], "name": "ASSIGNMENT-NAME"}"
2. Replace the variables with your details and run the request.
3. Verify the assignment was created by listing your assignments.

curl -X GET "https://containers.cloud.ibm.com/global/v2/storage/satellite/getAssignments" -H "accept: application/json" -H "Authorization: Bearer TOKEN"







 Deploying an app that uses Block Storage for Classic 

You can use the ibm-system-storage-block-csi-driver to create PVCs that you can use in your cluster workloads.



1. Create a Kubernetes secret configuration file that contains your Block Storage for Classic credentials.

kind: Secret
apiVersion: v1
metadata:
name: demo-secret
namespace: default
type: Opaque
stringData:
management_address: demo-management-address Example: baremetal-cluster.xiv.ibm.com
username: demo-username
data:
password: AAAA1AAA
2.
[Auto deployment button](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/autodeploy_button.png)[Deploy to IBM Cloud](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/Cloud-Schematics/gcat-iam-setup-module&terraform_version=terraform_v1.0) <br> 







 Classic infrastructure service 



Classic infrastructure templates to provision resource using Schematics workspace

 Template Description Provision 

 [Autoscale the Classic VSIs](https://github.com/Cloud-Schematics/classic-vsi-autoscaling-solution) Autoscale the classic VSIs using Schematics, Cloud Functions, and Sysdig. ![Auto deployment button](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/autodeploy_button.png)[Deploy to IBM Cloud](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/Cloud-Schematics/classic-vsi-autoscaling-solution&terraform_version=terraform_v0.13) <br> 
 [LEMP to provision a Classic Virtual Server instance](https://github.com/Cloud-Schematics/LEMP) Provision a classic Virtual Server Instance (VSI) by using a full-stack LEMP environment on a virtual machine. !
[Auto deployment button](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/autodeploy_button.png)[Deploy to IBM Cloud](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/Cloud-Schematics/logdna-provider-example&terraform_version=terraform_v0.13) <br> 
 [Configure alerts and dashboard for Monitoring services](https://github.com/Cloud-Schematics/sysdig-provider-example) Configure the monitoring service instance in IBM Cloud with alerts and dashboard. ![Auto deployment button](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/autodeploy_button.png)[Deploy to IBM Cloud](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/Cloud-Schematics/sysdig-provider-example&terraform_version=terraform_v0.12) <br> 







 Storage 



Storage Terraform templates to provision resource using Schematics workspace

 Template Description Provision 

 [IBM Cloud Object Storage bucket with encryption](https://github.com/Cloud-Schematics/kms-encrypted-cos-bucket) Provision IBM Cloud Object Storage with IBM Key Protect integration. !
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring//images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring//images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring//images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring//images/checkmark-icon.svg) 



For hosts running an agent for orchestrated environments that exceed the base tier allotment for Prometheus, JMX, appchecks, and Statsd metrics, additional prices apply:



* Time series are priced according to the following tiers:



* Tier 1: The price per time-series is 0.08 USD for up to 100K time-series per month.
* Tier 2: The price per time-series is 0.05 USD for 100K to 1M time-series per month.
* Tier 3: The price per time-series is 0.03 USD for 1M to 10M time-series per month.
* Tier 4: The price per time-series is 0.02 USD for more than 10M time-series per month.



* Containers are priced as follows: 5.23 USD per 10 containers per month.
* API calls are priced as follows: The price for API calls is 0.01 USD per 1000 API calls per month.



Each measure is priced independently when there is an overage.
[Auto deployment button](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/autodeploy_button.png)[Deploy to IBM Cloud](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/Cloud-Schematics/gcat-landing-zone&terraform_version=terraform_v1.0) <br> 
 [Setting up VPC infrastructure from an Enterprise account](https://github.com/Cloud-Schematics/gcat-landing-zone-child-account) Provision a VPC infrastructure in an Enterprise child account from an Enterprise parent account using modules. ![Auto deployment button](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/autodeploy_button.png)[Deploy to IBM Cloud](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/Cloud-Schematics/gcat-landing-zone-child-account&terraform_version=terraform_v1.0) <br> 







 Observability 



Observability Terraform templates to provision resource using Schematics workspace

 Template Description Provision 

 [Observability service instance](https://github.com/Cloud-Schematics/terraform-ibm-observability) Provision an instance of all the Observability services on IBM Cloud such as IBM Cloud Log Analysis, IBM Cloud Monitoring, and IBM Cloud Activity Tracker in your account. !
[Auto deployment button](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/autodeploy_button.png)[Deploy to IBM Cloud](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/Cloud-Schematics/sysdig-provider-example&terraform_version=terraform_v0.12) <br> 







 Storage 



Storage Terraform templates to provision resource using Schematics workspace

 Template Description Provision 

 [IBM Cloud Object Storage bucket with encryption](https://github.com/Cloud-Schematics/kms-encrypted-cos-bucket) Provision IBM Cloud Object Storage with IBM Key Protect integration. ![Auto deployment button](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/autodeploy_button.png)[Deploy to IBM Cloud](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/Cloud-Schematics/kms-encrypted-cos-bucket&terraform_version=terraform_v0.13) <br> 







 Account management and IAM 



Account management and IAM Terraform templates to provision resource using Schematics workspace

 Template Description Provision 

 [Clone users to new account](https://github.com/Cloud-Schematics/add-all-users-to-new-account) Clone all the IAM users from one IBM Cloud account into another IBM Cloud account. !
(https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) 
 Apply a Terraform template ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) 
 Destroy workspace resources ![Check mark icon.]
(https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) 
 Freeze and unfreeze workspace ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) 
 View the readme of a template ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.]