vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [ibmcloud ks cluster config](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_config)
* cluster create: Create a classic or VPC cluster.



* [ibmcloud ks cluster create classic](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_create)
* [ibmcloud ks cluster create vpc-gen2](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clicli_cluster-create-vpc-gen2)



* [ibmcloud ks cluster get](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_get)
* cluster image-security: Manage image security enforcement in your cluster.



* [ibmcloud ks cluster image-security disable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics-image-security-disable)
* [ibmcloud ks cluster image-security enable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics-image-security-enable)



* [ibmcloud ks cluster ls](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_clusters)
* cluster master: View and modify the master for a cluster.



* cluster master audit-webhook: View and modify the audit webhook configuration for a cluster's Kubernetes API server.



* [ibmcloud ks cluster master audit-webhook get](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_apiserver_config_get)
For more information, see [Deploy NSX Manager Nodes to Form a Cluster from the UI](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/installation/GUID-B89F5831-62E4-4841-BFE2-3F06542D5BF5.htmlGUID-B89F5831-62E4-4841-BFE2-3F06542D5BF5).
5. Configure a Virtual IP Address for a Cluster. se the IP addresses provisioned in the [previous tutorial](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-nsx-t-hostsvpc-bm-vmware-nsx-t-vlannics).For more information, see [Configure a Virtual IP Address for a Cluster](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/installation/GUID-A8DF27CC-B3A6-45F2-856D-4278A7DBC98E.html?hWord=N4IghgNiBcIG4EsAOIC+Q).
6. Create transport zones. For simplicity, you can use the default overlay and VLAN transport zones. For more information, see [Create Transport Zones](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/installation/GUID-F739DC79-4358-49F4-9C58-812475F33A66.htmlGUID-F739DC79-4358-49F4-9C58-812475F33A66).
Log in to your [IBM Cloud account](https://cloud.ibm.com/).
2. From the Catalog, click [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/kubernetes/catalog/about?platformType=openshift).
3. Review the platform version details, Red Hat OpenShift 4.11.42.
4. If you see the OCP entitlement section: Leave the value set to Purchase additional licenses for this worker pool because you are not using an IBM Cloud Pak for this getting started cluster.
5. For the Infrastructure, select Classic.
6. Configure the Location details for your cluster.



1. Select the Resource group that you want to create your cluster in. You can't change the resource group later. If you don't select a resource group, your cluster is created in the default resource group.
2. Select a Geography to create the cluster in, such as North America. The geography helps filter the Availability and Data centers values that you can select.
3. Select the Availability that you want for your cluster, such as Single zone.
4. Select the Worker zone to create your cluster in, such as Dallas 10.



7. Configure your Worker pool setup.



1. If you want a larger size for your worker nodes, click Change flavor. Otherwise, leave the default 4 vCPUs / 16 GB flavor selected.
2. Set how many worker nodes to create per zone, such as the minimum value of 2. For more information, see [What is the smallest size cluster that I can make?](https://cloud.ibm.com/docs/openshift?topic=openshift-faqssmallest_cluster).



8. Complete the Resource details to customize the cluster name and any tags that you want to use to organize your IBM Cloud resources.
9. In the Summary pane, review the order summary and then click Create. Your cluster creation might take some time to complete.
For more information, see [Creating a resource group](https://cloud.ibm.com/docs/account?topic=account-rgs). Ensure you have right access permission for the resource group. 
 profile_id String Required Create an IAM trusted profile ID for the Agents with the roles and actions. For more information, see [creating profile_id for Agents](https://cloud.ibm.com/docs/schematics?topic=schematics-agent-trusted-profile). 
 cluster_id String Required The IBM Cloud Kubernetes Service cluster ID used to run an Agent service. You need to record the cluster_id details that you have received in Agent infrastructure output job logs. 
 logdna_name String Required The LogDNA service instance name used to send an Agent logs. You need to record the logdna_name details that you have received in Agent infrastructure output job logs. 
 ibmcloud_api_key String Optional The IBM Cloud API key used to deploy the Schematics Agent resources. If not provided, resources provisions in currently logged in user credentials. 



4. Click Apply plan on the schematics-agent-service workspace to deploy the Agent service. Wait 15 - 30 minutes to complete the service execution.
5. View the Jobs logs and Resources page to observe the workspace status as ACTIVE.





 Expected outcome 

Follow the steps to view the deployment of Agent service workspace.



1. Navigate to the target [IBM Cloud clusters](https://cloud.ibm.com/kubernetes/clusters/) page. Enter your <target_iks_cluster_ID> as part of the URL.
2. Click Kubernetes Clusters page.
3. Click your cluster hyper link.
4. Click Kubernetes dashboard > Pods.
5. Switch to your schematics-job-runtime namespace from the drop down box next to search icon to view jobrunner pod (1 instance) > Status: Running.
6.
* UI
* CLI
* API







 NetApp Trident Operator 

Set up [NetApp Trident storage](https://netapp-trident.readthedocs.io/en/stable-v20.07/) for IBM Cloud Satellite® clusters. You can use Satellite storage templates to create storage configurations. When you assign a storage configuration to your clusters, the storage drivers of the selected storage provider are installed in your cluster.

You must deploy the NetApp Trident template to your clusters before you can create configurations with the NetApp ONTAP-NAS or NetApp ONTAP-SAN templates.

Before you can deploy storage templates to clusters in your location, make sure you set up Satellite Config by selecting the Enable cluster admin access for Satellite Config option in the console or including the --enable-config-admin option when you create your cluster.



 Prerequisites for NetApp Trident 



1. [Create a Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-locations).
2. [Set up Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig).







 Creating and assigning a configuration in the console 



1. [From the Locations console](https://cloud.ibm.com/satellite/locations), select the location where you want to create a storage configuration.
2. Select Storage > Create storage configuration
3. Enter a name for your configuration.
4. Select the Storage type.
5. Select the Version and click Next
6. If the Storage type that you selected accepts custom parameters, enter them on the Parameters tab.
7. If the Storage type that you selected requires secrets, enter them on the Secrets tab.
8. On the Storage classes tab, review the storage classes that are deployed by the configuration or create a custom storage class.
9. On the Assign to service tab, select the service that you want to assign your configuration to.
10. Click Complete to assign your storage configuration.
Create an SHH key in your IBM Cloud account. This is your SSH key that you will use to access the Slurm cluster. For more information, see [Managing SSH keys](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-ssh-keys).





 Step 3: Next steps 

After you've gathered the necessary input values to define your cluster configuration, you are ready to deploy your Slurm cluster. The Slurm cluster can be deployed on IBM Cloud by using the IBM Cloud Schematics UI, Schematics CLI, or the Schematics APIs. If you want to deploy your cluster by using the CLI or API, review the prerequisites for your interface of choice:



* [Setting up the IBM Cloud Schematics CLI](https://cloud.ibm.com/docs/hpc-slurm?topic=hpc-slurm-setting-up-cli)
* [Setting up the IBM Cloud Schematics API](https://cloud.ibm.com/docs/hpc-slurm?topic=hpc-slurm-setting-up-api)



After you've created and gathered your information and reviewed any additional prerequisites for your interface of choice, you are ready to begin [Creating a workspace](https://cloud.ibm.com/docs/hpc-slurm?topic=hpc-slurm-creating-workspace).
* Scale down to 1 Worker nodes per zone.
* Choose the smallest Worker Pool flavor.
* Enter a Cluster name.
* Click Create.







 Step 2: Deploy and configure a Kubernetes app to forward logs 

The ready-to-run [code for the logging app is located in this GitHub repository](https://github.com/IBM-Cloud/application-log-analysis). The application is written using [Django](https://www.djangoproject.com/), a popular Python server-side web framework. Clone or download the repository, then deploy the app to Kubernetes Service on IBM Cloud.



 Clone the application 

In a terminal window:



1. Clone the GitHub repository:

git clone https://github.com/IBM-Cloud/application-log-analysis
2. Change to the application directory

cd application-log-analysis







 Deploy the application 



1. Gain access to your cluster as described under the Access section of your cluster.

For more information on gaining access to your cluster and to configure the CLI to run kubectl commands, check the [CLI configure](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_installcs_cli_configure) section
2. Define an environment variable named MYCLUSTER with your cluster name:

MYCLUSTER=mycluster
3. Make sure to be logged in. Retrieve the cluster ingress subdomain:

ibmcloud ks cluster get --cluster $MYCLUSTER
4. Define a variable pointing to the subdomain:

MYINGRESSSUBDOMAIN=<Ingress Subdomain value>
5. Initialize the kubectl cli environment

ibmcloud ks cluster config --cluster $MYCLUSTER
6. Edit app-log-analysis.yaml and replace the placeholder ($MYINGRESSSUBDOMAIN) with the value captured in the previous step.
* [Setting up your location and cluster for autoscaling](https://cloud.ibm.com/docs/openshift?topic=openshift-prepare-autoscale-satsetup-location-cluster-scale-sat)



[Enabling the cluster autoscaler add-on in your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-scaling-install-addoncluster-scaling-install-addon)



* [Enabling the cluster autoscaler add-on from the console](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-scaling-install-addonautoscaler-enable-console)
* [Enabling the cluster autoscaler add-on from the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-scaling-install-addonautoscaler-enable-CLI)
* [Updating the cluster autoscaler add-on](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-scaling-install-addoncluster-scaling-update-addon)
* [Removing the cluster autoscaler add-on from the console](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-scaling-install-addonautoscaler-remove-console)
* [Removing the cluster autoscaler add-on from the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-scaling-install-addonautoscaler-remove-cli)
* [Cluster autoscaler add-on parameter reference](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-scaling-install-addonca_addon_ref)



[Setting up autoscaling for your worker pools](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-scaling-enablecluster-scaling-enable)
* UI
* CLI
* API







 AWS EFS 

Set up [Amazon Elastic File System (EFS)](https://docs.aws.amazon.com/efs/?id=docs_gateway) for Satellite clusters by creating a storage configuration in your location. When you assign a storage configuration to your clusters, the storage drivers of the selected storage provider are installed in your cluster.

To use AWS EFS storage for your apps, your Satellite hosts must reside in AWS. Only static provisioning is supported with this storage template. You must manually provision an [AWS EFS file system](https://docs.aws.amazon.com/efs/latest/ug/gs-step-two-create-efs-resources.html) on AWS before you create your Satellite storage configuration. Make sure that the EFS device is in the same VPC and subnet that you used for your AWS hosts, and that your hosts and EFS device use the same security group.

Before you can deploy storage templates to clusters in your location, make sure you set up Satellite Config by selecting the Enable cluster admin access for Satellite Config option in the console or including the --enable-config-admin option when you create your cluster.



 Prerequisites for using AWS EFS 

To use the AWS EFS storage template, complete the following tasks:



1. [Create a Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-locations).
2. [Set up Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig).
3. [Create a Satellite cluster](https://cloud.ibm.com/docs/satellite?topic=openshift-satellite-clusters) that runs on compute hosts in Amazon Web Services (AWS). Make sure that you select the Enable cluster admin access for Satellite Config option when you create the cluster.
The zone name for the default worker pool. To see available zones, run ibmcloud ks zones --provider vpc-gen2.



3. In the CLI, navigate to your Terraform directory.

cd <terraform_directory>
4. Run the commands to initialize and plan your Terraform actions. Review the plan output to make sure the correct actions are performed.

terraform init

terraform plan
5. Apply the Terraform files to create the cluster. Then, navigate to the IBM Cloud console to check that the cluster is provisioning.

terraform apply
TYPE", { "entry.name": "IBM-COS-ENDPOINT", { "entry.name": "IBM-COS-LOCATION", { "entry.name": "CLUSTER-ENCRYPTION", { "entry.name": "PERFORM-CLEANUP", { "entry.name": "KMS-ENCRYPTION", { "entry.name": "KMS-INSTANCE-NAME", { "entry.name": "KMS-INSTANCE-ID", { "entry.name": "KMS-BASE-URL", { "entry.name": "KMS-TOKEN-URL", { "entry.name": "IGNORE-NOOBAA","user-secret-parameters": { "entry.name": "IBM-COS-ACCESS-KEY",{ "entry.name": "IBM-COS-SECRET-KEY",{ "entry.name": "IAM-API-KEY",{ "entry.name": "KMS-ROOT-KEY",{ "entry.name": "KMS-API-KEY",}







 Creating a storage assignment in the console 

If you didn't assign your configuration to a cluster or service when you created it, you can create an assignment by completing the following steps.



1. Open the [Satellite console](https://cloud.ibm.com/satellite/locations) in your browser.
2. Select the location where you created your storage configuration.
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.
* UI
* CLI
* API







 Local Storage Operator - File 

Set up [Persistent storage using local volumes](https://docs.openshift.com/container-platform/4.6/storage/persistent_storage/persistent-storage-local.htmlcreate-local-pvc_persistent-storage-local) for IBM Cloud Satellite® clusters.You can use Satellite storage templates to create storage configurations. When you assign a storage configuration to your clusters, the storage drivers of the selected storage provider are installed in your cluster.

When you create a local file storage configuration, you specify the local storage devices that you want to make available as persistent volumes (PVs) in your clusters. After you assign the storage configuration to a cluster, Satellite deploys the local storage operator which mounts the local disks that you specified in your configuration. The operator further creates the persistent volumes with the file system type that you specify, and creates the sat-local-file-gold storage class which you can use to create persistent volume claims (PVCs). You can then reference your PVCs in your Kubernetes workloads.

Before you can deploy storage templates to clusters in your location, make sure you set up Satellite Config by selecting the Enable cluster admin access for Satellite Config option in the console or including the --enable-config-admin option when you create your cluster.



 Prerequisites for local file storage 

Before you can create a local file storage configuration, you must identify the worker nodes in your clusters that have the required available disks. Then, label these worker nodes so that the local storage drivers are installed on only these worker nodes.



1. [Create a Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-locations).
2. [Set up Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig).
3.
* Keep your the cluster_id, and logdna_name that are recorded from the Agent infrastructure Job logs.
* Create or use an existing trusted profile_id. For more information to create trusted profile-id, refer to [Create profile_id for Agents](https://cloud.ibm.com/docs/schematics?topic=schematics-agent-trusted-profile).



Here are the list of commands used to create the Agent service.



* Edit the Agent service using the following input variables in the [create Agent service workspace](https://github.com/Cloud-Schematics/schematics-agents/blob/main/tarfiles/create_agent_service_workspace.json) JSON file. For more information about the input variables, refer to [Input variable for Agent service](https://cloud.ibm.com/docs/schematics?topic=schematics-agents-setupagents-setup-svc).



Agent service input variable

 Input variable value 

 cluster_id provide the recorded cluster_id from Agent infrastructure job log. 
 resource_group_name provide the target resource group name, for example, default. 
 logdna_name provide the recorded logdna_name from Agent infrastructure job log. 
 schematics_endpoint_location provide your endpoint location, for example, us. 
 profile_id Provide your trusted profile ID. 
 location Enter the region, for example, us-south. 
 agent_name Enter your agent name, for example, myproject. 



The Agent service workspace should have the same input values for Resource Group, Location, and Tags. Use the cluster_id, and logdna_name that are recorded while provisioning the Agent infrastructure.
* Run [workspace new](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-new) command to create the Agent service workspace.

ibmcloud schematics workspace new --file <Provide the path where the JSON file resides>/create_agent_service_workspace.json
<br> <br>Resources <br><br><br><br> * ibm_container_cluster<br><br><br> [View code snippet](https://github.com/IBM-Cloud/terraform-provider-ibm/tree/master/examples/ibm-iks-classic-ROKS) 
 ibm-cluster-update Cordon and drain your worker nodes to update the IBM Cloud Kubernetes Service cluster master and worker nodes to the latest version. <br> <br>Resources <br><br><br><br> * null_resource<br> * ibm_container_cluster<br><br><br> [View code snippet](https://github.com/IBM-Cloud/terraform-provider-ibm/tree/master/examples/ibm-cluster-update) 
 cluster-worker-pool-zone Create an IBM Cloud Kubernetes Service cluster with a default worker pool that is spread across two zones. Also, you create another worker pool and bind an IBM Cloud service of your choice to the cluster. <br> <br>Resources <br><br><br><br> * ibm_container_cluster<br> * ibm_container_worker_pool_zone_attachment<br> * ibm_container_worker_pool<br> * ibm_service_instance<br> * ibm_service_key<br> * ibm_container_bind_service<br><br><br> [View code snippet](https://github.com/IBM-Cloud/terraform-provider-ibm/tree/master/examples/ibm-cluster/cluster-worker-pool-zone) 
 ibm-storage-cos Set up Helm in an IBM Cloud Kubernetes Service cluster to install the IBM Cloud Object Storage Helm plug-in. Then, you create an IBM Cloud Object Storage service instance where you can store data from the apps in your cluster. You also learn how to create a Kubernetes persistent volume claim (PVC) to create a bucket in your IBM Cloud Object Storage instance. Also to deploy an app in the cluster that mounts your IBM Cloud Object Storage bucket.
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. 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.