vania-janet/multiturn-rag-retrieval-data huggingface dataset:
GET/v1/addons List available add-ons that you can enable in a cluster. N/A N/A 
 GET/v1/config List configuration values for your IBM Cloud account. containers-kubernetes.cluster.read N/A 
 GET/v1/credentials View the IBM Cloud infrastructure account credentials that are set for your IBM Cloud Kubernetes Service account. containers-kubernetes.cluster.read N/A 
 GET/v1/datacenters/{datacenter}/machine-types List available machine types for a zone (data center). N/A N/A 
 GET/v1/datacenters/{datacenter}/vlans List available VLANs for a zone. N/A N/A 
 GET/v1/infra-permissions Get details on the permissions that the IBM Cloud infrastructure credentials have. containers-kubernetes.cluster.read N/A 
 GET/v1/kube-versions Deprecated: List available Kubernetes versions. N/A N/A 
 GET/v1/locations List available locations. N/A N/A 
 GET/v1/messages View the current user messages. N/A N/A 
 GET/v1/prodconfig List product-specific values to substitute for variables in other files. N/A N/A 
 GET/v1/regions Deprecated: List available Kubernetes Service regions. N/A N/A 
 GET/v1/subnets List available IBM Cloud infrastructure subnets. containers-kubernetes.cluster.read N/A 
 GET/v1/subnets/vlan-spanning View the VLAN spanning status. containers-kubernetes.cluster.read N/A 
 GET/v1/user-config View a user's ability to create clusters in a region and resource group. containers-kubernetes.cluster.read N/A 
 GET/v1/versions List available IBM Cloud Kubernetes Service versions. containers-kubernetes.cluster.read N/A
: Kubernetes version [1.18.6_1521](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog1186_1521), [1.17.9_1533](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog1179_1533), [1.16.13_1540](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog11613_1540), and [1.15.12_1547](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog11512_1547).

Worker node versions
: Worker node fix pack update change log documentation is available.
: Kubernetes version [1.18.6_1520](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog1186_1520), [1.17.9_1532](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog1179_1532), [1.16.13_1539](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog11613_1539), and [1.15.12_1546](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog11512_1546).





 17 July 2020 

Istio add-on
: [Version 1.6.5 of the Istio managed add-on](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog165) is released.





 16 July 2020 

Ingress ALB change log
: Updated the [nginx-ingress image build to 645 and the ingress-auth image build to 420](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog).
: Kubernetes version [1.18.6_1523](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog1186_1523), [1.17.9_1535](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog1179_1535), [1.16.13_1542](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog11613_1542), and [1.15.12_1549](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog11512_1549).







 July 2020 



 31 July 2020 

Red Hat OpenShift version 4.4
: The [Red Hat OpenShift version 4.4 release](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsk8s_version_archive) is certified for Kubernetes version 1.17.





 28 July 2020 

Ingress ALB versions
: Added the ibmcloud ks ingress alb versions CLI command to show the available versions for the ALBs in your cluster and the ibmcloud ks ingress alb update CLI command to update or rollback ALBs to a specific version.

UI for creating clusters
: 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.
* [ibmcloud oc cluster pull-secret apply](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_pull_secret_apply)



* [ibmcloud oc cluster rm](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_rm)
* cluster service: View, bind, and unbind IBM Cloud services on a cluster.



* [ibmcloud oc cluster service bind](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_service_bind)
* [ibmcloud oc cluster service ls](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_services)
* [ibmcloud oc cluster service unbind](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_service_unbind)



* cluster subnet: Add and create portable subnets for a classic cluster.



* [ibmcloud oc cluster subnet add](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_subnet_add)
* [ibmcloud oc cluster subnet create](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_subnet_create)
* [ibmcloud oc cluster subnet detach](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_subnet_detach)









 ibmcloud oc worker
[View the current user messages](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_messages).





 ibmcloud oc versions 

[List all the container platform versions that are available for IBM Cloud Kubernetes Service clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_versions_command).





 ibmcloud oc api 

Deprecated[View or set the API endpoint and API version for the service](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cli_api).





 ibmcloud oc init 

[Initialize the Kubernetes Service plug-in and get authentication tokens](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_init).





 ibmcloud oc script 

[Rewrite scripts that call IBM Cloud Kubernetes Service plug-in commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cliscript).



