vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you want to perform a blue-green instantaneous switch style update, set the maxSurge to 100%. The deployment creates all the new required replicas, then scales down the old version replicas to 0.
3. [Roll out](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/updating-a-deployment) a change. For example, you might want to change the image that you used in your initial deployment.



1. Get the deployment name.

kubectl get deployments
2. Get the pod name.

kubectl get pods
3. Get the name of the container that runs in the pod.

kubectl describe pod <pod_name>
4. Set the new image for the deployment to use.

kubectl set image deployment/<deployment_name><container_name>=<image_name>



When you run the commands, the change is immediately applied and logged in the roll-out history.
4. Check the status of your deployment.

kubectl rollout status deployments/<deployment_name>

If you notice something in the status that you want time to follow up on, you can pause and resume your rollout with the following commands.

kubectl rollout pause deployment <deployment_name>

kubectl rollout resume deployment <deployment_name>
5. Roll back a change.



1. View the roll-out history for the deployment and identify the revision number of your last deployment.

kubectl rollout history deployment/<deployment_name>

Tip: To see the details for a specific revision, include the revision number.

kubectl rollout history deployment/<deployment_name> --revision=<number>
2. Roll back to the previous version, or specify a revision. To roll back to the previous version, use the following command.

kubectl rollout undo deployment/<depoyment_name> --to-revision=<number>









 Setting up continuous integration and delivery
To run Code Engine commands, use ibmcloud code-engine or ibmcloud ce. To see everything that you can do with the Code Engine plug-in, run ibmcloud ce with no arguments.

ibmcloud ce



