vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Review the worker nodes' state and status](https://cloud.ibm.com/docs/containers?topic=containers-debug_worker_nodes).<br><br><br> 
 <br><br> * <br><br><br> Enabling The add-on is currently deploying to the cluster. Note that the add-on might take up to 15 minutes to install. 
 H1512 Addon daemonset may not be available on all Ready nodes. For the static route add-on: The static route operator DaemonSet is not available on any worker nodes, which prevents you from applying static route resources. Your worker nodes can't run the static route operator DaemonSet for the following reasons:<br><br><br><br> * One or more worker nodes reached their [resource limits](https://cloud.ibm.com/docs/containers?topic=containers-debug_worker_nodes).<br> * One or more worker nodes are running the [maximum number of pods per worker node](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_limitationsclassic_limits).<br><br><br> 







 Supported add-ons for clusters in Satellite locations 

Review which managed add-ons are available for Red Hat OpenShift clusters that are created in an IBM Cloud Satellite location.

The following list of add-ons for clusters are supported in Satellite locations.



* [Diagnostics and Debug Tool](https://cloud.ibm.com/docs/openshift?topic=openshift-debug-tool)
* [HPCS Router](https://cloud.ibm.com/docs/openshift?topic=openshift-hpcs-router-changelog)
* [Image Key Synchronizer](https://cloud.ibm.com/docs/openshift?topic=openshift-imagesencrypted-images)
* Deprecated: [Kubernetes web terminal](https://cloud.ibm.com/docs/containers?topic=containers-cli-install)
Liberty for Java buildpack defaults 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).

The Liberty buildpack is updated frequently in IBM Cloud®. Each release might contain security fixes or feature enhancements.

The buildpack has default values for settings such as the Java version or Liberty feature set for WAR or EAR apps. Some of the default values might change between the buildpack release, which might adversely impact the app. To prevent the app from being affected by the change in buildpack defaults, take steps to configure your app to avoid relying on the buildpack defaults.



 Liberty versions 

The buildpack provides two versions of the Liberty runtime:



1. A long-term stable release



* It is the default Liberty runtime.
* It does not provide any [beta features](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-using_beta_features).
* Typically updated on a quarterly basis.



2. The monthly release



* It must be explicitly enabled by setting the JBP_CONFIG_LIBERTY environment variable with the version: + value and the IBM_LIBERTY_MONTHLY environment variable with true.
* It provides [monthly features](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-using_monthly_runtime).
* Typically updated every 4 weeks.









 Liberty features 

When you deploy WAR or EAR files, the buildpack provides a configuration for the app with a default set of Liberty features. Although rare, that default set of Liberty features might change between the buildpack releases. The change in the default feature set might adversely affect the app. There are options to ensure that the app is not affected by the change in the feature defaults.



* Set the JBP_CONFIG_LIBERTY environment variable to explicitly specify a list of enabled features for the app.
: As part of work done to fully support Identity and Access Management (IAM) authentication, the endpoint that you use to access your Discovery service programmatically is changing. The old endpoint URLs are deprecated and will be retired on 26 May 2021. Update your API calls to use the new URLs.

The pattern for the endpoint URL changed from gateway-{location}.watsonplatform.net/discovery/api/ to api.{location}.discovery.watson.cloud.ibm.com/. The domain, location, and offering identifier are different in the new endpoint. For more information, see [Updating endpoint URLs from watsonplatform.net](https://cloud.ibm.com/docs/watson?topic=watson-endpoint-change).

If your service instance API credentials use the old endpoint, create a new credential and start using it today. After you update your custom applications to use the new credential, you can delete the old one.





 19 March 2021 

Improved Web crawl connector
: You can use the Web crawl collection type to connect to content that is stored on an internal company website. For more information, see [Web crawl](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-web-cloud).





 4 March 2021 

New drag and drop feature when uploading
: Upload collections now support dragging and dropping documents before and during document upload. For more information, see [Uploading data](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-upload-data).

New list view for collections
: You can view a list of collections that are connected to a particular gateway. For more information, see [Viewing collections connected to a gateway](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-sourcesgateway-connection).





 17 December 2020 

Improved date and time display on Activity tab
: Each collection now displays the Next sync scheduled for date and time on the Activity tab of the Manage collections page.

New beta FAQ extraction
"name": "url",
"value": "api.example.com/"
}
],
"threshold": 60,
"period": 900,
"correlate": {
"by": "nat"
},
"action":
{
"mode": "simulate",
"timeout": 86400,
"response": {
"content_type": "text/plain",
"body": "<error>This request has been rate-limited.</error>"
}
}
],
"match": {
"request": {
"methods":
"GET"
],
"schemes":
"HTTP",
"HTTPS"
],
"url": ".example.org/path"
},
"response": {
"status":
403, 401
],
"headers":
{
"name": "Cf-Cache-Status",
"op": "eq",
"value": "HIT"
}
] ! !
}
}
}
Show more
-s, --json-str: Deprecated. The JSON data describing a rate limiting rule.-j, --json-file: Deprecated. A file contains input JSON data.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-update-ratelimit-options" "> --><-- <section "id="section-update-ratelimit-examples" "> --> Examples Update rate limiting rule for domain 31984fea73a15b45779fa0df4ef62f9b.
Getting Started with Databases for DataStax 