* [ibmcloud oc script update](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cliscript_update)







 ibmcloud oc security-group 

[Reset or sync security group settings](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clisecurity_group)



* [ibmcloud oc security-group reset](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clisecurity_group_reset)
* [Deploy a Kubernetes cluster on IBM Cloud](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-deploy-iks-icibp-v2-deploy-iks-deploy-cluster)



* [Free IBM Kubernetes Service clusters](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-deploy-iks-icibp-v2-deploy-iks-deploy-cluster-free)



* [Create an IBM Blockchain Platform service instance in IBM Cloud](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-deploy-iks-icibp-v2-deploy-iks-create-service-instance)



* [Step one: Create and name the instance](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-deploy-iks-icibp-v2-deploy-iks-create-service-instance-create)
* [Step two: Link the instance to your Kubernetes cluster on IBM Cloud](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-deploy-iks-icibp-v2-deploy-iks-steps)
* [Blockchain component deployment](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-deploy-iks-icibp-v2-deploy-components)



* [(Optional) Add additional users to the console](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-deploy-iks-icibp-v2-deploy-iks-add-users)
* The Kubernetes service subnet CIDR: 172.21.0.0/16. Service IP addresses provide a way to expose multiple app pods that are deployed on several worker nodes behind a single IP.
* If your apps are exposed by a NodePort service on the private network or a private Ingress ALB, add the worker node's private subnet CIDR. Retrieve the first three octets of your worker's private IP address by running ibmcloud ks worker <cluster_name>. For example, if it is 10.176.48.xx then note 10.176.48. Next, get the worker private subnet CIDR by running the following command, replacing <xxx.yyy.zz> with the octet that you previously retrieved: ibmcloud sl subnet list | grep <xxx.yyy.zzz>. Note: If a worker node is added on a new private subnet, you must add the new private subnet CIDR to the local.subnet setting and the on-premises VPN endpoint. Then, the VPN connection must be restarted.
* If you have apps that are exposed by LoadBalancer services on the private network, add the cluster's private user-managed subnet CIDRs. To find these values, run ibmcloud ks cluster get --cluster <cluster_name> --show-resources. In the VLANs section, look for CIDRs that have a Public value of false. Note: If ipsec.keyexchange is set to ikev1, you can specify only one subnet. However, you can use the localSubnetNAT setting to combine multiple cluster subnets into a single subnet.



2. Optional: Remap cluster subnets by using the localSubnetNAT setting. Network Address Translation (NAT) for subnets provides a workaround for subnet conflicts between the cluster network and on-premises remote network. You can use NAT to remap the cluster's private local IP subnets, the pod subnet (172.30.0.0/16), or the pod service subnet (172.21.0.0/16) to a different private subnet.
service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-lb-name: "my-load-balancer"
service.kubernetes.io/ibm-load-balancer-cloud-provider-enable-features: "proxy-protocol"
service.kubernetes.io/ibm-load-balancer-cloud-provider-ip-type: "<public_or_private>"
service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-node-selector: "<key>=<value>"
service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-subnets: "<subnet1_ID,subnet2_ID>"
service.kubernetes.io/ibm-load-balancer-cloud-provider-zone: "<zone>"
service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-health-check-protocol: "<protocol>"
service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-health-check-port: "<port>"
service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-health-check-path: "<url_path>"
service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-health-check-delay: "<value>"
service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-health-check-timeout: "<value>"
service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-health-check-retries: "<value>"
service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-idle-connection-timeout: "<value>"
spec:
type: LoadBalancer
selector:

<selector_key>: <selector_value>
ports:
- name: http
ibmcloud ks storage attachment rm --cluster aa1111aa11aaaaa11aa1 --attachment 0111-1a111aaa-1111-1111-111a-aaa1a1a11a11 --worker kube-aa1111aa11aaaaa11aa1-my_cluster-default-00000110 [--output json]





 ibmcloud ks storage volume get 

Virtual Private Cloud

Classic infrastructure

List storage volumes for your classic clusters.

Minimum required permissions
: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service

ibmcloud ks storage volume get --volume VOLUME

Command options:

--volume VOLUME
: Required: Specify the volume ID. To list available volumes, run ibmcloud ks storage volume ls.

--output json
: Optional: Prints the command output in JSON format.

Example:

ibmcloud ks storage volume get --volume 111111111





 ibmcloud ks storage volume ls 

Virtual Private Cloud

