vania-janet/multiturn-rag-retrieval-data huggingface dataset:
containers-kubernetes.cluster-worker-pool.rebalance A worker pool is rebalanced. 
 containers-kubernetes.cluster-worker-pool.resize A worker pool is resized, to add or decrease the number of worker nodes in the pool. 
 containers-kubernetes.cluster-worker-pool-autoscale.disable Autoscaling the worker pool is disabled. 
 containers-kubernetes.cluster-worker-pool-autoscale.enable Autoscaling the worker pool is enabled. 
 containers-kubernetes.cluster-worker-pool-label.set Kubernetes labels for a worker pool are set. Existing and future worker nodes in the worker pool inherit the label. 
 containers-kubernetes.cluster-worker-pool-taint.set Kubernetes taints for a worker pool are set. Existing and future worker nodes in the worker pool inherit the taint. 
 containers-kubernetes.cluster-worker-pool-zone.create A zone is added to a worker pool. 
 containers-kubernetes.cluster-worker-pool-zone.delete A zone is deleted from a worker pool. 
 containers-kubernetes.cluster-worker-pool-zone.get The details of a zone that a worker pool spans in the cluster are returned as part of cluster autoscaler operations. 
 containers-kubernetes.cluster-worker-pool-zone.list The worker pools for a cluster in a particular zone are listed as part of cluster autoscaler operations. 
 containers-kubernetes.cluster-worker-pool-zone.resize A worker node is added to or removed from a zone that the worker pool spans. 
 containers-kubernetes.cluster-worker-pool-zone-network.add The networking data, such as public and private VLAN data, is added for a zone that the worker pool spans. 
 containers-kubernetes.cluster-worker-pool-zone-worker.list The worker nodes within a zone that a the worker pool spans are listed as part of cluster autoscaler operations. 
 containers-kubernetes.worker.delete A worker node is deleted from the cluster.
resource "ibm_container_worker_pool" "workerpool" {
worker_pool_name = "tf-workerpool"
machine_type = "u3c.2x4"
cluster = ibm_container_cluster.tfcluster.id
size_per_zone = 2
hardware = "shared"

resource_group_id = data.ibm_resource_group.resource_group.id
}

resource "ibm_container_worker_pool_zone_attachment" "tfwp-dal10" {
cluster = ibm_container_cluster.tfcluster.id
worker_pool = element(split("/",ibm_container_worker_pool.workerpool.id),1)
zone = "dal10"
private_vlan_id = "<private_vlan_ID_dal10>"
public_vlan_id = "<public_vlan_ID_dal10>"
resource_group_id = data.ibm_resource_group.resource_group.id
}

resource "ibm_container_worker_pool_zone_attachment" "tfwp-dal12" {
cluster = ibm_container_cluster.tfcluster.id
worker_pool = element(split("/",ibm_container_worker_pool.workerpool.id),1)
zone = "dal12"
private_vlan_id = "<private_vlan_ID_dal12>"
public_vlan_id = "<public_vlan_ID_dal12>"
resource_group_id = data.ibm_resource_group.resource_group.id
}