IBM Cloud® Databases for DataStax is deprecated and no longer supported as of 30 June 2024. For more information, see the [deprecation details](https://cloud.ibm.com/docs/databases-for-cassandra?topic=databases-for-cassandra-deprecationdep_details).

This tutorial uses the IBM Cloud Dashboard to create an IBM Cloud® Databases for DataStax service instance. You also see essential information to enable your application to work with the database.

This tutorial is a short introduction to using an IBM Cloud® Databases for DataStax deployment.



 Step 1: Before you begin 



* You need to have an [IBM Cloud account](https://cloud.ibm.com/registration).







 Step 2: Create a service instance 



1. Navigate to the [IBM Cloud® Databases for DataStax service](https://cloud.ibm.com/databases/databases-for-cassandra/create) in the IBM Cloud Catalog.
2. Give your service a memorable name that will later appear in your account's Resource List.
3. Choose a resource group.
4. Choose a location.
5. Choose your resource allocation, using one of the provided templates or a custom allocation.
6. Configure your service.



* Database version
* Encryption
* Endpoints: Select which endpoints you'd like to be initially enabled, either public or private.



7. Click Create.

After you click Create, the system displays a message to say that the instance is being provisioned, which returns you to the Resource list. From the Resource list, you see that the status for your instance is, Provision in progress.
8. When the status changes to Active, select the instance.







 Step 3: Set your admin password 



* [Set the Admin Password](https://cloud.ibm.com/docs/databases-for-cassandra?topic=databases-for-cassandra-admin-password) for your deployment.
initializing - The replication was added to the scheduler, but isn't yet initialized or scheduled to run. The status occurs when a new or updated replication document is stored within the [_replicator database](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-replication-apithe-replicator-database).
2. error - The replication can't be turned into a job. This error might be caused in several different ways. For example, the replication must be [filtered](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-design-documentsfilter-functions), but it wasn't possible to fetch the filter code from the source database.
3. pending - The replication job is scheduled to run, but isn't yet running.
4. running - The replication job is running.
5. crashing - A temporary error occurred that affects the replication job. The job is automatically retried later.
6. completed - The replication job completed. This state doesn't apply to [continuous replications](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-replication-apicontinuous-replication).
7. failed- The replication job failed. The failure is permanent. This state means that no further attempt is made to replicate by using this replication task. The failure might be caused in several different ways, for example, if the source or target URLs aren't valid.



The transition between these states is illustrated in the following diagram:

Zoom

![The transition between states is , , , and .](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/images/fb85704.svg)

Figure 1. Replication Scheduler states

The scheduler introduces two new endpoints:
Managing deprecated SAML federation 

If you previously set up federation by using a SAML identity provider (IdP) in the SoftLayer customer portal, you can edit the IdP configuration data or delete it from the Identity providers page in the IBM Cloud® console.

This type of federation is deprecated. If you delete this configuration, it is permanent and you can't set it up again. You can now take advantage of federation with IBMid. For more information, see [Signing up with a federated ID](https://cloud.ibm.com/docs/account?topic=account-account-getting-started).

To edit your SAML configuration data, complete the following steps:



1.  In the IBM Cloud console, go to Manage > Access (IAM), and then select Identity providers.
2.  Click Edit.
3.  Change the information in the fields that you need to edit.
4.  Click Save.



To delete your deprecated SAML federation configuration, complete the following steps:



1.  In the IBM Cloud console, go to Manage > Access (IAM), and then select Identity providers.
2.  Click Delete.
3.  Select the option to confirm that you understand deleting the configuration is permanent. Since this type of federation is deprecated, it can't be set up again.
4.  Click Delete.
* The IBM Semeru Open J9 alternate JRE is changed to ibm-semeru-open-jre_x64_linux_11.0.15_10_openj9-0.32.0.



* To specify the alternate JRE set the following variable:

ibmcloud cf set-env myapp JBP_CONFIG_IBMJDK "version: 11.+"



* The IBM JRE version remains unchanged 8 SR7 FP6.







 31 May 2022 

IBM® Cloud Foundry is deprecated
: IBM announces the deprecation of IBM® Cloud Foundry. For more information, see [the deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecation).





 12 May 2022 

Updated Liberty buildpack v3.69-20220426-1537
: The alternate Liberty runtime GA version is changed to the 22.0.0.5 release. The default runtime remains the same [22.0.0.3](https://openliberty.io/blog/2022/03/15/sql-retries-22003.html).



* To specify the monthly runtime set the following two variables:

ibmcloud cf set-env <yourappname> JBP_CONFIG_LIBERTY "version: +"
ibmcloud cf set-env <yourappname> IBM_LIBERTY_MONTHLY true
* The IBM Semeru Open J9 alternate JRE remains the same ibm-semeru-open-jre_x64_linux_11.0.14.1_1_openj9-0.30.1.



* To specify the alternate JRE set the following variable:

ibmcloud cf set-env myapp JBP_CONFIG_IBMJDK "version: 11.+"



* The IBM JRE version is changed to 8 SR7 FP6.







 12 April 2022 

Updated Liberty buildpack v3.68-20220329-1120
* 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-etcd?topic=databases-for-etcd-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
4.2 deprecated false

The IBM Cloud Databases API deployables endpoint returns all deployable databases. Use the version parameter to return the version number.

GET /v5/ibm/deployables







 Minor versions
* 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-redis?topic=databases-for-redis-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
4.2 deprecated false

The IBM Cloud Databases API deployables endpoint returns all deployable databases. Use the version parameter to return the version number.

GET /v5/ibm/deployables







 Minor versions
For example, automated software agents attempting to modify one or both vSRX nodes. Configurations changes can corrupt the OS reload process. Additionally, these configuration changes are not preserved if a rollback is initiated.
* Before performing an OS reload upgrade on an HA cluster, run the command show chassis cluster status. The nodes should be clustered with one node that is listed as the primary and the other as secondary. Ensure that there are no monitor failures. If the cluster is not healthy prior to the upgrade, then the upgrade can fail, causing an extended traffic outage.

Example of a healthy cluster:

root@asloma-19-10g-ha1-vsrx-vSRX-Node0> show chassis cluster status
Monitor Failure codes:
CS Cold Sync monitoring FL Fabric Connection monitoring
GR GRES monitoring HW Hardware monitoring
IF Interface monitoring IP IP monitoring
LB Loopback monitoring MB Mbuf monitoring
NH Nexthop monitoring NP NPC monitoring
SP SPU monitoring SM Schedule monitoring
CF Config Sync monitoring RE Relinquish monitoring
IS IRQ storm

Cluster ID: 2
Node Priority Status Preempt Manual Monitor-failures

Redundancy group: 0 , Failover count: 1
node0 100 primary no no None
node1 1 secondary no no None

Redundancy group: 1 , Failover count: 1
node0 100 primary no no None
node1 1 secondary no no None

{primary:node0}

Example of an unhealthy cluster with monitor failures:

root@asloma-tc11-15-10g-pubpriv-ha1-vsrx-vSRX-Node1> show chassis cluster status
Monitor Failure codes:
CS Cold Sync monitoring FL Fabric Connection monitoring
GR GRES monitoring HW Hardware monitoring
IF Interface monitoring IP IP monitoring
LB Loopback monitoring MB Mbuf monitoring
NH Nexthop monitoring NP NPC monitoring
SP SPU monitoring SM Schedule monitoring
CF Config Sync monitoring
Cluster ID: 3
Node Priority Status Preempt Manual Monitor-failures

Redundancy group: 0 , Failover count: 1
node0 0 lost n/a n/a n/a
In the action settings page you, need to set the input variable as ansible_python_interpreter = auto as shown in the screen capture to avoid DEPRECATION WARNING message.

![Configuring input variable to silence warning message](https://cloud.ibm.com/images/advanced_inputvariable.png)

Configuring input variable to silence warning message
* How can I resolve that might not run action error while provisioning WinRM by using Schematics action?

Error: 2021/12/06 10:15:49 Terraform apply | Error: Error running command 'ANSIBLE_FORCE_COLOR=true ansible-playbook ansible.yml --inventory-file='inventory.yml' --extra-vars='{"ansible_connection":"winrm","ansible_password":"password","ansible_user":"administrator","ansible_winrm_server_cert_validation":"ignore"}' --forks=15 --user='root' --ssh-extra-args='-p 22 -o ConnectTimeout=120 -o ConnectionAttempts=3 -o StrictHostKeyChecking=no'': exit status 2. Output:
2021/12/06 10:15:49 Terraform apply | PLAY [!Please wait and have a coffee The show is about to begin....] 
2021/12/06 10:15:49 Terraform apply 
2021/12/06 10:15:49 Terraform apply | TASK [Gathering Facts] 
2021/12/06 10:15:49 Terraform apply | fatal: [161.156.161.7]: FAILED! => {"msg": "winrm or requests is not installed: No module named 'winrm'"}
2021/12/06 10:15:49 Terraform apply 
2021/12/06 10:15:49 Terraform apply | PLAY RECAP 
2021/12/06 10:15:49 Terraform apply | 161.156.161.7 : ok=0 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
"op": "eq",
"value": "HIT"
}
] ! !
}
}
}
Show more
-s, --json-st: Deprecated. The JSON data describing a rate limiting rule.-j, --json-file: Deprecated. A file contains input JSON data.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-create-ratelimit-options" "> --><-- <section "id="section-create-ratelimit-examples" "> --> Examples Create a rate limiting rule for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis ratelimit-rule-create 31984fea73a15b45779fa0df4ef62f9b --json '{"id":"372e67954025e0ba6aaa6d586b9e0b59","disabled":false,"description":"Prevent multiple login failures to mitigate brute force attacks","match":{"request":{"methods":"GET","POST"],"schemes":"HTTP","HTTPS"],"url":".example.org/path"},"response":{"status": 403, 401],"headers":{"name":"Cf-Cache-Status","op":"ne","value":"HIT"}]}},"bypass":{"name":"url","value":"api.example.com/"}] ! ! !
Note that the Ready field of the subscription shows false until the destination application or job is created. Then, the subscription moves to a Ready: true state automatically.

After the subscription is created, the subscription is repeatedly polled for status to verify its readiness. This polling lasts for 15 seconds by default before it times out. You can change the amount of time before the command times out by using the --wait-timeout option. You can also bypass the status polling by setting the --no-wait option to false.

You can display the status of your subscription by using the [subscription cron get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cron-get), [subscription cos get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-get) or the [subscription kafka get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-kafka-get) CLI commands.
: Fixes [Alpine vulnerabilities](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogfluentd_changelog).





 22 July 2019 

Version policy
: Increased the [version deprecation](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionscs_versions_available) period from 30 to 45 days.

Version change logs
: Updated the change logs for [1.14.4_1526](https://cloud.ibm.com/docs/containers?topic=containers-114_changelog1144_1526_worker), [1.13.8_1529](https://cloud.ibm.com/docs/containers?topic=containers-113_changelog1138_1529_worker), and [1.12.10_1560](https://cloud.ibm.com/docs/containers?topic=containers-112_changelog11210_1560_worker) worker node patch updates.

Version change log
: [Version 1.11is unsupported](https://cloud.ibm.com/docs/containers?topic=containers-111_changelog111_changelog).





 17 July 2019 

Ingress ALB change log
: Fixes [rbash vulnerabilities](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog).





 15 July 2019 

Cluster and worker node ID
: The ID format for clusters and worker nodes is changed. Existing clusters and worker nodes keep their existing IDs. If you have automation that relies on the previous format, update it for new clusters.



* Cluster ID: In the regex format {a-v0-9}7]{a-z0-9}[2]{a-v0-9}[11].
* Worker node ID: In the format: kube-<cluster_ID>-<cluster_name_truncated>-<resource_group_truncated>-<worker_ID>