vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud ks ingress lb proxy-protocol enable --cluster CLUSTER [--cidr CIDR ...] [--header-timeout TIMEOUT] [-f] [-q]

Minimum required permissions
: Operator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

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

--cidr CIDR
: Optional: Load balancer CIDRs from which ALBs process information in PROXY protocol headers. If requests that contain PROXY headers originate from load balancers in other IP ranges, the information in the headers is not process by the ALB. This option is supported only for ALBs that run the community Kubernetes Ingress image. Default: 0.0.0.0/0

--header-timeout TIMEOUT
: Optional: The timeout value, in seconds, for the load balancer to receive the PROXY protocol headers that contain the client connection information. This option is supported only for ALBs that run the community Kubernetes Ingress image. Default: 5

-f
: Optional: Force the command to run with no user prompts.

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



 Example ingress lb proxy-protocol enable command 

ibmcloud ks ingress lb proxy-protocol enable --cluster mycluster --cidr 1.1.1.1/16







 ibmcloud ks ingress secret create 

Virtual Private Cloud

Classic infrastructure

Create an Ingress secret in a cluster for a certificate that is stored in IBM Cloud® Secrets Manager. This command can be used to create TLS or non-TLS secrets.

The previous alias for this command, ibmcloud ks ingress alb cert deploy, is deprecated. In CLI version 1.0.157 and later, the ibmcloud ks ingress alb cert category is deprecated, and these commands are now listed in the ibmcloud ks ingress secret subcategory.
ibmcloud is image-create IMAGE_NAME ([--file IMAGE_FILE_LOCATION --os-name OPERATING_SYSTEM_NAME --encrypted-data-key ENCRYPTED_DATA_KEY --encryption-key ENCRYPTION_KEY]] | [--source-volume SOURCE_VOLUME --encryption-key-volume ENCRYPTION_KEY_VOLUME]) [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME] [--deprecate-at DEPRECATE_AT] [--obsolete-at OBSOLETE_AT] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is image-create my-ubuntu-16-amd64 --file cos://us-south/custom-image-vpc-bucket/customImage-0.qcow2 --os-name ubuntu-16-amd64
* ibmcloud is image-create my-ubuntu-16-amd64 --file cos://us-south/custom-image-vpc-bucket/customImage-0.qcow2 --os-name ubuntu-16-amd64 --resource-group-id fee82deba12e4c0fb69c3b09d1f12345
* ibmcloud is image-create my-ubuntu-16-amd64 --file cos://us-south/custom-image-vpc-bucket/customImage-0.qcow2 --os-name ubuntu-16-amd64 --resource-group-name Default
* ibmcloud is image-create my-ubuntu-16-amd64 --file cos://us-south/custom-image-vpc-bucket/customImage-0.qcow2 --os-name ubuntu-16-amd64 --output JSON
If you need to use a different version of node.js, use nvm install v<node version> at the beginning of your script. This image now contains the Terraform CLI.

Support for helm2 was discontinued on 13 November 2020. The helm tool within this image is the latest in the 3.x branch. The helm3 tool is now named helm. The helm3 symbolic link is deprecated and will be removed in upcoming releases.

This image includes the following tools:

 node
v18.16.0

 npm
9.5.1

 jq
jq-1.6

 yq
yq version 2.4.1

 yq3
yq version 3.4.1

 yq4