resource "ibm_container_worker_pool_zone_attachment" "tfwp-dal13" {
cluster = ibm_container_cluster.tfcluster.id
worker_pool = element(split("/",ibm_container_worker_pool.workerpool.id),1)
zone = "dal13"
private_vlan_id = "<private_vlan_ID_dal13>"
* ibmcloud is load-balancer-create my-lb public --subnet 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --subnet 7ec86020-1c6e-4889-b3f0-a15f2e50f87e
* ibmcloud is load-balancer-create my-lb public --subnet my-subnet --subnet my-subnet2
* ibmcloud is load-balancer-create my-lb public --subnet my-subnet --vpc my-vpc
* ibmcloud is load-balancer-create my-nlb public --subnet 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --family network
* ibmcloud is load-balancer-create my-lb public --subnet 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --subnet 7ec86020-1c6e-4889-b3f0-a15f2e50f87e --resource-group-id fee82deba12e4c0fb69c3b09d1f12345
* ibmcloud is load-balancer-create my-lb public --subnet 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --subnet 7ec86020-1c6e-4889-b3f0-a15f2e50f87e --resource-group-name Default
* ibmcloud is load-balancer-create my-lb public --subnet 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --subnet 7ec86020-1c6e-4889-b3f0-a15f2e50f87e --output JSON
If specified, this annotation takes precedence over the service.kubernetes.io/ibm-load-balancer-cloud-provider-zone annotation. Note that you can specify a different subnet in the same VPC than the subnets that your cluster is attached to. In this case, even though the VPC NLB deploys to a different subnet in the same VPC, the VPC NLB can still route traffic to your worker nodes on the cluster subnets in the same zone. To see subnets in all resource groups, run ibmcloud ks subnets --provider vpc-gen2 --vpc-id <vpc> --zone <zone>.

service.kubernetes.io/ibm-load-balancer-cloud-provider-zone
: Optional: Annotation to specify a VPC zone that your cluster is attached to. The VPC NLB is deployed to the same subnet in that zone that your worker nodes are connected to. Because the VPC NLB is single-zone, only worker nodes in your cluster in this zone are configured to receive traffic.
: To see zones, run ibmcloud ks zone ls --provider vpc-gen2. If you later change this annotation to a different zone, the VPC NLB is not moved to the new zone.
: Note that if you don't specify this annotation or the service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-subnets annotation, the VPC NLB is deployed to the most optimal zone. For example, the VPC NLB is deployed only to zones in which worker nodes exist and are in the Ready state.

service.kubernetes.io/ibm-load-balancer-cloud-provider-vpc-health-check-udp
: Optional: Specify a TCP port to use for TCP health checks in a UDP load balancer. Required for UDP load balancers that have externalTrafficPolicy set to Cluster.
Reader role When scoped to one namespace: view cluster role applied by the ibm-view role binding in that namespace.<br><br><br><br> * When scoped to all namespaces: view cluster role applied by the ibm-view role binding in each namespace of the cluster. You can also view the cluster in the IBM Cloud console and CLI.<br><br><br> <br><br> * Read access to resources in a namespace<br> * No read access to roles and role bindings or to Kubernetes secrets<br> * Access the Kubernetes dashboard to view resources in a namespace.<br><br><br> 
 Writer role When scoped to one namespace: edit cluster role applied by the ibm-edit role binding in that namespace.<br><br>When scoped to all namespaces: edit cluster role applied by the ibm-edit role binding in each namespace of the cluster <br><br> * Read/write access to resources in a namespace<br> * No read/write access to roles and role bindings<<br> * Access the Kubernetes dashboard to view resources in a namespace.<br><br><br>
Restoring it back to a working state might not be easy.



 Architecture diagram 

The following diagram depicts a Spectrum Symphony cluster that uses NFS for shared storage. For a view of a cluster that uses Spectrum Scale, see the [Using Spectrum Scale storage](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-using-spectrum-scale-storage) section.

Zoom

![Architecture diagram](https://cloud.ibm.com/docs-content/v1/content/7a8d1342aca7be29e4771ffe1bc72ebc54df73dc/hpc-spectrum-symphony/images/hpccluster-sym-schematics-architecture.png)

Figure 1. Architecture diagram of an IBM Spectrum Symphony cluster on IBM Cloud
(https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-monitoringibm_databases_for_elasticsearch_cpu_used_percent) 
 [Used JVM heap for a database member of the instance in percent.](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-monitoringibm_databases_for_elasticsearch_jvm_heap_percent) 
 [Used disk space for an instance.](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-monitoringibm_databases_for_elasticsearch_disk_used_bytes) 
 [Used memory for an instance.](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-monitoringibm_databases_for_elasticsearch_memory_used_bytes) 





 Cluster status 

A number derived from the status value of the /_cluster/health endpoint. Possible Values: 'green' = 1.0, 'yellow' = 0.5, 'red' = 0, ERROR = -1.



Table 2. Cluster status metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_elasticsearch_cluster_status 
 Metric Type gauge 
 Value Type count 
 Segment By Service instance 







 Disk read latency mean 

Disk read latency mean



Table 3: Disk read latency mean metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_elasticsearch_disk_read_latency_mean 
 Metric Type gauge 
 Value Type count 
 Segment By Service instance 







 Disk write latency mean 

Disk write latency mean



Table 4: Disk write latency mean metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_elasticsearch_disk_write_latency_mean 
 Metric Type gauge 
 Value Type count 
 Segment By Service instance 







 GC Percentage
To continue receiving logs for clusters in these regions, you must create instances of IBM Cloud Activity Tracker and IBM Cloud Activity Tracker in the same region as your cluster. If you already have instances in these regions, look for logs in those instances.

IBM Cloud Object Storage
: Version 2.1.7 of the [IBM Cloud Object Storage plug-in](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog) is released.





 17 November 2021 

Worker node fix pack update
: Change log documentation is available for version [4.8.18_1535_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_484818_1535), [4.7.36_1539_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_474736_1539), [4.6.47_1563_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464647_1563), and [3.11.542_1611_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311542_1611).





 16 November 2021 

HPCS Router add-on
: Version 4.8.0_997 of the [HPCS Router add-on](https://cloud.ibm.com/docs/openshift?topic=openshift-hpcs-router-changelog) is released.





 15 November 2021 

CLI change log
: The [CLI change log](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelog) is updated for version 1.0.344.





 12 November 2021 

Master fix pack updates
Status pending
Created 2019-09-20T16:27:32-05:00
Zone us-south-1
VPC myvpc(36c8f522-4f0d-400c-8226-299f0b8198cf)
Resource group -
2. By using the IDs of the public gateway and the subnet, attach the public gateway to the subnet.

ibmcloud is subnet-update <subnet_ID> --public-gateway-id <gateway_ID>

Example output

ID 91e946b4-7094-46d0-9223-5c2dea2e5023
Name mysubnet1
IPv4 CIDR 10.240.xx.xx/24
Address available 250
Address total 256
ACL allow-all-network-acl-36c8f522-4f0d-400c-8226-299f0b8198cf(585bc142-5392-45d4-afdd-d9b59ef2d906)
Gateway mycluster-us-south-1-gateway(26466378-6065-4716-a90b-ac7ed7917c63)
Created 2019-08-21T09:43:11-05:00
Status available
Zone us-south-1
VPC myvpc(36c8f522-4f0d-400c-8226-299f0b8198cf)



6. Use the subnets to [create a cluster](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-vpc-gen2&interface=ui). Do not delete the subnets that you attach to your cluster during cluster creation or when you add worker nodes in a zone. If you delete a VPC subnet that your cluster used, any load balancers that use IP addresses from the subnet might experience issues, and you might be unable to create new load balancers.
The following examples show how you can use the attribute names in the CLI to build trusted profile links and conditions.



 Linking a trusted profile to Kubernetes a cluster 

To link the trusted profile Test to the Kubernetes cluster c0pigdctkkc07fs7pm06 in the account 444aebb0657c7f0f3aae8e7bdc78709a and service account my-service-account in the namespace my-namespace, specify the following command:

ibmcloud iam trusted-profile-link-create Test --name NewLink4IKS --cr-type IKS_SA                --link-crn 
crn:v1:bluemix:public:containers-kubernetes:us-east:a/444aebb0657c7f0f3aae8e7bdc78709a:c0pigdctkkc07fs7pm06::               --link-namespace "my-namespace"               --link-name "my-service-account"





 Creating trusted profile conditions for Kubernetes 

To connect the trusted profile with the ID Profile-b2f13064-2b8c-4e4b-9181-c1973a408e3c to all service accounts in the Kubernetes cluster c0pigdctkkc07fs7pm06 in the account 444aebb0657c7f0f3aae8e7bdc78709a and the service account namespace my-namespace, specify the following command:

ibmcloud iam trusted-profile-rule-create Profile-b2f13064-2b8c-4e4b-9181-c1973a408e3c               --name NewRule4IKS --type Profile-CR --cr-type IKS_SA                --conditions "claim:service_instance,operator:EQUALS,vlaue:c0pigdctkkc07fs7pm06"                --conditions "claim:namespace,operator:EQUALS,value:my-namespace"





 Creating trusted profile conditions for VPC
"crn": "crn:v1:bluemix:public:is:us-east-2:a/be636a7a6e4d4b6296bedf669ce8f757::load-balancer:r014-020f4f34-bb49-4699-98a7-a53384cd649d",
"is_public": false,
"created_at": "2021-09-14T21:45:06.377862525Z",
"hostname": "020f4f34-us-east.lb.appdomain.cloud",
"listeners": [],
"operating_status": "offline",
"pools": [],
"private_ips": [],
"provisioning_status": "create_pending",
"public_ips": [],
"subnets": [
  {
"id": "0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024",
"href": "https://us-east.iaas.cloud.ibm.com/v1/subnets/0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024",
"crn": "crn:v1:bluemix:public:is:us-east-2:a/be636a7a6e4d4b6296bedf669ce8f757::subnet:0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024",
"name": "nlb-subnet"
}
],
"resource_group": {
"id": "42c4f51adc3147b4b4049ad9826c30a1",
"name": "share-name1",
"profile": {
"family": "tiered",
"href": "https://us-south.iaas.cloud.ibm.com/v1/share/profiles/tier-10iops",
"name": "tier-10iops",
"resource_type": "share_profile"
},
"resource_group": {
"crn": "crn:...]",
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/60fc731a-1794-4f5d-ba51-ea24b5357207",
"id": "60fc731a-1794-4f5d-ba51-ea24b5357207",
"name": "Default"
},
"resource_type": "share",
"size": 40,
"mount_targets":
{
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares/51bba578-0dce-4f8a-aa6e-f06c899e2c8e/mount_targets/d5fd8173-f519-4ff7-8f63-0ead23ecf1f4",
"id": "d5fd8173-f519-4ff7-8f63-0ead23ecf1f4",
"name": "mount-target-name1",
"resource_type": "share_target",
"vpc": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/vpcs/c2d941de-27f5-432c-b4d0-37a8491c3216",
The following example deletes a placement group named PLACEMENT_GROUP.

terraform destroy -target=ibm_is_placement_group.is_placement_group





 Listing all placement groups with the UI 

You can generate a list of placement groups for a region.

To display a list of all existing placement groups:



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Placement Groups.
2. All existing placement groups are displayed.







 Listing all placement groups with the CLI 

You can generate a list of placement groups for a region. You can list all the existing placement group in your IBM Cloud VPC by using the command-line interface (CLI).

To list all the existing placement groups by using the CLI, use the ibmcloud is placement-groups command. Specify the name and ID of the resource group that you are listing placement groups.

The following example lists all the existing placement groups for the resource group ID RESOURCE_GROUP_ID and name RESOURCE_GROUP.

ibmcloud is placement-groups --resource-group-id RESOURCE_GROUP_ID --resource-group-name RESOURCE_GROUP_NAME --all-resource-groups --output JSON





 Listing all placement groups with the API 

You can generate a list of placement groups for a region. The following example generates a list of all placement groups.

curl -X GET "$vpc_api_endpoint/v1/placement_groups?version=2021-04-20&generation=2" -H "Authorization: $iam_token"





 Listing all placement groups with Terraform 

You can generate a list of placement groups for a region. You can list all the existing placement groups in your IBM Cloud VPC by using Terraform.

The following example lists all the existing placement groups.
ibmcloud is snapshots [--volume VOLUME] [--tag TAG_NAME] [--source-image SOURCE_IMAGE] [--backup-policy-plan BACKUP_POLICY_PLAN --backup-policy BACKUP_POLICY] [--clones-zone-name CLONES_ZONE_NAME] [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME | --all-resource-groups] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is snapshots
* ibmcloud is snapshots --volume r134-f13fc172-22e0-4e5b-ab81-63f5fe8b3ea0
* ibmcloud is snapshots --volume vol-bkp-policy-do-not-delete
* ibmcloud is snapshots --volume crn:v1:staging:public:is:us-south-2:a/efe5afc483594adaa8325e2b4d1290df::volume:r134-f13fc172-22e0-4e5b-ab81-63f5fe8b3ea0
* ibmcloud is snapshots --tag dev:env
* ibmcloud is snapshots --source-image r134-24d856e2-6aec-41c2-8f36-5a8a3766f0d6
* ibmcloud is snapshots --source-image ibm-centos-7-9-minimal-amd64-9
* ibmcloud is snapshots --source-image crn:v1:staging:public:is:us-east:a/efe5afc483594adaa8325e2b4d1290df::image:r134-24d856e2-6aec-41c2-8f36-5a8a3766f0d6
Command options:

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

--crn
: Required. The CRN of the IBM Cloud Secret Manager instance.

--name NAME
: Required. The name of the Secret Manager instance.

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

Example:

ibmcloud oc ingress instance default unset --cluster --cluster a111aaa11a1aaaaaaa1 --crn crn:v1:staging:public:secrets-manager:eu-gb:a/1a11a1a111aa11aa111aa1a1111aa1a1:1aaa1a1a-aaaa-11aa-1a11-a11aaa1a11a1:secret:a1a11a11-111a-11a1-aa11-11aaa1a11a11 --name my-secret-manager --namespace default





 ibmcloud oc ingress instance get 

Virtual Private Cloud

Classic infrastructure

View the details of a Secrets Manager instance.

ibmcloud oc ingress instance get --cluster CLUSTER --name NAME [--output OUTPUT] [-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.

--name NAME
: Required. The name of the Secret Manager instance.

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

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

Example:

ibmcloud oc ingress instance get --cluster my-cluster --name my-secrets-manager





 ibmcloud oc ingress instance ls 

Virtual Private Cloud

Classic infrastructure

List all Secrets Manager instances registered to a cluster.

ibmcloud oc ingress instance ls --cluster CLUSTER [--output OUTPUT] [-q] [--show-deleted]

Minimum required permissions
"subnets": [
{
"id": "0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024"
}
]
}

Sample output:

{
"id": "r014-eac21cde-a4ce-4980-b037-fc3507112955",
"name": "pdns-alb-example",
"href": "https://us-east.iaas.cloud.ibm.com/v1/load_balancers/r014-eac21cde-a4ce-4980-b037-fc3507112955",
"crn": "crn:v1:bluemix:public:is:us-east:a/be636a7a6e4d4b6296bedf669ce8f757::load-balancer:r014-eac21cde-a4ce-4980-b037-fc3507112955",
"is_public": false,
"created_at": "2023-02-13T18:58:12Z",
"hostname": "eac21cde-us-east.example.com",
"listeners": [],
"operating_status": "offline",
"pools": [],
"private_ips": [],
"provisioning_status": "create_pending",
"public_ips": [],
"subnets": [
{
"id": "0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024",
Use the following example for CLI.

ic iam access-group-policy-create Developers_MyApp --roles Viewer --service-name kms --tags abc:test







 Related links 

For more information about IAM, resource groups, access groups, and access management tags, see the following IBM Cloud topics:



* [IBM Cloud IAM](https://cloud.ibm.com/docs/account?topic=account-iamoverview)
* [Access groups](https://cloud.ibm.com/docs/account?topic=account-cloudaccess)
: New pages for [Preparing your cluster for autoscaling](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-scaling-classic-vpc), [Installing the cluster autoscaler add-on](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-install-addon), and [Enabling autoscaling](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-enable).
: New troubleshooting pages for [resizing worker pools](https://cloud.ibm.com/docs/containers?topic=containers-ts-ca-resize) and updating [unbalanced worker pools](https://cloud.ibm.com/docs/containers?topic=containers-ts-ca-unbalanced) in autoscaled clusters.

ALB OAuth Proxy add-on
: Versions 1.0.0_1001 and 2.0.0_999 of the [ALB OAuth Proxy add-on](https://cloud.ibm.com/docs/containers?topic=containers-alb-oauth-proxy-changelog) are released.

Worker node fix pack
: Kubernetes [1.23.4_1521](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1231234_1521), [1.22.7_1542](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1221227_1542), [1.21.10_1551](https://cloud.ibm.com/docs/containers?topic=containers-changelog_12112110_1551), [1.20.15_1572](https://cloud.ibm.com/docs/containers?topic=containers-changelog_12012015_1572), and [1.19.16_1579](https://cloud.ibm.com/docs/containers?topic=containers-changelog_11911916_1579).
[--copies-remote-region COPIES_REMOTE_REGION] [--source-snapshot SOURCE_SNAPSHOT] [--source-snapshot-remote-region SOURCE_SNAPSHOT_REMOTE_REGION] [--volume-remote-region VOLUME_REMOTE_REGION] [--source-image-remote-region SOURCE_IMAGE_REMOTE_REGION] [--backup-policy-plan BACKUP_POLICY_PLAN --backup-policy BACKUP_POLICY] [--clones-zone-name CLONES_ZONE_NAME] [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME | --all-resource-groups] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is snapshots
* ibmcloud is snapshots --volume r134-f13fc172-22e0-4e5b-ab81-63f5fe8b3ea0
* ibmcloud is snapshots --volume vol-bkp-policy-do-not-delete
* ibmcloud is snapshots --volume crn:v1:staging:public:is:us-south-2:a/efe5afc483594adaa8325e2b4d1290df::volume:r134-f13fc172-22e0-4e5b-ab81-63f5fe8b3ea0
* ibmcloud is snapshots --tag dev:env
* ibmcloud is snapshots --source-image r134-24d856e2-6aec-41c2-8f36-5a8a3766f0d6
* ibmcloud is snapshots --source-image ibm-centos-7-9-minimal-amd64-9
31 August 2022 

Cluster autoscaler add-on
: Versions 1.0.5_775, 1.0.6_774, and 1.1.0_776 are available. See [Cluster autoscaler add-on change log](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog).





 29 August 2022 

Worker node fix pack
: Kubernetes [1.21.14_1578](https://cloud.ibm.com/docs/containers?topic=containers-changelog_121), [1.22.13_1568](https://cloud.ibm.com/docs/containers?topic=containers-changelog_122), [1.23.10_1543](https://cloud.ibm.com/docs/containers?topic=containers-changelog_123) and [1.24.4_1535](https://cloud.ibm.com/docs/containers?topic=containers-changelog_124).





 26 August 2022 

CLI change log update
: The [CLI change log](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelog) is updated for version 1.0.439.





 25 August 2022 

Block Storage for VPC add-on version 4.4.9_1566 is available.
: For more information, see [version 4.4.9_1566](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog)

Ingress ALB change log updates
: Updated the [Ingress ALB change log](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelog) for versions 1.2.1_2506_iks and 1.1.2_2507_iks.





 24 August 2022 

Block Storage for VPC add-on version 4.3.5_1563 is available.