Optionally, you can install the [jq package](https://stedolan.github.io/jq). Many Code Engine commands include an option (--output JSON) to create JSON output. With this package, you can view and parse JSON responses from the command line.

For more information about Code Engine commands, see the [ibmcloud ce commands](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli).





 Updating the Code Engine CLI 

Update the CLI periodically to take advantage of new features.



1. View your current plug-in list by running the ibmcloud plugin list command.

ibmcloud plugin list

Example output

Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
code-engine[ce] 1.31.0 true
container-registry 0.1.571 true
container-service[kubernetes-service] 1.0.408 false
2. If an update is available, run the ibmcloud plugin update command.

ibmcloud plugin update code-engine







 Uninstalling the CLI 

If you no longer need the CLI, you can uninstall it.



1. List the plug-ins that are installed.

ibmcloud plugin list
2. Uninstall the plug-ins. For example, to uninstall the Code Engine CLI plug-in:

ibmcloud plugin uninstall code-engine
3. Verify the plug-ins were uninstalled by running the following command and checking the list of the plug-ins that are installed.

ibmcloud plugin list



The plug-ins that you deleted are not displayed in the results.





 Accessing the IBM Cloud Shell in your web browser
Find the TLS CA certificate that is the value of the cert parameter in the JSON file. This is your client-tls-cert for use in the commands below.



* peer tls-ca cert or orderer tls-ca cert

You can find the TLS CA certificate of the peer or orderer in the console.



1. Click the peer or orderer's node in the Node tab.
2. Click the Settings icon beside the node name.
3. Copy the node's TLS CA certificate string. This is your peer tls-ca cert or orderer tls-ca cert that can be used in the commands below.





Note: For all the certificates and keys, you must convert the certificate strings, which are in base64 format, to individual .pem files by using the following commands:


export FLAG=$(if [ "$(uname -s)" == "Linux" ]; then echo "-w 0"; else echo "-b 0"; fi)
echo <base64_string> | base64 --decode $FLAG > <key_name>.pem






 Checking node health 

Run the curl -k <peer-endpoint>/healthz or curl -k <orderer-endpoint>/healthz command to check the health of the peer or orderer node. For example:

curl -k https://169.46.208.93:3210/healthz

For more information about health checks, see [Health checks](https://hyperledger-fabric.readthedocs.io/en/release-2.2/operations_service.htmlhealth-checks).





 Viewing the metrics 

Run the following command to view the peer metrics. To view the orderer metrics you would run the same command but replace the <peer-endpoint> with the <orderer-endpoint>.

curl -k <peer-endpoint>/metrics --cert <client-tls-cert> --key <client-tls-key> --cacert <peer tls ca-cert>

For example:
Version 1.0.510 of the CLI was released on 11 April 2023.
: Adds support for Pod Security admission.
: Resolved an issue about config file race conditions.
: Updates the ibmcloud ks ingress domain create command output to return the full qualified domain.





 Version v1.0.498 

Version 1.0.498 of the CLI was released on 1 March 2023.
: Adds the ibmcloud ks cluster master pod-security get command.
: Updates the golang version to resolve [CVE-2022-41723](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-41723).
: Adds an Architecture field to the ibmcloud ks flavor get command output.
: Improves formatting of the ibmcloud ks ingress secret ls command output.
: When the ibmcloud ks cluster config command returns, you can run kubectl or oc commands immediately without a waiting period.





 Version 1.0.489 

Version 1.0.489 of the CLI was released on 30 January 2023.
: Adds a fix where table headings are no longer printed if the output of a command contains no results.
: Adds the --secondary-storage option to the cluster create vpc-gen2, worker-pool create vpc-gen2, and flavor get commands.





 Version 1.0.487 

Version 1.0.487 of the CLI was released on 24 January 2023.
: Adds the satellite-service-endpoint allowlist commands
: Updates the help text in various languages.





 Version 1.0.480 

Version 1.0.480 of the CLI was released on 14 December 2022.
: Adjusted ibmcloud ks flavor get and ibmcloud ks flavor ls commands to show secondary storage details.
: Introduced Secondary Storage Configuration for worker-pool get.
: Added Ignored Errors to ingress status-report.





 Version 1.0.471 

Version 1.0.471 of the CLI was released on 1 December 2022.
Version 1.0.510 of the CLI was released on 11 April 2023.
: Adds support for Pod Security admission.
: Resolved an issue about config file race conditions.
: Updates the ibmcloud oc ingress domain create command output to return the full qualified domain.





 Version v1.0.498 

Version 1.0.498 of the CLI was released on 1 March 2023.
: Adds the ibmcloud oc cluster master pod-security get command.
: Updates the golang version to resolve [CVE-2022-41723](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-41723).
: Adds an Architecture field to the ibmcloud oc flavor get command output.
: Improves formatting of the ibmcloud oc ingress secret ls command output.
: When the ibmcloud oc cluster config command returns, you can run kubectl or oc commands immediately without a waiting period.





 Version 1.0.489 

Version 1.0.489 of the CLI was released on 30 January 2023.
: Adds a fix where table headings are no longer printed if the output of a command contains no results.
: Adds the --secondary-storage option to the cluster create vpc-gen2, worker-pool create vpc-gen2, and flavor get commands.





 Version 1.0.487 

Version 1.0.487 of the CLI was released on 24 January 2023.
: Adds the satellite-service-endpoint allowlist commands
: Updates the help text in various languages.





 Version 1.0.480 

Version 1.0.480 of the CLI was released on 14 December 2022.
: Adjusted ibmcloud oc flavor get and ibmcloud oc flavor ls commands to show secondary storage details.
: Introduced Secondary Storage Configuration for worker-pool get.
: Added Ignored Errors to ingress status-report.





 Version 1.0.471 

Version 1.0.471 of the CLI was released on 1 December 2022.
Logging in to a RHCOS host machine to debug 

You might need to log in to your host machine to debug issues.

You can SSH into the host machine if you did not assign the host to a cluster, or if the assignment failed. Otherwise, Satellite disables the ability to log in to the host by using SSH for security purposes. You can [remove the host](https://cloud.ibm.com/docs/satellite?topic=satellite-host-remove) and reload the operating system to restore the ability to SSH into the host machine.



1. Download the host attach script and add your public SSH key.

{
"ignition": {
"version": "3.1.0"
},
"passwd": {
"users": [
{
"name": "core",
"sshAuthorizedKeys": "PUBLIC-SSH-KEY" ]
}
]
},
...
}
2. Log in to your host as core.

ssh core@<IP_address>
3. Run the following journalctl commands when you attempt to attach your host again to log the systemd service that is causing the issue.

journalctl -u ibm-host-attach --no-pager

journalctl -u ibm-host-agent --no-pager

journalctl -u ibm-firstboot-ignition --no-pager
4. Review the logs for errors. See the following section for more details.





 Machine cannot be reached on the network 

You receive output similar to the following messages.

curl: (6) Could not resolve host

The machine cannot be reached on the network.
Run 'ibmcloud ce subscription cron get -n mycronevent' to check the cron source status.
OK









 Subscription kafka commands 

Oftentimes in distributed environments you want your applications or jobs to react to messages (events) that are generated from other components, which are usually called event producers. With Code Engine, your applications or jobs can receive events of interest by subscribing to event producers. Event information is received as POST HTTP requests for applications and as environment variables for jobs.

The Kafka event producer watches for new messages to appear in a Kafka instance. When you create a Code Engine Kafka subscription for a set of topics, your app or job receives a separate event for each new message that appears in one of the topics.

You must be within the context of a [project](https://cloud.ibm.com/docs/cli?topic=cli-clicli-project) before you use subscription kafka commands.

For more information about working with Kafka event subscriptions, see [Working with the Kafka event producer](https://cloud.ibm.com/docs/codeengine?topic=codeengine-working-kafkaevent-producer). See [Getting started with subscriptions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-events) for more information about working with subscriptions in Code Engine.

You can use either subscription or sub in your subscription kafka commands. To see CLI help for the subscription commands, run ibmcloud ce sub kafka -h.



 ibmcloud ce subscription kafka create 

Create a Kafka event subscription.
Run 'ibmcloud ce subscription cron get -n mycronevent' to check the cron source status.
OK









 Subscription kafka commands 

Oftentimes in distributed environments you want your applications or jobs to react to messages (events) that are generated from other components, which are usually called event producers. With Code Engine, your applications or jobs can receive events of interest by subscribing to event producers. Event information is received as POST HTTP requests for applications and as environment variables for jobs.

The Kafka event producer watches for new messages to appear in a Kafka instance. When you create a Code Engine Kafka subscription for a set of topics, your app or job receives a separate event for each new message that appears in one of the topics.

You must be within the context of a [project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project) before you use subscription kafka commands.

For more information about working with Kafka event subscriptions, see [Working with the Kafka event producer](https://cloud.ibm.com/docs/codeengine?topic=codeengine-working-kafkaevent-producer). See [Getting started with subscriptions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-events) for more information about working with subscriptions in Code Engine.

You can use either subscription or sub in your subscription kafka commands. To see CLI help for the subscription commands, run ibmcloud ce sub kafka -h.



 ibmcloud ce subscription kafka create 

Create a Kafka event subscription.
For more information about regions, see [Locations](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-regions).
* <VERSION> indicates the version of the agent that you want to deploy. You must use a version that has a tag with the following format: X.Y.Z.



If you need to use a version that has a tag with any of the following formats: X.Y.Z-<date>.[hash], X, or X.Y, you must download the agent yaml file and modify it. Replace the version for all entries app.kubernetes.io/version in the file with the one that you want to use. You must download the yaml file that has the format X.Y.Z. Then, after you make the version changes, you can run kubectl apply -f <CUSTOM_YAML_FILE> to deploy the agent.

For more information about the agent tags, see [Understanding image tags](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-log_analysis_agentlog_analysis_agent_image_kube_tags).

For more information about the versions that are available, see [Getting information about Kubernetes logging agent images](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-log_analysis_agent_image).

For example, to configure an agent that sends data to a logging instance in Dallas, you must run the following command:

kubectl apply -f https://assets.us-south.logging.cloud.ibm.com/clients/logdna-agent/2.2.0/agent-resources-openshift.yaml





 Logging agent V1 

Choose one of the following commands to install and configure the logging agent version 1 by using kubectl commands::

Command (By using public endpoints)

Command (By using private endpoints)



Table 2. Commands by location when you use public endpoints

 Location Command (By using public endpoints)
You can now create Red Hat CoreOS enabled Satellite locations in the Toronto (tor, ca-tor) region.





* [July 2022](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-july22)



* [22 July 2022](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-july2222)



* New! Beta support for the VMware CSI driver template



* [15 July 2022](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-july1522)



* New information about using a custom Network Time Protocol (NTP) server





* [June 2022](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-june22)



* [21 June 2022](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-june2122)



* New and updated template parameter for the Azure File CSI driver template.



* [16 June 2022](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-june1622)



* New! You can now create Red Hat CoreOS enabled Satellite locations in the Washington D.C. (wdc, us-east) region.



* [15 June 2022](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-june1522)



* CLI change log
* New! You can now create Red Hat CoreOS enabled Satellite locations in the London (lon, eu-gb) region.



* [14 June 2022](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-relnotessatellite-june1422)



* Satellite for resellers
Be sure to keep your CLI up-to-date so that you can use the new commands. You can view the current version of all installed plug-ins by running ibmcloud plugin list.



 Output 

The command returns the following output:

Looking up 'app-configuration' from repository 'IBM Cloud'...
Plug-in 'app-configuration' found in repository 'IBM Cloud'
Attempting to download the binary file...
[==============================================================================================================================================] 100.00%
Installing binary...
OK
Plug-in 'app-configuration' was successfully installed into /Users/<username>/.bluemix/plugins/app-configuration. Use 'ibmcloud plugin show app-configuration' to show its details.







 Logging in to the CLI with a private endpoint 

For enhanced control and security over your data when using CLI, you have the option of using private routes to IBM Cloud endpoints. You must first enable virtual routing and forwarding in your account, and then you can enable the use of IBM Cloud private service endpoints. For more information about setting up your account to support the private connectivity option, see [Enabling VRF and service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint).

Use the following command to log in to a private endpoint by using the CLI:

ibmcloud login -a private.cloud.ibm.com





 ibmcloud ac init
Importing a boot image 

You can import an AIX or IBM i boot image by using the IBM® Power® Systems Virtual Server CLI or the console. All data centers use Tier 1 (NVMe-based flash storage) or Tier 3 (SSD flash storage) storage types. The Tier 1 storage type is best for customers who require higher throughput. Customers who do not require exceptionally high throughput and are looking to minimize costs want to select Tier 3. The storage types cannot be changed once the volume is created. A VM cannot have disks from both storage types. Large boot images take time to successfully import. You might experience a delay before receiving a confirmation message.

Image import requires HMAC keys (access, secret) in order to access your IBM Cloud Object Storage bucket. If you have not already generated your HMAC keys you can follow the instructions in [Using IBM COS HMAC credentials](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-uhc-hmac-credentials-main).

The IBM® Power® Systems Virtual Server Job feature tracks long-running asynchronous operations like VM capture, image export, and image import across multiple workspaces in your cloud account.

As part of this Job feature, new version of Power Cloud API and CLI enhancements have been introduced for these operations. To view the new API and CLIs, see the following:



* API for image import - [Create a new image from available images you have stored in IBM COS](https://cloud.ibm.com/apidocs/power-cloudpcloud-v1-cloudinstances-cosimages-post).- CLI enhancements include changes to the existing [ibmcloud pi image-import](https://cloud.ibm.com/docs/power-iaas-cli-plugin?topic=power-iaas-cli-plugin-power-iaas-cli-referenceibmcloud-pi-image-import) command.
Endurance Tier READHEAVY_TIER
Endurance Tier Per IOPS 2
Datacenter dal10
Target IP 161.26.99.155
 of Active Transactions 0
Replicant Count 0

So you can map the iscsi LUN ID to the block device's hostname:

SL02SEL1160157-221 lun id: 0 Target IP: 161.26.99.155







 Viewing the LUN ID in the UI 

You can also gather the LUN ID, Target IP address, and hostname of the Block Storage for Classic device on the Volume Details page in the UI.

Zoom

![The Volume Details page in the Console provides detailed information about the LUN.](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/BlockStorage//images/vmwareLUNID.vsg)

Image 1 shows the Volume Details page in the Console that provides detailed information about the LUN.
If you no longer need the instance group, you can delete the instance group to permanently remove it from your account. All instances that are part of the instance group are deleted as well.





 Editing an instance group 

You can access the instance group details page to make changes to the instance group. You can change the scaling method between static and dynamic methods. You can adjust the instance group size. And you can edit or add target policies for scaling.



 Editing the details for an instance group 

On the Instance group details page, you can use the pencil icon to make changes to the following items:



* Name
* Subnets: Subnet IP address capacity is validated against the size of the instance group. The membership count of the group cannot exceed the total number of IP addresses that are available to assign across the subnet(s). Currently, 6 IP addresses per subnet are allotted as overhead and not available to assign to instances.
* Load balancer pool: If the membership count of an instance group is set to 0, you can change the load balancer pool that is associated with the instance group. You can select a different load balancer that is available, or select none to stop using an assigned load balancer.
* Instance template: You can select a different instance template to be used to provision any new instances that are created for the instance group. Existing instances are not updated with the new instance template.
* Membership count: For more information, see [Changing the membership count of a static instance group](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-instance-groupchanging-membership-count). You cannot manually adjust the membership count for an instance group that is using the dynamic auto scale method, unless dynamic auto scaling is disabled.







 Changing the membership count of a static instance group 

If you are using the static method for your instance group, the instance group works to always maintain the number of instances you have set. If any instances fail, the instance group automatically replaces those failed instances in the instance group. By maintaining the instances in the group, the availibility of the applications running in those instances is also enhanced.

You can manually scale the instances in the group at any time by editing the membership count.
Release notes for App ID 



 22 June 2023 

IdP-initiated login is now available
: If you want to log in to your applications on IBM Cloud from your identity provider's UI, you can enable IdP-initiated login. [Learn more](https://cloud.ibm.com/docs/appid?topic=appid-enterprise&interface=uisaml-configure).





 4 May 2023 

IBM Cloud Foundry service broker unsupported
: All services that use the Cloud Foundry service broker will stop working on 1 June 2023, when Cloud Foundry enters the [End-of-Support stage](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecation).

Does this change affect me?

Not sure if your App ID instance is using the Cloud Foundry service broker? In the [Cloud Foundry services](https://cloud.ibm.com/cloudfoundry/public) section, check whether your App ID instance is listed as an alias. If your instance is already an alias, you do not need to take any action.

If your instance is not an alias and you want to keep it, please contact [IBM Cloud support](https://cloud.ibm.com/unifiedsupport/supportcenter) to discuss next steps.





 1 February 2023 

Ability to bulk delete Cloud Directory users
: It's now more efficient for users to clean up App ID instances. You can now use the bulk_remove API endpoint to remove multiple users from an App ID instance at once. [Learn more](https://cloud.ibm.com/docs/appid?topic=appid-cd-usersdelete-users).





 15 December 2022 

New App ID API endpoints
: App ID added options to make it more efficient for you to migrate your users from one service instance to another.