vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To add a breakdown, click on the arrow below the graph:



* Choose Histogram as your breakdown type.
* Choose level as your field type.
* Click Add Breakdown to see a breakdown with all the levels you logged for the app.











 Step 6: Validate IBM Cloud Monitoring instance configuration and monitor your cluster 

During creation of the IBM Cloud Kubernetes Service cluster, it is expected that you completed the steps to also connect to a Monitoring service. In the following, you are going to add IBM Cloud Monitoring to the application. The service regularly checks the availability and response time of the app.



1. From the [Kubernetes clusters](https://cloud.ibm.com/kubernetes/clusters), click on the name of the Kubernetes cluster you just created and click Overview on the left pane.
2. Scroll down to Integrations and open the Monitoring UI by clicking on the Launch button. It may take few minutes for the monitoring information to appear. If instead of Launch you see a Connect button, you can click on it to create the integration if it was not done during the creation of the cluster. It simplifies the installation of sysdig-agent pod on each node of your cluster. The agent captures metrics and forwards them to your monitoring instance.
3. To check whether the sysdig-agent pods on each node of your cluster are in Running status, run the below command in a shell:

kubectl get pods --namespace ibm-observe

You should see an output similar to the one below, with one sysdig-agent running per worker node that you have deployed in your cluster.

sysdig-agent-m6k9w 1/1 Running 0 73s
sysdig-agent-mp4d6 1/1 Running 0 73s
sysdig-agent-q2s55 1/1 Running 0 73s



Small clusters will result in pods in a Pending state. This can be adjusted by changing the daemon set:

kubectl edit daemonset/sysdig-agent -n ibm-observe
* The AdoptOpenJDK OpenJ9 alternate JRE was updated to version 11.0.9_11_openj9-0.23.0.
* The alternate Liberty runtime version 20.0.0.12 includes a fix for the [CVE-2020-10693 security vulnerability](https://www.ibm.com/support/pages/node/6348216).
* The IBM JRE Version (8 SR 6 FP16) remains unchanged







 22 October 2020 

Updated Liberty buildpack v3.50-20201019-1521
: The default Liberty runtime GA version is the [20.0.0.9](https://openliberty.io/blog/2020/08/28/graphql-apis-open-liberty-20009.html) release.



* The alternate Liberty runtime GA version is the [20.0.0.11](https://openliberty.io/blog/2020/10/23/kerberos-grafana-200011.html) release.
* The IBM JRE version is updated to 8 SR6 FP16.







 15 October 2020 

Updated Liberty buildpack v3.49.1-20201014-1251
: The default Liberty runtime GA version is the [20.0.0.9](https://openliberty.io/blog/2020/08/28/graphql-apis-open-liberty-20009.html) release.



* The alternate Liberty runtime GA version is the [20.0.0.10](https://openliberty.io/blog/2020/09/25/signed-certificate-with-acme-200010.html) release.
* This buildpack contains a DB2 service fixing:



* Liberty incompatibility issue with updated DB2 paid plans. It will allow users to create the paid plan of the service and bind the application with new VCAP service format.









 2 October 2020 

Updated Liberty buildpack v3.49-20200918-0244
Default limits and quotas for Analytics Engine instances 

The following sections provide details about the default limit and quota settings for IBM Analytics Engine serverless instances.

These default values are set to avoid excessive billing, however the values can be set to larger defaults based on user requirements by opening a support ticket.



  Application limits 

The following table lists the default limits and quotas for Analytics Engine instances.



Default limits and quotas for Analytics Engine instances

 Category                                 Default                           

 Maximum number of instances per account  5                                 
 Maximum cores per instance               150                               
 Maximum memory per instances             600 GB                            
 Shuffle space per core                   approx. 30 GB (Not customizable)  
 Maximum time applications can run        72 hours (Not customizable)       







  Supported Spark driver and executor vCPU and memory combinations 

The IBM Analytics Engine Standard serverless plan for Apache Spark supports only the following pre-defined Spark driver and executor vCPU and memory combinations.

These two vCPU to memory proportions are supported: 1 vCPU to 4 GB of memory and 1 vCPU to 8 GB of memory.

The following table shows the supported vCPU to memory size combinations.



Supported vCPU to memory size combinations

 1 : 2 ratio      1 : 4 ratio      1 : 8 ratio    

 1 vCPU x 2 GB    1 vCPU x 4 GB    1 vCPU x 8 GB  
 2 vCPU x 4 GB    2 vCPU x 8 GB    2 vCPU x 16 GB 
 3 vCPU x 6 GB    3 vCPU x 12 GB   3 vCPU x 24 GB 
 4 vCPU x 8 GB    4 vCPU x 16 GB   4 vCPU x 32 GB 
 5 vCPU x 10 GB   5 vCPU x 20 GB  
 6 vCPU x 12 GB   6 vCPU x 24 GB   6 vCPU x 48 GB 
 7 vCPU x 14 GB   7 vCPU x 28 GB  
 8 vCPU x 16 GB   8 vCPU x 32 GB  
 10 vCPU x 20 GB  10 vCPU x 40 GB 
 12 vCPU x 24 GB  12 vCPU x 48 GB 



The default vCPU to memory combinations are:



*  Default Spark driver size: 1vCPU and 4GB memory
*  Default Spark executor size: 1vCPU and 4GB memory
quasi_dists: [{0: 0.2490234375, 1: 0.2578125, 2: 0.2431640625, 3: 0.25}]

You can still access the Aer simulator through its dedicated Sampler. This can be handy for performing simulations with noise models. In this example, the simulation method has been updated to match the result from 3.a.

from qiskit_aer.primitives import Sampler as AerSampler import change!

sampler = AerSampler(run_options= {"method": "statevector"})

result = sampler.run(circuit, shots=1024).result()
quasi_dists = result.quasi_dists

>>> print("result: ", result)
>>> print("quasi_dists: ", quasi_dists)
result: SamplerResult(quasi_dists=[{1: 0.2802734375, 2: 0.2412109375, 0: 0.2392578125,
3: 0.2392578125}], metadata=[{'shots': 1024, 'simulator_metadata':
{'parallel_state_update': 16, 'parallel_shots': 1, 'sample_measure_time': 0.000409608,
'noise': 'ideal', 'batched_shots_optimization': False, 'remapped_qubits': False,
'device': 'CPU', 'active_input_qubits': 0, 1, 2, 3], 'measure_sampling': True,
'num_clbits': 4, 'input_qubit_map': 3, 3], 2, 2], 1, 1], 0, 0]], 'num_qubits': 4,
'method': 'statevector', 'fusion': {'applied': False, 'max_fused_qubits': 5,
'threshold': 14, 'enabled': True}}}])
Resource actions are indicated with the following symbols:
+ create