Classic infrastructure

Get a list of storage volumes.

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

ibmcloud ks storage volume ls [--cluster CLUSTER_ID] [--provider PROVIDER] [--zone ZONE] [--output json]

Command options:

--cluster CLUSTER_ID
: Optional: Specify the cluster ID. To list available clusters, run ibmcloud ks cluster ls.

--provider PROVIDER
: Optional: Specify the provider. Supported values are classic and vpc-gen2.

--zone ZONE
: Optional: Specify the zone. To list available zones, run ibmcloud ks locations.

--output json
: Optional: Prints the command output in JSON format.

Example:

ibmcloud ks storage volume ls --cluster aa1111aa11aaaaa11aa1
ibmcloud ks cluster user-subnet rm --cluster CLUSTER --subnet-cidr SUBNET_CIDR --private-vlan PRIVATE_VLAN

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.

--subnet-cidr SUBNET_CIDR
: The subnet Classless InterDomain Routing (CIDR). This value is required, and must match the CIDR that was set by the ibmcloud ks cluster user-subnet add[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_user_subnet_add).

--private-vlan PRIVATE_VLAN
: The ID of the private VLAN. This value is required, and must match the VLAN ID that was set by the ibmcloud ks cluster user-subnet add[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_user_subnet_add).



 Example cluster user-subnet rm command 

ibmcloud ks cluster user-subnet rm --cluster my_cluster --subnet-cidr 169.xx.xxx.xxx/29 --private-vlan 1502175









 Beta: dedicated commands 

View, create, and remove a dedicated host or dedicated host pool.

The dedicated commands are available in beta.



 Beta: ibmcloud ks dedicated flavors 

Virtual Private Cloud

View dedicated host flavors.

ibmcloud ks dedicated flavors --zone ZONE --provider PROVIDER

Minimum required permissions
: Operator platform access role for the cluster in IBM Cloud Kubernetes Service.

Command options:

--zone ZONE
: The zone to search for dedicated host flavors.

--provider PROVIDER
: The provider to use to search for dedicated host flavors.

--output json
: Optional: Prints the command output in JSON format.

Example:
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).

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

--secondary-storage STORAGE
: Optional: The storage option for the flavor. For example, 900gb.5iops-tier. When you add a secondary disk, that disk is used for the container runtime, while the primary disk is used for the operating system. To view the storage options for a flavor, run the ibmcloud ks flavor get --flavor FLAVOR --zone ZONE --provider vpc-gen2 command.

--security-group GROUP
: Optional. Specify up to five security group IDs to apply to all workers in the worker pool.

--output json
: Optional: Prints the command output in JSON format.



 Example worker-pool create vpc-gen2 command 

ibmcloud ks worker-pool create vpc-gen2 --name my_pool --cluster my_cluster --flavor bx2.4x16 --size-per-zone 3







 ibmcloud ks worker-pool get 

Virtual Private Cloud

Classic infrastructure

View the details of a worker pool.

ibmcloud ks worker-pool get --worker-pool WORKER_POOL --cluster CLUSTER [--output json] [-q]

Minimum required permissions
: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-p, --worker-pool WORKER_POOL
: Required: The name of the worker node pool that you want to view the details of. To list available worker pools, run ibmcloud ks worker-pool ls --cluster <cluster_name_or_ID>.
: Required: The name of the secret. To see available secrets, run ibmcloud ks ingress secret ls.

--namespace NAMESPACE
: Required: The namespace that the secret is deployed to. To see the secret namespace, run ibmcloud ks ingress secret get --cluster cluster_name_or_ID <--name secret_name> --namespace <namespace>.