yq (https://github.com/mikefarah/yq/) version v4.34.1

 kubectl
v1.25.8

 buildctl
buildctl github.com/moby/buildkit v0.11.6 2951a28cd7085eb18979b1f710678623d94ed578

 helm
v3.12.1+gf32a527

 ibmcloud
/usr/local/bin/ibmcloud version 2.16.1+5813b04-2023-06-07T22:01:53+00:00

 ibmcloud plugins
Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
cloud-functions[wsk/functions/fn] 1.0.69 false
cloud-internet-services[cis] 1.15.2 true
code-engine[ce] 1.43.7 true
container-registry[cr] 1.0.11 true
container-service[kubernetes-service/ks] 1.0.523 false
cra 1.3.6 false
doi 0.4.2 false
schematics[sch] 1.12.10 true
secrets-manager[sm] 2.0.1 true
If you create a newer version of an image with the same tag as the original image, the original image is overwritten in the container registry and becomes untagged. The newer image is tagged, and this newer image has a different digest. Your Code Engine application does not use this newer image, because the newer image has a different digest than the image that is referenced by the application revision. Code Engine can still create new instances of the application revision as long as the untagged image, which was referenced originally, still exists. For more information, see [Why can't Code Engine pull an image?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-image-cannot-pull)

The default URL for applications is of the format https://<appname>.<uuid>.<region>.codeengine.appdomain.cloud where appname is the name of your app, uuid is the automatically generated unique identifier, and region is the region in which your Code Engine project resides. The UUID portion of the URL of an application is of the format aaaabbbbccc. The automatically generated application URL persists for the lifecycle of the project for your application.

For more information about endpoints to access applications by region, see [Code Engine endpoints for accessing applications](https://cloud.ibm.com/docs/codeengine?topic=codeengine-regionsendpoints-app).

By default, Code Engine assumes that apps listen for incoming connections on port 8080. In addition, Code Engine sets the PORT environment variable to the port value that the application is expected to be listening on. If your app needs to listen on a port other than port 8080, either deploy your app from the console and specify the correct port or use the --port option on the app create command. For more information about environment variables that are set by Code Engine, see [Automatically injected environment variables](https://cloud.ibm.com/docs/codeengine?topic=codeengine-inside-env-vars). The following ports are reserved by Code Engine: 8022, 8008, 8012, 9090, 9091, and 15090.
Updated default container network sysctls New containers running on the pod network will have the following sysctl tuning applied by default: net.ipv4.tcp_keepalive_intvl=15, net.ipv4.tcp_keepalive_probes=6 and net.ipv4.tcp_keepalive_time=40. If your apps rely on the previous defaults, you will need to update your app deployment to customize the sysctl settings. See [Optimizing network keepalive sysctl settings](https://cloud.ibm.com/docs/containers?topic=containers-kernelkeepalive-iks) for details. 





 Removing the Block Storage Helm chart 



1. Add the iks-charts repo and update it.

helm repo add iks-charts https://icr.io/helm/iks-charts && helm repo update
2. List the Helm deployments in your cluster and make a note of the Block Storage for Classic plug-in deployment in the kube-system namespace.

helm ls -A
3. Delete the plug-in from your cluster by using the helm delete command.

helm delete RELEASE -n kube-system
4. List pods in the kube-system namespace to verify the plug-in pods have been removed.

kubectl get pods -n kube-system | grep block









 Update after master 

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



Changes to make after you update the master to Kubernetes 1.24

 Type Description 

 Unsupported:kubectl expose removes --container-port and --generator options The kubectl expose command no longer supports the deprecated --container-port and --generator options. If your scripts rely on these options, update them. 
 Unsupported:kubectl run removes several options The kubectl run command no longer supports the deprecated --serviceaccount, --hostport, --requests and --limits options.
: URL pointing to the .zip file of the product.

--include-config (optional)
: If provided, all configuration values are included and available when you add the product.







 ibmcloud catalog offering version merge-draft 

Run the following command to merge a draft version of a product.

ibmcloud catalog offering version merge-draft --version-locator VERSION_NUMBER



 Command options 

--version-locator VERSION_NUMBER
: To get the version locator for the product, run the ibmcloud catalog offering list command and locate the specified product or version you want to use.







 ibmcloud catalog offering enable-sharing 

Run the following command to enable your product to be shared.

ibmcloud catalog offering enable-sharing --catalog CATALOG --offering OFFERING



 Command options 

--catalog CATALOG
: The catalog name or ID.

--offering OFFERING
: The product name or ID.







 ibmcloud catalog offering ready 

Run the following command to mark your product as ready to share or publish.

ibmcloud catalog offering ready --version-locator VERSION_NUMBER



 Command options 

--version-locator VERSION_NUMBER
: To get the version locator for the product, run the ibmcloud catalog offering list command and locate the specified product or version you want to use.







 ibmcloud catalog offering delete 

Run the following command to delete a product from your private catalog. You cannot delete a product that is published in the IBM Cloud catalog. To deprecate a published product from the IBM Cloud catalog, see [ibmcloud catalog offering deprecate-offering](https://cloud.ibm.com/docs/cli?topic=cli-manage-catalogs-pluginpublish-offering-deprecate).

ibmcloud catalog offering delete --catalog CATALOG --offering OFFERING



 Command options 

--catalog CATALOG
: The catalog name or ID.

--offering OFFERING
: The product name or ID.







 ibmcloud catalog offering publish account 

Run the following command to publish a product from your private catalog to an account.
--space-role SPACE_ROLE (deprecated)
: Space role. Valid inputs are: SpaceManager, SpaceDeveloper, and SpaceAuditor.

-r, --region REGION (deprecated)
: Region name. Defaults to current region if not specified.

If you aren't ready to assign access, or want to assign an IAM policy, you can invite a user and assign it later. For more information about assigning access to users, see [Managing access to resources](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources).







 ibmcloud account user-reinvite 

Resend invitation to a user (account admin):

ibmcloud account user-reinvite USER_EMAIL



 Command options 

USER_EMAIL (required)
: The email of the user to be invited again.







 ibmcloud account user-preference 

Show user preference details:

ibmcloud account user-preference





 ibmcloud account user-preference-update 

Update user preferences:

ibmcloud account user-preference-update (--position NEW_POSITION)



 Command options 

--position NEW_POSITION (optional)
: Set a user's position, such as manager or student.







 ibmcloud account user-status 

Show user's status:

ibmcloud account user-status [USER_ID] [--output FORMAT] [-q, --quiet]



 Command options 

USER_ID
: User ID. If not specified, default to current user.

--output FORMAT
: Specify output format. Only 'JSON' is supported.

-q, --quiet
: Suppress verbose output.







 ibmcloud account user-status-update 

Update user's status:

ibmcloud account user-status-update USER_ID NEW_STATUS [--output FORMAT] [-q, --quiet]



 Command options 

USER_ID (required)
: User ID.

NEW_STATUS (required)
: Set a user's status, such as SUSPENDED or ACTIVE.
* UI
* CLI
* API
* Terraform







 Destroying workspace resources 

Remove the IBM Cloud® resources that you provisioned with your Schematics Workspace, even if these resources are active.

IBM Cloud Schematics deprecates older version of Terraform. For more information, see [Deprecating older version of Terraform process in IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-deprecate-tf-version).



 Before you begin 



* [Create a Terraform configuration](https://cloud.ibm.com/docs/schematics?topic=schematics-create-tf-config), and store the configuration in a GitHub, GitLab, or Bitbucket repository. You can also upload a tape archive file (.tar) from your local workstation to provide your template to IBM Cloud Schematics. For more information, see the [ibmcloud schematics workspace upload](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-upload) command and see the [upload a tar file to your workspace](https://cloud.ibm.com/apidocs/schematics/schematicsupload-template-tar) API.
* Make sure that you have the [permissions](https://cloud.ibm.com/docs/schematics?topic=schematics-access) to create a workspace.



Ensure the location and the url endpoint are pointing to the same region when you create or update the Schematics Workspaces and actions. For more information about location and endpoint, see [Where is your information stored](https://cloud.ibm.com/docs/schematics?topic=schematics-secure-datapi-location)?





 Destroying workspace resources using the UI 



1. Log in to [IBM Cloud](https://cloud.ibm.com/).
2.
Image Entrypoint Image Cmd Code Engine command Code Engine args Command that is run 

 /myapp --debug <not set> <not set> /myapp --debug 
 /myapp --debug /myapp2 <not set> /myapp2 
 /myapp --debug <not set> -d /myapp -d 
 /myapp --debug /myapp2 -d /myapp2 -d 



You can specify these values by using the --command and --argument options in the CLI for apps and jobs and the Command and Arguments entry boxes in the console for jobs. For more information, see [Deploying your app with commands and arguments](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloadsdeploy-app-cmd-args) and [Running your job with commands and arguments](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-planjob-cmd-args).
Using community buildpacks 

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

If you can't find a starter in the IBM Cloud® catalog that provides the runtime you want, you can bring an external buildpack to IBM Cloud. You can specify a custom, Cloud Foundry-compatible buildpack when you deploy your app by using the ibmcloud cf push command.

External buildpacks are provided by the Cloud Foundry community for you to use as your own buildpacks. Before you deploy your app to IBM Cloud, make sure that you install the IBM Cloud command-line interface.

External buildpacks are not provided by IBM. Contact the Cloud Foundry community for support.



 Built-in community buildpacks 

In IBM Cloud, you can use built-in buildpacks that are provided by the Cloud Foundry community. To see built-in community buildpacks, run the ibmcloud cf buildpacks command:

ibmcloud cf buildpacks

Getting buildpacks...

buildpack position enabled locked filename
...
java_buildpack 7 true false buildpack_java_v2.0.2.zip
ruby_buildpack 8 true false buildpack_ruby_v46-245-g2fc4ad8.zip
nodejs_buildpack 9 true false buildpack_nodejs_v8-177-g2b0a5cf.zip

For the same runtime or framework, IBM-created buildpacks take precedence over the community ones. If you want to use the community buildpack to overwrite the IBM-created buildpack, you must specify the buildpack by using the -b option with the ibmcloud cf push command.

For example, you can use the community buildpack for Java™ web apps by using the following command.

ibmcloud cf push app_name -b java_buildpack -p app_path

You can also use the community buildpack for Node.js app with the following command.
The [ibmcloud plugin list](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_settingsibmcloud_plugin_list) command reports whether an installed CLI plug-in supports private endpoints. If a plug-in that you use does not show private support, you must continue to use it with your API set to the public endpoint cloud.ibm.com.





 Determining which commands support private endpoints 

The following commands support private endpoints:



* api
* login
* target
* logout



Most commands under the following namespaces work when you are using private endpoints:



* account
* billing
* iam
* resource
* catalog



If the CLI is set to access private endpoints and you try to run a command or plug-in that does not yet support private endpoints, you might see an error.

The following core commands do not yet support private endpoints:

account
domain-cert
domain-cert-add
domain-cert-remove
org
org-account
org-create
org-rename
org-replicate
org-role-set
org-role-unset
org-roles
org-user-add
org-user-remove
org-users
orgs
space
space-create
space-delete
space-rename
space-role-set
space-role-unset
space-roles
space-users
spaces
audit-logs
update
billing
org-usage
catalog
template-run
dev
all commands
cf
all commands
sl
all commands
app (deprecated)
all commands
service (deprecated)
all commands
Show more
curl -O http://downloads.service.softlayer.com/citrix/xen/vhd-util-standalone-3.5.0-xs.2+1.0_71.2.2.x86_64.rpm
3. Install the RPM by using the following command:

rpm -iv vhd-util-standalone-3.5.0-xs.2+1.0_71.2.2.x86_64.rpm
4. Identify and select the AES data encryption key (DEK) that you need to encrypt and decrypt your disk image, then write it into a keyfile. This DEK is the same base64-encoded DEK that you wrapped with your key management service-provided customer root key that is in [Preparing your environment](https://cloud.ibm.com/docs/image-templates?topic=image-templates-using-end-to-end-e2e-encryption-to-provision-an-encrypted-instancepreparing-your-environment). Key material that is written into keyfiles must be [unwrapped](https://cloud.ibm.com/docs/key-protect?topic=key-protect-cli-referencekp-key-command) and not be encoded.

Because the keyfile isn't base64-encoded, you can't print or view the keyfile content from the command line by using standard ASCII characters.

Use the following command to create keyfiles with either an AES 256 bit or an AES 512 bit encryption key:

echo <data_key> | base64 -d - > <keyfile_name>

Example command:

echo Nrfen98EpMxF2B+wdgLfagzrqvgUZfMK4vL2T0NsT20ihrsNC9pUUHtizF6218pze8RLCgQ6kwxuE58IWLzgDA== | base64 -d - > aes512.dek
5. Use the following command to verify the keyfiles that you created in the previous step:
File shares must be based on the [dp2 profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles&interface=uidp2-profile) to use the security_group value. See [2023-07-11 API migration (file shares)](https://cloud.ibm.com/docs/vpc?topic=vpc-2023-07-11-migration-file-shares) for guidance on migrating access_control_mode from vpc to security_group.

When [creating a mount target](https://cloud.ibm.com/apidocs/vpc-betacreate-share-mount-target) for a file share with access_control_mode set to security_group, you must also create a virtual network interface by using the virtual_network_interface property. For more information, see [About virtual network interfaces](https://cloud.ibm.com/docs/vpc?topic=vpc-vni-about&interface=api) and [Mount target access modes](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-about&interface=uifs-mount-access-mode). You must use an access_control_mode of security_group to enable [Data encryption in transit for file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-eit).







 13 June 2023 



 For all version dates 

Image lifecycle management property name changes. For accounts that have been granted special approval to preview the image lifecycle management feature, the deprecated_at and obsoleted_at properties for [images](https://cloud.ibm.com/apidocs/vpc-betacreate-image) requests have been renamed deprecation_at and obsolescence_at, respectively. Original property names deprecated_at and obsoleted_at will continue to be supported until the feature becomes generally available. Requests that specify the original and revised property names simultaneously will be rejected.

This feature is now generally available.
Updating your domain 

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

Domains provide the URL route that is allocated to your organization in IBM Cloud®. For Cloud Foundry apps, you can migrate your domain from mybluemix.net to appdomain.cloud by using either the IBM Cloud console or the command-line interface.

The default shared domain is mybluemix.net, but appdomain.cloud is another domain option that you can use.



 Updating domains from the IBM Cloud console 

Complete these steps to update the domain for your Cloud Foundry org by using the console:



1. From the [IBM Cloud console](https://cloud.ibm.com), click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/1e0945ee44f87283927af9404a8f2d077786db0c/icons/icon_hamburger.svg), and select Resource List.
2. On the Resource List page, click Cloud Foundry Apps.
3. Click the app that you want to change the domain for. The app's Overview page is displayed.
4. Select the Routes menu, notice the current domain, such as <myapp.mybluemix.net>, and click Edit routes.
5. Select the list of domains, and then click the domain that you want to use, such as us-south.cf.appdomain.cloud.
6. Confirm your updates by clicking Save.
7. Confirm that you want to replace the old domain, and click Remove.
8. To verify that the new route is working, click Visit App URL.







 Updating domains from the IBM Cloud command-line interface 



1. Connect to your targeted Cloud Foundry API endpoint by typing the following command:
Schematics worker runtime 

The Schematics worker runs your automation workload. The workload is deployed as a Kubernetes job pod that run only one Schematics automation command and self-destructs on completion. All your Schematics command such as schematics plan, schematics apply, schematics run, and schematics destroy runs by using the Schematics worker pods. In addition to the core Terraform CLI and Ansible CLI, the Schematics worker job images include several utilities and executables.

Following are the Schematics type of workers.



Schematics workers types

 Worker Description 

 runtime-terraform-job Used to run the Terraform CLI. <br>This worker is used to run the Schematics Workspace jobs. 
 runtime-ansible-job Used to run the Ansible playbook CLI. <br>This worker is used to run the Schematics Action jobs. 



The Schematics worker images are built by using the [Universal Base Image (UBI-8)](https://catalog.redhat.com/software/containers/ubi8/ubi/5c359854d70cc534b3a3784e) as the base image. The Schematics worker images used by the multi-tenant Schematics service instance and the corresponding Schematics agents are not the same.

In the multi-tenant Schematics service instance, your Terraform or Ansible automation cannot install any software or tools in the Schematics worker pods. It is blocked by design.

For more information about depreciation note, see [Schematics announcement](https://cloud.ibm.com/status/announcement?component=schematics).



Schematics depreciation note

 From date Deprecation notice 

 21 September 2022 Support for Python v3.6 in runtime-ansible-job is deprecated. Instead the runtime-ansible job image uses Python v3.8. 



The following table enlists the preinstalled software and tools in the Schematics worker images.



 Runtime-terraform-job image