Terraform will perform the following actions:

ibm_is_floating_ip.fip1 will be created
+ resource "ibm_is_floating_ip" "fip1" {
...
}

ibm_is_instance.vsi1 will be created
+ resource "ibm_is_instance" "vsi1" {
...
}
}

ibm_is_vpc.vpc will be created
+ resource "ibm_is_vpc" "vpc" {
+ address_prefix_management = "auto"
...
}

Apply complete! Resources: 6 added, 0 changed, 0 destroyed.

Outputs:

sshcommand = ssh root@ibm_is_floating_ip.fip1.address





 Step 5: Analyzing the provisioned resource 



1. Log in to your VPC VSI by using the ssh command that is listed at the end of your command-line output of the previous step.

ssh root@52.118.150.55

Example output

The authenticity of host '52.116.134.139 (52.116.134.139)' can't be established.
ECDSA key fingerprint is SHA256:ZZRZY07mx3ccmnS5+Tip7eDDVSL7jlunPbANcrCeEYE.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '52.116.134.139' (ECDSA) to the list of known hosts.

-bash: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8): No such file or directory
[root@vpctestexample-vsi1 ]
2. You can verify that VPC and VSI are created by accessing your [IBM Cloud console](https://cloud.ibm.com).



* Click Navigation Menu icon > VPC Infrastructure > VPCs to view VPC named vpctestexample is created
* [Change log for master fix pack 4.9.25_1534_openshift, released 6 April 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_494.9.25_1534)
* [Change log for worker node pack 4.9.25_1532_openshift, released 28 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_494925_1532)
* [Change log for worker node pack 4.9.23_1530_openshift, released 14 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_494923_1530)
* [Change log for master fix pack 4.9.21_1528_openshift, released 3 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_494921_1528)
* [Change log for worker node fix pack 4.9.22_1529_openshift, released 28 February 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_494922_1529)
* [Change log for worker node fix pack 4.9.19_1526_openshift, released 14 February 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_494919_1526)
* [Change log for master fix pack 4.9.17_1525_openshift and worker node fix pack 4.9.17_1523_openshift, released 9 February 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_494917_1525)
CRI-O configuration N/A N/A CRI-O configuration now sets container network sysctl tuning for net.ipv4.tcp_keepalive_intvl to 15, net.ipv4.tcp_keepalive_probes to 6 and net.ipv4.tcp_keepalive_time to 40. 







 Change log for master fix pack 4.11.22_1540_openshift, released 30 January 2023 

The following table shows the changes that are in the master fix pack 4.11.22_1540_openshift. Master patch updates are applied automatically.



Changes since version 4.11.17_1535_openshift

 Component Previous Current Description 

 Calico Operator v1.27.16 v1.27.17 See the [Calico Operator release notes](https://github.com/tigera/operator/releases/tag/v1.27.17). 
 Cluster health image v1.3.14 v1.3.15 Updated Go dependencies and to Go version 1.19.4. 
 IBM Calico extension 1257 1280 Publish s390x image. 
 IBM Cloud Block Storage driver and plug-in v2.3.4 v2.3.6 Updated UBI images to 8.7-1031 
 IBM Cloud Controller Manager v1.24.8-3 v1.24.10-2 Updated to support the Kubernetes 1.24.10 release. Updated Go dependencies and to Go version 1.19.5. 
 IBM Cloud File Storage for Classic plug-in and monitor 421 425 Fixes for Fixing [CVE-2022-40303](https://nvd.nist.gov/vuln/detail/CVE-2022-40303) and [CVE-2022-40304](https://nvd.nist.gov/vuln/detail/CVE-2022-40303). 
 Key Management Service provider v2.5.12 v2.5.13 Updated Go dependencies and to Go version 1.19.4.
* [Change log for patch update 1.1.0_429, released 16 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog110429_ca)



* [Version 1.0.9](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog0109_ca_addon)



* [Change log for patch update 1.0.9_44, released 22 June 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog10944_ca)



* [Version 1.0.8](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog0108_ca_addon)



* [Change log for patch update 1.0.8_56, released 6 July 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog10856_ca)
* [Change log for patch update 1.0.8_1078, released 15 May 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog1081078_ca)
* [Change log for patch update 1.0.8_1016, released 5 April 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog1081016_ca)
* [Change log for patch update 1.0.8_987, released 29 March 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog108987_ca)
* [Change log for patch update 1.0.8_968, released 9 March 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog108968_ca)
Pods in the openshift-markeplace namespace are in ImagePullBackOff 

Virtual Private Cloud

 What’s happening 

In VPC clusters with worker nodes in a VPC subnet that doesn't have a public gateway, the pods in the openshift-markeplace namespace show a state of ImagePullBackOff and cannot reach Running state.

 Why it’s happening 

The images for these containers are hosted on a public image registry but the workers do not have access to the public internet, so the workers cannot to pull the image. The cluster still works, but these pods and the openshift marketplace does not work. If you run the kubectl get pods command, you get output such as:

NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
certified-operators-48dsc 0/1 ImagePullBackOff 0 4h6m 172.17.70.94 172.24.0.6 <none> <none>
certified-operators-s7qtb 0/1 ImagePullBackOff 0 4h17m 172.17.70.77 172.24.0.6 <none> <none>
community-operators-h7hl9 0/1 ImagePullBackOff 0 4h17m 172.17.70.78 172.24.0.6 <none> <none>
community-operators-hc76f 0/1 ImagePullBackOff 0 4h6m 172.17.70.96 172.24.0.6 <none> <none>
marketplace-operator-66c666bf74-gnltf 1/1 Running 0 4h43m 172.17.126.216 172.24.0.8 <none> <none>
redhat-marketplace-tfwwp 0/1 ImagePullBackOff 0 82s 172.17.126.226 172.24.0.8 <none> <none>
redhat-marketplace-zkvfc 0/1 ImagePullBackOff 0 4h6m 172.17.70.95 172.24.0.6 <none> <none>
myproj-eude 01234567-abcd-abcd-abcd-abcdabcd2222 active false eu-de default 27d
myproject 01234567-abcd-abcd-abcd-abcdabcd1111 active true us-south default 52d





 How can I see details about a project? 

From the Code Engine console, you can see details of a project by clicking the name of a project from the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects).

You can also run the [project get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-get) command to display details of a project. Replace PROJECT_NAME with the name of your project. If your project is selected as the current context, the output of this command includes details about limits and quota usage of Code Engine project resources. For more information about limits for projects, see [Project quotas](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limitsproject_quotas).

ibmcloud ce project get --name PROJECT_NAME

Example output

Getting project 'myproject'...
OK

Name: myproject
ID: 01234567-abcd-abcd-abcd-abcdabcd1111
Status: active
Selected: true
Region: us-south
Resource Group: default
Service Binding Service ID: ServiceId-1234abcd-abcd-abcd-1111-1a2b3c4d5e6f
Age: 52d
Created: Fri, 15 Jan 2021 13:32:30 -0500
Updated: Fri, 15 Jan 2021 13:32:45 -0500

Quotas:
Category Used Limit
App revisions 33 100
Apps 10 100
Build runs 4 100
Builds 4 100
Configmaps 7 100
CPU 6.15 64
Ephemeral storage 5415750Ki 256G
Instances (active) 6 250
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
ocs-storagecluster 72m Ready 2021-02-10T06:00:20Z 4.6.0
2. Get a list of pods in the openshift-storage namespace and verify that the status is Running.

oc get pods -n openshift-storage

Example output

NAME READY STATUS RESTARTS AGE
csi-cephfsplugin-9g2d5 3/3 Running 0 8m11s
csi-cephfsplugin-g42wv 3/3 Running 0 8m11s
csi-cephfsplugin-provisioner-7b89766c86-l68sr 5/5 Running 0 8m10s
csi-cephfsplugin-provisioner-7b89766c86-nkmkf 5/5 Running 0 8m10s
csi-cephfsplugin-rlhzv 3/3 Running 0 8m11s
csi-rbdplugin-8dmxc 3/3 Running 0 8m12s
csi-rbdplugin-f8c4c 3/3 Running 0 8m12s
csi-rbdplugin-nkzcd 3/3 Running 0 8m12s
csi-rbdplugin-provisioner-75596f49bd-7mk5g 5/5 Running 0 8m12s
csi-rbdplugin-provisioner-75596f49bd-r2p6g 5/5 Running 0 8m12s
noobaa-core-0 1/1 Running 0 4m37s
After the chart is deployed, verify that the updated settings in the config.yaml file were used.

helm get values vpn



Only strongSwan Helm chart versions that were released in the last 6 months are supported. Ensure that you consistently [upgrade your strongSwan Helm chart](https://cloud.ibm.com/docs/openshift?topic=openshift-vpnvpn_upgrade) for the latest features and security fixes.







 Testing and verifying strongSwan VPN connectivity 

After you deploy your Helm chart, test the VPN connectivity.



1. If the VPN on the on-premises gateway is not active, start the VPN.
2. Set the STRONGSWAN_POD environment variable.

export STRONGSWAN_POD=$(oc get pod -l app=strongswan,release=vpn -o jsonpath='{ .items[0].metadata.name }')
3. Check the status of the VPN. A status of ESTABLISHED means that the VPN connection was successful.

oc exec $STRONGSWAN_POD -- sudo ipsec status

Example output

Security Associations (1 up, 0 connecting):
k8s-conn[1]: ESTABLISHED 17 minutes ago, 172.30.xxx.xxx[ibm-cloud]...192.xxx.xxx.xxx[on-premises]
k8s-conn{2}: INSTALLED, TUNNEL, reqid 12, ESP in UDP SPIs: c78cb6b1_i c5d0d1c3_o
k8s-conn{2}: 172.21.0.0/16 172.30.0.0/16 === 10.91.152.xxx/26



* When you try to establish VPN connectivity with the strongSwan Helm chart, it is likely that the VPN status is not ESTABLISHED the first time. You might need to check the on-premises VPN endpoint settings and change the configuration file several times before the connection is successful.



1.
From the Overview page, click Event subscriptions to view a listing of defined subscriptions.



If your job prints information to log files, as the sample codeengine job does, then view the log files for your event consumer application. See [Viewing job logs from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logsview-joblog-cli).





 Viewing event information for a job with the CLI 

If your job prints information to log files, as the codeengine job does, then use the [ibmcloud ce jobrun logs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-logs) CLI command to view the information that was sent.

Before you can view event information for your job, you must first create an Object Storage event. Make a change to your bucket.

To find the job run for the job in the previous example,

ibmcloud ce jobrun list

Example output

Listing job runs...
OK

Name Failed Pending Requested Running Succeeded Unknown Age
myjob-pnz6m 0 0 0 0 1 0 39s

View the logs for the job run by specifying the job run name.

ibmcloud ce jobrun logs --jobrun myjob-pnz6m

Example output

Getting logs for all instances of job run 'myjob-pnz6m'...
Getting jobrun 'myjob-pnz6m'...
Getting instances of jobrun 'myjob-pnz6m'...
OK

myjob-pnz6m-0-0/myjob:
Hello from helloworld! I'm a batch job! Index: 0

Hello World from:
. ___ __ ____ ____
./ __)/ ( ( __)
( (__( O )) D ( ) _)
.___)__/(____/(____)
Change log for patch update 1.0.8_968, released 9 March 2023 



* Image tags: 1.20.0 108-0, 1.21.0 108-0, 1.22.0 108-0, 1.23.0 108-0, 1.24.0 108-0, 1.25.0 108-0, and 1.26.0 108-0
* Golang updated to 1.19.6
* Adds support for cluster version 1.26 based on the Kubernetes community [cluster-autoscaler](https://github.com/kubernetes/autoscaler/releases/tag/cluster-autoscaler-1.26.0).









 Version 1.0.7 



 Change log for patch update 1.0.7_57, released 6 July 2023 



* Image tags: 1.20.0 107-6, 1.21.0 107-6, 1.22.0 107-6, 1.23.0 107-6, 1.24.0 107-6,1.25.0 107-6.
* Updates the storage-secret-sidecar image to v1.2.21.
* Updates the golang version to 1.19.8.
* Fixes an issue where cluster-autoscaler stops retrying requests that return HTTP401 code.







 Change log for patch update 1.0.7_1076, released 15 May 2023 



* Image tags: 1.20.0 107-5, 1.21.0 107-5, 1.22.0 107-5, 1.23.0 107-5, 1.24.0 107-5,1.25.0 107-5.
* Updates the storage-secret-sidecar image to v1.2.21
* Golang updated to 1.19.8.
* Fixes issue where cluster-autoscaler stops retrying requests return HTTP401 code.







 Change log for patch update 1.0.7_1021, released 5 April 2023
print(model.forecast_at(120))

6.334135728495107

ts = tspy.time_series([float(i) for i in range(10)])

print(ts)

TimeStamp: 0 Value: 0.0
TimeStamp: 1 Value: 1.0
TimeStamp: 2 Value: 2.0
TimeStamp: 3 Value: 3.0
TimeStamp: 4 Value: 4.0
TimeStamp: 5 Value: 5.0
TimeStamp: 6 Value: 6.0
TimeStamp: 7 Value: 7.0
TimeStamp: 8 Value: 8.0
TimeStamp: 9 Value: 9.0

num_predictions = 5
model = tspy.forecasters.auto(8)
confidence = .99

predictions = ts.forecast(num_predictions, model, confidence=confidence)

print(predictions.to_time_series())

TimeStamp: 10 Value: {value=10.0, lower_bound=10.0, upper_bound=10.0, error=0.0}
TimeStamp: 11 Value: {value=10.997862810553725, lower_bound=9.934621260488143, upper_bound=12.061104360619307, error=0.41277640121597475}
TimeStamp: 12 Value: {value=11.996821082897318, lower_bound=10.704895525154571, upper_bound=13.288746640640065, error=0.5015571318964149}
TimeStamp: 13 Value: {value=12.995779355240911, lower_bound=11.50957896664928, upper_bound=14.481979743832543, error=0.5769793776877866}
* [Change log for patch update 1.0.8_987, released 29 March 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog108987_ca)
* [Change log for patch update 1.0.8_968, released 9 March 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog108968_ca)



* [Version 1.0.7](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog0107_ca_addon)



* [Change log for patch update 1.0.7_57, released 6 July 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog10757_ca)
* [Change log for patch update 1.0.7_1076, released 15 May 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog1071076_ca)
* [Change log for patch update 1.0.7_1021, released 5 April 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog1071021_ca)
* [Change log for patch update 1.0.7_988, released 29 March 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog107988_ca)
* [Change log for patch update 1.0.7_956, released 7 March 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog107956_ca)
For more information about data center closures and recommended data centers, see [Data center consolidations](https://cloud.ibm.com/docs/get-support?topic=get-support-dc-closure).

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.1.2_2084_iks, 1.1.1_2085_iks, and 0.49.3_2083_iks.

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.394.





 6 April 2022 

Master fix pack update
: Kubernetes [1.23.5_1525](https://cloud.ibm.com/docs/containers?topic=containers-changelog_123), [1.22.8_1547](https://cloud.ibm.com/docs/containers?topic=containers-changelog_122), [1.21.11_1555](https://cloud.ibm.com/docs/containers?topic=containers-changelog_121), and [1.20.15_1576](https://cloud.ibm.com/docs/containers?topic=containers-changelog_120).







 March 2022 



 30 March 2022 

Cluster autoscaler add-on
: Version [1.1.0_475](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog) is available.

Kubernetes Service 1.20 end of support date change
: The end of support date of Kubernetes Service 1.20 is now 15 June 2022.