--cert-crn CERTIFICATE_CRN
: Optional: The certificate CRN. To see the secret CRN, run ibmcloud ks ingress secret get --cluster <cluster_name_or_ID> --name secret_name> --namespace <namespace>. This option requires a default [Secrets Manager](https://cloud.ibm.com/docs/containers?topic=containers-secrets-mgrsecrets-mgr_about) instance in your cluster.

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



 Example ingress secret update command 

Virtual Private Cloud

Classic infrastructure

ibmcloud ks ingress secret update --cluster my_cluster --name my_alb_secret --namespace demo_ns







 ibmcloud ks ingress status-report disable 

Virtual Private Cloud

Classic infrastructure

Disable status reporting for Ingress components in a cluster.

ibmcloud ks ingress status-report disable --cluster CLUSTER [--output json] [-q]

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--output json
: Optional: Prints the command output in JSON format.

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



 Example ingress status-report disable command 

ibmcloud ks ingress status-report disable --cluster mycluster







 ibmcloud ks ingress status-report enable 

Virtual Private Cloud

Classic infrastructure

Enable the status reporting of the Ingress components in a cluster.
ibmcloud ks cluster user-subnet rm --cluster CLUSTER --subnet-cidr SUBNET_CIDR --private-vlan PRIVATE_VLAN

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.

--subnet-cidr SUBNET_CIDR
: The subnet Classless InterDomain Routing (CIDR). This value is required, and must match the CIDR that was set by the ibmcloud ks cluster user-subnet add[command](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_cluster_user_subnet_add).

--private-vlan PRIVATE_VLAN
: The ID of the private VLAN. This value is required, and must match the VLAN ID that was set by the ibmcloud ks cluster user-subnet add[command](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_cluster_user_subnet_add).



 Example cluster user-subnet rm command 

ibmcloud ks cluster user-subnet rm --cluster my_cluster --subnet-cidr 169.xx.xxx.xxx/29 --private-vlan 1502175









 Beta: dedicated commands 

View, create, and remove a dedicated host or dedicated host pool.

The dedicated commands are available in beta.



 Beta: ibmcloud ks dedicated flavors 

Virtual Private Cloud

View dedicated host flavors.

ibmcloud ks dedicated flavors --zone ZONE --provider PROVIDER

Minimum required permissions
: Operator platform access role for the cluster in IBM Cloud Kubernetes Service.

Command options:

--zone ZONE
: The zone to search for dedicated host flavors.

--provider PROVIDER
: The provider to use to search for dedicated host flavors.

--output json
: Optional: Prints the command output in JSON format.

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



 Example webhook-create command 

ibmcloud ks webhook-create --cluster my_cluster --level Normal --type slack --url http://github.com/mywebhook







 api-key commands 

View information about the API key for a cluster or reset it to a new key.



 ibmcloud ks api-key info 

Virtual Private Cloud

Classic infrastructure

View the name and email address for the owner of the IBM Cloud Identity and Access Management (IAM) API key that IBM Cloud Kubernetes Service uses to authenticate certain requests like infrastructure in the region and resource group. For more information, see [Understanding how the API key works](https://cloud.ibm.com/docs/containers?topic=containers-access-credsapi_key_about).

To create a different API key for the resource group and region, use the [ibmcloud ks api-key reset](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_api_key_reset) command.

If you manually set IBM Cloud infrastructure credentials by using the [ibmcloud ks credential set](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_credentials_set) command, the API key that is returned in this command is not used for infrastructure permissions.

ibmcloud ks api-key info --cluster CLUSTER [--output json] [-q]

Minimum required permissions
: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--output json
: Optional: Prints the command output in JSON format.

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



 Example api-key info command 

ibmcloud ks api-key info --cluster my_cluster







 ibmcloud ks api-key reset 

Virtual Private Cloud

Classic infrastructure
: Optional: Do not show the message of the day or update reminders.



 Example webhook-create command 

ibmcloud ks webhook-create --cluster my_cluster --level Normal --type slack --url http://github.com/mywebhook







 api-key commands 

View information about the API key for a cluster or reset it to a new key.



 ibmcloud ks api-key info 

Virtual Private Cloud

Classic infrastructure

View the name and email address for the owner of the IBM Cloud Identity and Access Management (IAM) API key that IBM Cloud Kubernetes Service uses to authenticate certain requests like infrastructure in the region and resource group. For more information, see [Understanding how the API key works](https://cloud.ibm.com/docs/containers?topic=containers-access-credsapi_key_about).

To create a different API key for the resource group and region, use the [ibmcloud ks api-key reset](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_api_key_reset) command.

If you manually set IBM Cloud infrastructure credentials by using the [ibmcloud ks credential set](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_credentials_set) command, the API key that is returned in this command is not used for infrastructure permissions.

ibmcloud ks api-key info --cluster CLUSTER [--output json] [-q]

Minimum required permissions
: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--output json
: Optional: Prints the command output in JSON format.

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



 Example api-key info command 

ibmcloud ks api-key info --cluster my_cluster







 ibmcloud ks api-key reset 

Virtual Private Cloud