vania-janet/multiturn-rag-retrieval-data huggingface dataset:
(https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) 
 Agent plan ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) 
 Agent update ![Check mark icon.](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/checkmark.svg) ![Check mark icon.]
HPCS Router add-on
: Versions 4.6.0_1383, 4.7.0_1386, 4.8.0_1385, and 4.9.0_1384 of the [HPCS Router add-on](https://cloud.ibm.com/docs/openshift?topic=openshift-hpcs-router-changelog) are released. Cloud Image Key Synchronizer add-on
: Version 1.0.0_906 of the [Cloud Image Key Synchronizer add-on](https://cloud.ibm.com/docs/openshift?topic=openshift-image-key-synchronizer-changelog) is released.





 22 March 2022 

Hong Kong (HKG02) and Seoul (SEO01) are deprecated and become unsupported later this year.
: To prevent any interruption of service, [redeploy your cluster workloads](https://cloud.ibm.com/docs/openshift?topic=openshift-update_appcopy_apps_cluster) to a [supported data center](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneszones-mz) and remove your Hong Kong (HKG02) and Seoul (SEO01) clusters by 28 September 2022. Clusters remaining in these data centers after 28 September 2022 will be removed. Cluster creation in these locations will be stopped on 29 April 2022. 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_2050_iks, 1.1.1_1996_iks, and 0.49.3_1994_iks.





 21 March 2022
* A blog post, for example: [Messages for RabbitMQ 3.8 End of Life in July 2022](https://www.ibm.com/cloud/blog/announcements/messages-for-rabbitmq-38-end-of-life-in-july-2022)
* An announcement in your service's Release Notes, for example: [IBM Cloud® Messages for RabbitMQ 3.8 End of Life in July 2022](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-rabbitmq-relnotesmessages-for-rabbitmq-25jan2022)
* A notification by email through the IBM Cloud Databases API. This email contains a Notifications link that takes you to a Notifications Management page. Make sure that these announcements are not being caught by your email service's spam filter. For more information, see [Setting up Distribution Lists for IBM Cloud Notifications](https://www.ibm.com/cloud/blog/announcements/setting-up-distribution-lists-for-ibm-cloud-notifications).



For more information, see [Programmatic Methods for Checking Version Status](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-versioning-policy-major-version-eol-check-version-status).



 Programmatic Methods for Checking Version Status 

The following [IBM Cloud Databases deployables command](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployables-show) shows deployable database types, specifically the available versions of databases, and their preferred or stable status.

ibmcloud cdb deployables-show [--stable] [--preferred] [--json]

Check the status of a major version by reviewing the output of the deployable command, specifically Status and Preferred. The following output example shows that version 4.4 is the Preferred version and version 4.2's Status is deprecated.

Database Type: mongodb
Version Status Preferred
* A blog post, for example: [Messages for RabbitMQ 3.8 End of Life in July 2022](https://www.ibm.com/cloud/blog/announcements/messages-for-rabbitmq-38-end-of-life-in-july-2022)
* An announcement in your service's Release Notes, for example: [IBM Cloud® Messages for RabbitMQ 3.8 End of Life in July 2022](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-rabbitmq-relnotesmessages-for-rabbitmq-25jan2022)
* A notification by email through the IBM Cloud Databases API. This email contains a Notifications link that takes you to a Notifications Management page. Make sure that these announcements are not being caught by your email service's spam filter. For more information, see [Setting up Distribution Lists for IBM Cloud Notifications](https://www.ibm.com/cloud/blog/announcements/setting-up-distribution-lists-for-ibm-cloud-notifications).



For more information, see [Programmatic Methods for Checking Version Status](https://cloud.ibm.com/docs/databases-for-mongodb?topic=databases-for-mongodb-versioning-policy-major-version-eol-check-version-status).



 Programmatic Methods for Checking Version Status 

The following [IBM Cloud Databases deployables command](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployables-show) shows deployable database types, specifically the available versions of databases, and their preferred or stable status.

ibmcloud cdb deployables-show [--stable] [--preferred] [--json]

Check the status of a major version by reviewing the output of the deployable command, specifically Status and Preferred. The following output example shows that version 4.4 is the Preferred version and version 4.2's Status is deprecated.

Database Type: mongodb
Version Status Preferred
job: "ansible-playbook -i /swlib/ansible/hosts /swlib/ansible/airgap.yml --tags open >>/swlib/ansible/airgap.log"
tags: set

- name: Create the airgap-close cron job
ansible.builtin.cron:
name: airgap-close
weekday: ""
minute: ""
hour: "5"
job: "ansible-playbook -i /swlib/ansible/hosts /swlib/ansible/airgap.yml --tags close >>/swlib/ansible/airgap.log"
tags: set

- name: Delete the airgap-open cron job
ansible.builtin.cron:
name: airgap-open
state: absent
tags: cancel

- name: Delete the airgap-close cron job
ansible.builtin.cron:
name: airgap-close
state: absent
tags: cancel
Show more

If you are creating the cyber-recovery isolated recovery environment solution architecture, then see [Production environment configuration](https://cloud.ibm.com/docs/vmwaresolutions/?topic=vmwaresolutions-veeam-cr-sag-ireprod) for details.





 Related links 



* [Cyber recovery with Veeam architecture overview](https://cloud.ibm.com/docs/vmwaresolutions/?topic=vmwaresolutions-veeam-cr-sa-overview)
* [Juniper vSRX overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-juniper-overview)
* [Managing Juniper vSRX](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-juniper-managing)
* A blog post, for example: [Messages for RabbitMQ 3.8 End of Life in July 2022](https://www.ibm.com/cloud/blog/announcements/messages-for-rabbitmq-38-end-of-life-in-july-2022)
* An announcement in your service's Release Notes, for example: [IBM Cloud® Messages for RabbitMQ 3.8 End of Life in July 2022](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-rabbitmq-relnotesmessages-for-rabbitmq-25jan2022)
* A notification by email through the IBM Cloud Databases API. This email contains a Notifications link that takes you to a Notifications Management page. Make sure that these announcements are not being caught by your email service's spam filter. For more information, see [Setting up Distribution Lists for IBM Cloud Notifications](https://www.ibm.com/cloud/blog/announcements/setting-up-distribution-lists-for-ibm-cloud-notifications).



For more information, see [Programmatic Methods for Checking Version Status](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=cloud-databases-versioning-policy-major-version-eol-check-version-status).



 Programmatic Methods for Checking Version Status 

The following [IBM Cloud Databases deployables command](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployables-show) shows deployable database types, specifically the available versions of databases, and their preferred or stable status.

ibmcloud cdb deployables-show [--stable] [--preferred] [--json]

Check the status of a major version by reviewing the output of the deployable command, specifically Status and Preferred. The following output example shows that version 4.4 is the Preferred version and version 4.2's Status is deprecated.

Database Type: mongodb
Version Status Preferred
4.4 stable true
* Node.js 8 is deprecated.



* [9 March 2020](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-mar920)



* New Functions CLI version 1.0.38.
* Updated trigger parameters for CLI.
* Updated troubleshooting information for Node.js.





* [December 2019](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-dec19)



* [18 December 2019](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-dec1819)



* New environmental variable: __OW_TRANSACTION_ID.
* Updated information for packaging your Python code.



* [5 December 2019](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-dec519)



* Improved documentation for the quick start templates.
* Updated the API endpoints documentation.





* [November 2019](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-nov19)



* [18 November 2019](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-nov1819)



* New Functions CLI version 1.0.36.





* [October 2019](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-oct19)
* A blog post, for example: [Messages for RabbitMQ 3.8 End of Life in July 2022](https://www.ibm.com/cloud/blog/announcements/messages-for-rabbitmq-38-end-of-life-in-july-2022)
* An announcement in your service's Release Notes, for example: [IBM Cloud® Messages for RabbitMQ 3.8 End of Life in July 2022](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-rabbitmq-relnotesmessages-for-rabbitmq-25jan2022)
* A notification by email through the IBM Cloud Databases API. This email contains a Notifications link that takes you to a Notifications Management page. Make sure that these announcements are not being caught by your email service's spam filter. For more information, see [Setting up Distribution Lists for IBM Cloud Notifications](https://www.ibm.com/cloud/blog/announcements/setting-up-distribution-lists-for-ibm-cloud-notifications).



For more information, see [Programmatic Methods for Checking Version Status](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-versioning-policy-major-version-eol-check-version-status).



 Programmatic Methods for Checking Version Status 

The following [IBM Cloud Databases deployables command](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployables-show) shows deployable database types, specifically the available versions of databases, and their preferred or stable status.

ibmcloud cdb deployables-show [--stable] [--preferred] [--json]

Check the status of a major version by reviewing the output of the deployable command, specifically Status and Preferred. The following output example shows that version 4.4 is the Preferred version and version 4.2's Status is deprecated.

Database Type: mongodb
ibmcloud is instance-group-manager-action-update INSTANCE_GROUP MANAGER ACTION (--run-at RUN_AT | --cron CRON) [--membership-count MEMBERSHIP_COUNT | (--min-members MIN_MEMBERS --max-members MAX_MEMBERS)] [--name NEW_NAME] [--output JSON] [-q, --quiet]



Where:



* INSTANCE_GROUP: is the ID of the instance group.
* MANAGER is the ID of the manager.
* ACTIONis the ID of the action.
* --run-atis the date and time that is specified for the scheduled action. The format is in ISO 8601 format. Example: 2024-03-05T15:31:50.701Z or 2024-03-05T15:31:50.701+8:00.
* --cron is the cron specification for a recurring scheduled action.
* --membership-count is the number of members in the instance group that you want at the scheduled time.
* --min-members is the minimum number of members in the instance group that you want at the scheduled time. Range 1-100.
* --max-members: The maximum number of members in the instance group that you want at the scheduled time. Range 1-100.
* --name is the new name of the instance group manager action.
* --output specifies output format, only JSON is supported. One of: JSON.
* -q, --quietsuppresses verbose output.







 Delete a scheduled action 

Use the following command to delete a scheduled action.

ibmcloud is instance-group-manager-action-delete INSTANCE_GROUP MANAGER ACTION [--output JSON] [-f, --force] [-q, --quiet]



Where:



* INSTANCE_GROUP: is the ID of the instance group.
* MANAGER is the ID of the manager.
* ACTIONis the ID of the action.
* --output specifies output format, only JSON is supported. One of: JSON.
In the Shared Cluster deployment (otherwise known as MAS-MAS), Red Hat OpenShift will be shared across multiple Production Instance(s), Non-Production Instance(s) and Clients. Clients choosing the Shared Cluster deployment will be subject to the software upgrade policy that is set by IBM SRE. IBM will determine and communicate when upgrades will occur, and no deferrals or exceptions will be allowed.





 Maintenance Windows 

Standard maintenance windows for Production environments are planned on weekends (Saturday / Sunday). Non-Production environment maintenance is performed on weekdays.

The IBM SRE team will proactively notify customers at least 5 business days prior to any Non-Production maintenance and 10 business days prior to any Production maintenance via the [Client Communications Center (CCC)](https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-client-communications-center).

Systems are usually not available to users during maintenance windows, but the following maintenance categories will be applied as needed:



* Outage - systems will not be available to users during the scheduled window
* Low Impact - users may experience a brief period of intermittent connectivity (up to 15 mins) during the scheduled window
* No Outage - maintenance will be performed, but it will not impact users







 Change Freeze Period 

The Change Freeze period for year end 2023 is December 16, 2023 through January 2, 2024. Systems are available to users and all standard automated processes such as database backups continue as normal during the change freeze period. Coordinated changes to environments such as application upgrades are not available during this time. The IBM SRE team does not schedule maintenance during the change freeze period.





 Upgrade Rules, Policy and Plans 

Application and MAS component Upgrades are on a defined schedule based on the Maximo Application Suite release schedule and complexity of the upgrade. Upgrades will be deployed first to non-production and then scheduled for production. The upgrade window duration will depend on the size and complexity of the upgrade isd will be communicated through the [Client Communications Center (CCC)](https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-client-communications-center).
* IBM Cloud Schematics job queue process
* Schematics Actions APIs enhances the credentials parameter
* Schematics introduces compact flag in the workspace create and update API
* Importance of location and URL endpoint in workspace creation





* [August 2021](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesaug-2021)



* Review the release notes for August 2021.
* [27 August 2021](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-aug272021)



* Workspace update command enhancement
* Terraform v1.0 support
* IBM Cloud Schematics support job queue logs enhancement



* [11 August 2021](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-aug112021)



* IBM Cloud Schematics deprecates older version of Terraform





* [July 2021](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesjuly-2021)



* Review the release notes for July 2021.
* [30 July 2021](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-jul302021)



* IBM Cloud Schematics deprecates Terraform v0.11
* Terraform v0.15 support
* Ansible v2.9.23 API and command-line support



* [19 July 2021](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-jul192021)



* Support parallelism and other environment variables in IBM Cloud Schematics
* A blog post, for example: [Messages for RabbitMQ 3.8 End of Life in July 2022](https://www.ibm.com/cloud/blog/announcements/messages-for-rabbitmq-38-end-of-life-in-july-2022)
* An announcement in your service's Release Notes, for example: [IBM Cloud® Messages for RabbitMQ 3.8 End of Life in July 2022](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-rabbitmq-relnotesmessages-for-rabbitmq-25jan2022)
* A notification by email through the IBM Cloud Databases API. This email contains a Notifications link that takes you to a Notifications Management page. Make sure that these announcements are not being caught by your email service's spam filter. For more information, see [Setting up Distribution Lists for IBM Cloud Notifications](https://www.ibm.com/cloud/blog/announcements/setting-up-distribution-lists-for-ibm-cloud-notifications).



For more information, see [Programmatic Methods for Checking Version Status](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-versioning-policy-major-version-eol-check-version-status).



 Programmatic Methods for Checking Version Status 

The following [IBM Cloud Databases deployables command](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployables-show) shows deployable database types, specifically the available versions of databases, and their preferred or stable status.

ibmcloud cdb deployables-show [--stable] [--preferred] [--json]

Check the status of a major version by reviewing the output of the deployable command, specifically Status and Preferred. The following output example shows that version 4.4 is the Preferred version and version 4.2's Status is deprecated.

Database Type: mongodb
Version Status Preferred
[Job queuing in Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-job-queue-processjob-queue-process)



* [About the Schematics job queue](https://cloud.ibm.com/docs/schematics?topic=schematics-job-queue-processabout-job-queue)
* [Functioning of job queue](https://cloud.ibm.com/docs/schematics?topic=schematics-job-queue-processfunctions-job-queue)
* [When does the job enter into the pending queue?](https://cloud.ibm.com/docs/schematics?topic=schematics-job-queue-processpending-job-queue)
* [Timeout](https://cloud.ibm.com/docs/schematics?topic=schematics-job-queue-processjob-queue-timeout)







 Deleting Schematics data 

[Deleting Schematics data](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-schematics-data-introdelete-schematics-data-intro)



* [Scope](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-schematics-data-introdelete-schematics-data-scope)
* [Deleting Schematics objects from UI](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-schematics-data-introdelete-schematics-data-ui)



* [Workspaces](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-schematics-data-introdelete-schematics-data-wkscategory)
: See [Setting access policies](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-iam).







 March 2020 



 24 March 2021 

Node.js 8 is deprecated.
: See [Runtimes](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-runtimes).





 9 March 2020 

New Functions CLI version 1.0.38.
: See [CLI version history](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-cli_versions).

Updated trigger parameters for CLI.
: See [Trigger commands](https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli-plugin-functions-clicli_trigger).

Updated troubleshooting information for Node.js.
: See [Troubleshooting Node.js issues](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-troubleshooting).







 December 2019 



 18 December 2019 

New environmental variable: __OW_TRANSACTION_ID.
: See [Environment variables for actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_envvars).

Updated information for packaging your Python code.
: See [How do I package my Python app for deployment in Cloud Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prephow_to_package_python).





 5 December 2019 

Improved documentation for the quick start templates.
: See [Deploying quick start templates](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-templates).

Updated the API endpoints documentation.
For more information about Kubernetes project version 1.20, see [Kubernetes documentation](https://kubernetes.io/docs/home/).



 Release timeline 

The following table includes the expected release timeline for version 1.20 of IBM Cloud® Kubernetes Service. You can use this information for planning purposes, such as to estimate the general time that the version might become unsupported.

Dates that are marked with a dagger (†) are tentative and subject to change.



Release timeline for IBM Cloud Kubernetes Service version 1.20

 Version Supported? IBM Cloud Kubernetes Service <br>release date IBM Cloud Kubernetes Service <br>unsupported date 

 1.20 Unsupported 16 Feb 2021 19 June 2022 







 Preparing to update 

This information summarizes updates that are likely to have and impact on deployed apps when you update a cluster to version 1.20. For a complete list of changes, review the [community Kubernetes change log](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.20.md) and [IBM version change log](https://cloud.ibm.com/docs/containers?topic=containers-changelog_120) for version 1.20. You can also review the [Kubernetes helpful warnings](https://kubernetes.io/blog/2020/09/03/warnings/).



 Update before master 

The following table shows the actions that you must take before you update the Kubernetes master.



Changes to make before you update the master to Kubernetes 1.20

 Type Description 

 Kubernetes snapshot CRDs IBM Cloud Kubernetes Service installs Kubernetes snapshot custom resource definition (CRD) version v1beta1. If you use other Kubernetes snapshot CRD versions v1 or v1alpha1, you must change the version to v1beta1.
* Worker node fix pack update.



* [24 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-mar2422)



* IBM Cloud Object Storage plug-in
* Block Storage for VPC add-on.
* HPCS Router add-on
* Cloud Image Key Synchronizer add-on



* [22 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-mar2222)



* Hong Kong (HKG02) and Seoul (SEO01) are deprecated and become unsupported later this year.
* Ingress ALB change log updates



* [21 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-mar2122)



* CLI change log update



* [17 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-mar1722)



* Block Storage for VPC add-on.



* [14 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-mar1422)



* Worker node fix pack update.
* HPCS Router add-on



* [11 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-mar1122)



* IBM Cloud Object Storage plug-in



* [10 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-mar1022)



* Cluster autoscaler
* IBM Cloud Object Storage plug-in