vania-janet/multiturn-rag-retrieval-data huggingface dataset:
On 11 November 2022, virtual private endpoints (VPEs) for IBM Cloud Container Registry are being updated and the existing VPE version is being deprecated on 15 December 2022. If you use Container Registry VPE gateways, you must create new VPE gateways and remove your VPE gateways that were created before 11 November 2022 at the earliest opportunity so that you pick up these changes. VPE gateways that were created before 11 November 2022 are deprecated and will not work after 15 December 2022.

If you create a new Container Registry VPE gateway after 11 November 2022 and also use Cloud Identity and Access Management (IAM) [restricted IP address lists](https://cloud.ibm.com/docs/account?topic=account-ips&interface=ui), you must ensure that your restricted IP address list contains the Cloud Service Endpoint (CSE) source IP addresses of the VPCs in which your Container Registry VPE gateways exist. This requirement is related to a previous change to how Container Registry works over the private network that the new VPE version also uses, see [Container Registry private IP addresses changed on 5 July 2022](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_notices_iam_private_network).

For more information, see [Changes to Container Registry VPE gateways from 11 November 2022](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_notices_vpe&interface=ui).





 2 November 2022 

Changes to private IP addresses from 15 December 2022
: The IBM Cloud Container Registry private IP addresses that were replaced on 5 July 2022 are being decommissioned on 15 December 2022.

IP addresses for accessing Container Registry over the private network changed on 5 July 2022, see [Container Registry private IP addresses changed on 5 July 2022](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_notices_iam_private_network). You continue to be able to use these old IP addresses, but they are due to be decommissioned on 15 December 2022. After this date, you will not be able to access Container Registry by using these IP addresses.
The output of this command typically contains one <REGISTRY> key.
4. Confirm the following information about the key:

a. Look at the <REGISTRY> value. This value must match the image of the build.



* If the image name is on IBM Cloud Container Registry, for example us.icr.io/aNamespace/anImage, then the <REGISTRY> needs to be us.icr.io.
* If the image name is docker.io/aNamespace/aRepository or /aNamespace/aRepository without any hostname, then the build is using Docker Hub. In this case, the <REGISTRY> must be https://index.docker.io/v1/.



b. Look at the <USERNAME> value. If the registry is an IBM Cloud Container Registry, then an API key must be used for authentication. The <USERNAME> needs to be iamapikey and the password needs to be an API key. See [Automating access to IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_access) for steps to create the API key.

c. The credentials need to be validated. IBM Cloud® Identity and Access Management (IAM) allows permissions to be assigned in a fine-grained way. For example, a service ID with access to an IBM Cloud Container Registry namespace and the permission to pull images, might not be allowed to push images. But, this permission is what is needed in this case.
5. After you determine the changes that are needed, create a container registry secret that uses corrected values. Use the [ibmcloud ce secret create --format](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-secret-create) command; for example,

ibmcloud ce secret create --format registry --name <REGISTRY_SECRET> --server <REGISTRY_SERVER> --username <USERNAME> --password <PASSWORD>
6. Update the build to reference the name of your registry secret.

a.
* [Access roles for configuring Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_configure)
* [Access roles for using Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_using)



* [Assigning access to Container Registry in the console](https://cloud.ibm.com/docs/Registry?topic=Registry-iamregistry_iam_assign-access-console)
* [Assigning access to Container Registry in the CLI](https://cloud.ibm.com/docs/Registry?topic=Registry-iamregistry_iam_assign-access-cli)
* [Assigning access to Container Registry by using the API](https://cloud.ibm.com/docs/Registry?topic=Registry-iamregistry_iam_assign-access-api)
* [Assigning access to Container Registry by using Terraform](https://cloud.ibm.com/docs/Registry?topic=Registry-iamregistry_iam_assign-access-terraform)



[Defining IAM access policies](https://cloud.ibm.com/docs/Registry?topic=Registry-useruser)



* [Creating policies](https://cloud.ibm.com/docs/Registry?topic=Registry-usercreate)







 Managing image security with Vulnerability Advisor 

[Managing image security with Vulnerability Advisor](https://cloud.ibm.com/docs/Registry?topic=Registry-va_indexva_index)



* [About Vulnerability Advisor](https://cloud.ibm.com/docs/Registry?topic=Registry-va_indexabout)



* [Data protection](https://cloud.ibm.com/docs/Registry?topic=Registry-va_indexabout_data_protection)



* [Types of vulnerabilities](https://cloud.ibm.com/docs/Registry?topic=Registry-va_indextypes)
If you want to view the current version of your container-registry CLI plug-in, run the ibmcloud plugin list command.

For more information about the IAM platform and service access roles that are required for some Container Registry commands, see [Managing IAM access for Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iam).

Do not put personal information in your container images, namespace names, description fields, or in any image configuration data (for example, image names or image labels).

If Container Registry commands fail with an error that says that they're not registered commands, see [Why do cr commands fail saying they’re not registered?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-login-error) for assistance. If the commands fail saying that you're not logged in, see [Why do commands fail saying that I'm not logged in?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-login-cloud) for assistance.







 ibmcloud cr api 

Returns the details about the registry API endpoint that the commands are run against.

ibmcloud cr api



 Prerequisites 

None







 ibmcloud cr exemption-add 

Create an exemption for a security issue. You can create an exemption for a security issue that applies to different scopes. The scope can be the account, [namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_namespace), [repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_repository), [digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_digest), or [tag](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_tag).

You can identify the images in the scope by using either the tag or the digest.
* [Create a cluster](https://cloud.ibm.com/docs/containers?topic=containers-clusters).
* Ensure that you have the correct access permissions for adding and removing

namespaces, see [Access roles for configuring IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_configure).
* Ensure that you are using Vulnerability Advisor version 4.

Vulnerability Advisor version 3 is deprecated from 19 June 2023. For more information about how to update to version 4, see [Update Vulnerability Advisor to version 4 by 19 June 2023](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_notices_va_v4&interface=ui).







 Step 1: From code to a running container 

Using [IBM Cloud Container Registry](https://www.ibm.com/cloud/container-registry) to store your container images is the easiest way to get an application up and running with IBM Cloud Kubernetes Service. The following steps show you how to build a container image, store it in IBM Cloud Container Registry, and create a Kubernetes deployment that uses that image.



 Create a namespace 

Create a

namespaceto store your container images in IBM Cloud Container Registry. Namespaces are created in aresource group. For more information, see [Planning namespaces](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_setup_cli_namespaceregistry_setup_cli_namespace_plan).



1. To log in to IBM Cloud and target the us-south region, run the following command.

ibmcloud login -r us-south [--sso]

If you have a federated ID, use ibmcloud login -r us-south --sso to log in. Enter your username and use the provided URL in your CLI output to retrieve your one-time passcode. If you have a federated ID, the login fails without the --sso and succeeds with the --sso option.
[IBM Developer - Containers](https://developer.ibm.com/technologies/containers/)





 Troubleshooting 

[Troubleshooting](https://cloud.ibm.com/docs/Registry?topic=Registry-ts_indexts_index)



* [Troubleshooting topics](https://cloud.ibm.com/docs/Registry?topic=Registry-ts_indexgettinghelp_ts)



* [Troubleshooting CLI login](https://cloud.ibm.com/docs/Registry?topic=Registry-ts_indexgettinghelp_ts_cli_login)
* [Troubleshooting pull and push errors](https://cloud.ibm.com/docs/Registry?topic=Registry-ts_indexgettinghelp_ts_pull_push)
* [Troubleshooting CLI commands](https://cloud.ibm.com/docs/Registry?topic=Registry-ts_indexgettinghelp_ts_cli_commands)
* [Troubleshooting networking](https://cloud.ibm.com/docs/Registry?topic=Registry-ts_indexgettinghelp_ts_network)
* [Troubleshooting Portieris](https://cloud.ibm.com/docs/Registry?topic=Registry-ts_indexgettinghelp_ts_portieris)







 Troubleshooting CLI login 

[Why can't I log in to Container Registry?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-logintroubleshoot-login)

[Why does the Container Registry login keep expiring?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-login-expiretroubleshoot-login-expire)

[Why do commands fail saying that I'm not logged in?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-login-cloudtroubleshoot-login-cloud)
* You're using an IBM Cloud Kubernetes Service cluster in a [configuration](https://cloud.ibm.com/docs/containers?topic=containers-registrycluster_registry_auth_private) that automatically talks to the registry over a private connection.
* You're accessing Container Registry through a virtual private cloud (VPC) virtual private endpoint gateway (VPE gateway).
* You're using the Container Registry private IP addresses for configuring network access, for example, in firewalls or Access Control Lists (ACL).



If any of the previous statements is true when this change takes effect, the IP addresses in the IBM Cloud Activity Tracker logs change, but you don't need to do anything unless you are also using IAM IP address access restrictions.





 What actions you need to take 

You must take the appropriate actions before 23 June 2022. If you don’t make the appropriate updates, your requests to push and pull from Container Registry might fail.

Depending on which of the following scenarios you fit, take the appropriate action.

You access Container Registry over the private network and maintain a list of restricted IP addresses in IAM.
: You must update your IAM restricted IP address list to include any IP addresses or subnets of hosts in your account that make requests to Container Registry. You must keep the current Container Registry private IP addresses in your restricted IP list until an announcement indicates it is safe to remove them. For more information about how to update a restricted IP address list, see [Allowing specific IP addresses](https://cloud.ibm.com/docs/account?topic=account-ips) in the Cloud Identity and Access Management (IAM) documentation.

Your firewalls are configured with the Container Registry private IP addresses.
: You must include the new private IP addresses in your firewall configuration. For more information about connecting to Container Registry over the private network, see [Securing your connection to Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_private).

For more information about the new and current Container Registry private IP addresses, see the following topics:
* [Supported clients](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewsupport_clients)



* [Support for Docker](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewdocker)
* [Support for other clients](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewclients)









 Container Registry architecture and workload 

[Container Registry architecture and workload](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_architectureregistry_architecture)



* [Segmentation of data](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_architectureregistry_architecture_segment)
* [Private connections](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_architectureregistry_architecture_private_connections)







 Public IBM images 

[Public IBM images](https://cloud.ibm.com/docs/Registry?topic=Registry-public_imagespublic_images)



* [Accessing the public IBM images by using the CLI](https://cloud.ibm.com/docs/Registry?topic=Registry-public_imagespublic_images_cli)







 What are containers? 

[What are containers?](https://www.ibm.com/topics/containers)





 Notifications 

[Notifications](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_noticesregistry_notices)



* [Notifications topics](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_noticesregistry_notices_topics)



[Upcoming public networking changes for Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_notices_wildcard_domainsregistry_notices_wildcard_domains)
IP addresses for accessing Container Registry over the private network changed on 5 July 2022, see [Container Registry private IP addresses changed on 5 July 2022](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_notices_iam_private_network). You continue to be able to use these old IP addresses, but they are due to be decommissioned on 15 December 2022. After this date, you will not be able to access Container Registry by using these IP addresses.

For more information, see [Changes to private IP addresses from 15 December 2022](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_notices_ip_address).





 15 September 2022 

Container Registry plug-in 1.0.0 is available
: A new version, version 1.0.0, of the Container Registry CLI plug-in is available. To update the version of your Container Registry CLI plug-in, see [Updating the container-registry CLI plug-in](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_setup_cli_namespace&interface=uiregistry_cli_update).

Version 1.0.0 includes [Vulnerability Advisor 4](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_release_notes15sep2022_va_version_4).

In version 1.0.0, the ibmcloud cr image-list and ibmcloud cr image-digests commands no longer include security status by default. To include security status, you can either add the --va option to the command, or use the [ibmcloud cr va](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_va) command to query the security status for an individual image.

For more information, see [Container Registry CLI stops returning security status results in lists by default from version 1.0.0](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_notices_lists).
* [VMs, containers, and Kubernetes](https://cloud.ibm.com/docs/Registry?topic=Registry-vm-to-containers-and-kubernetesvm-to-containers-and-kubernetes-4)



* [Virtual machines vs containers](https://cloud.ibm.com/docs/Registry?topic=Registry-vm-to-containers-and-kubernetesvm-to-containers-and-kubernetes-5)
* [Kubernetes orchestration](https://cloud.ibm.com/docs/Registry?topic=Registry-vm-to-containers-and-kubernetesvm-to-containers-and-kubernetes-6)



* [What IBM's doing for you](https://cloud.ibm.com/docs/Registry?topic=Registry-vm-to-containers-and-kubernetesvm-to-containers-and-kubernetes-7)



* [Sizing clusters](https://cloud.ibm.com/docs/Registry?topic=Registry-vm-to-containers-and-kubernetesvm-to-containers-and-kubernetes-sizing_clusters)
* [Decide what Database option to use](https://cloud.ibm.com/docs/Registry?topic=Registry-vm-to-containers-and-kubernetesvm-to-containers-and-kubernetes-database_options)
* [Decide where to store application files](https://cloud.ibm.com/docs/Registry?topic=Registry-vm-to-containers-and-kubernetesvm-to-containers-and-kubernetes-decide_where_to_store_data)



* [Non-persistent data storage](https://cloud.ibm.com/docs/Registry?topic=Registry-vm-to-containers-and-kubernetesvm-to-containers-and-kubernetes-11)
IBM Cloud Container Registry Container images Set up your own secured Docker image repository where you can safely store and share images between cluster users. For more information, see the [IBM Cloud® Container Registry documentation](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-started). Yes Yes 
 IBM Cloud Continuous Delivery Build automation Automate your app builds and container deployments to Kubernetes clusters by using a toolchain. For more information about the setup, see [working with Tekton pipelines](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tekton-pipelines). Yes Yes 
 IBM Cloud Classic File Storage for Classic File storage [IBM Cloud Classic File Storage for Classic](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-getting-startedgetting-started) is persistent, fast, and flexible network-attached, NFS-based file storage that you can add to your apps by using Kubernetes persistent volumes. You can choose between predefined storage tiers with GB sizes and IOPS that meet the requirements of your workloads. For more information about how to provision file storage in your cluster, see [Setting up IBM Cloud File Storage for Classic](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_storage). Yes 
 IBM Key Protect for IBM Cloud Data encryption Encrypt the Kubernetes secrets that are in your cluster by [enabling a key management service (KMS) provider](https://cloud.ibm.com/docs/containers?topic=containers-encryptionkms). Encrypting your Kubernetes secrets prevents unauthorized users from accessing sensitive cluster information. Yes Yes 
 IBM Log Analysis Cluster and app logs Add log management capabilities to your cluster by deploying a Log Analysis agent to your worker nodes to manage logs from your pod containers. For more information, see [Managing Kubernetes cluster logs with IBM Log Analysis](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-tutorial-use-logdna).
Container services 

IBM Cloud Container Registry
: You can configure one monitoring instance in each region to collect platform metrics for IBM Cloud® Container Registry. For information about the locations where the automatic collection of Container Registry service metrics is enabled, see [Monitoring metrics for IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_monitorregistry_monitor_locations).

IBM Cloud Kubernetes Service
: You can choose the monitoring instance where you want to collect IBM Cloud® Kubernetes Service service metrics.

Red Hat OpenShift on IBM Cloud
: You can choose the monitoring instance where you want to collect Red Hat® OpenShift® on IBM Cloud® service metrics.





 Satellite 

IBM Cloud Satellite
: You can monitor IBM Cloud Satellite® through the monitoring instance that is configured with service platform metrics in the same region that your Satellite location is managed from.





 Developer tools 

Europe

America

Asia Pacific



Developer tools and DevOps services in Europe locations

 Service Frankfurt (eu-de) London (eu-gb) 

 IBM Cloud® Continuous Delivery ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) 
 IBM Cloud® App Configuration ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) 
 IBM Cloud® Event Notifications !
For more information, see [Securing your connection to Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_private) and [IBM Cloud Container Registry architecture and workload](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_architecture).

ibmcloud cr private-only command is available
: You can use the ibmcloud cr private-only command to prevent image pulls or pushes over public network connections for your account.

For more information, see [ibmcloud cr private-only](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcliic_cr_private_only).





 3 February 2020 

Using Container Registry tokens is deprecated
: The use of UAA and Container Registry tokens is deprecated. From 12 August 2020, UAA tokens are not accepted for authentication.

For more information, see [Announcing End of IBM Cloud Container Registry Support for UAA Tokens](https://www.ibm.com/cloud/blog/announcements/announcing-end-of-ibm-cloud-container-registry-support-for-uaa-tokens).





 31 January 2020 

ibmcloud cr image-digests command is available
: The ibmcloud cr image-digests command displays all images in your account, including untagged images.

For more information, see [ibmcloud cr image-digests](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_digests).





 4 December 2019 

Support for Red Hat signatures is available
: Container Registry now supports Red Hat signatures.

For more information, see [Signing images for trusted content by using Red Hat® signatures](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_trustedcontentregistry_trustedcontent_red_hat_sig).





 25 October 2019 

IBM Log Analysis platform services logs are available
: Container Registry generates platform services logs that are displayed in your logging instances.
* Check the information about logging a client into Container Registry, see [Push images to your namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-started&interface=uigs_registry_images_pushing) in [Getting started with Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-started&interface=ui).
* Create and use a valid IAM API key to log a client, such as Docker, in to Container Registry with username iamapikey and the API key as your password. For more information, see [Managing user API keys](https://cloud.ibm.com/docs/account?topic=account-userapikey&interface=uiuserapikey).
* Use the ibmcloud CLI or IAM API to retrieve a valid OAuth token to authenticate against the Container Registry API. For more information, see [IBM Cloud Container Registry API - Authentication](https://cloud.ibm.com/apidocs/container-registryauthentication).
* When you authenticate against the Container Registry API, ensure that you use a valid Account ID.
* When you access Container Registry by using automation, set up a service ID and API key. For more information, see [Accessing Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_accessregistry_access_serviceid_apikey_create).
* If your image is in a different region of Container Registry, you must log in to IBM Cloud in that region by running the [ibmcloud cr region-set](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_region_set) and [ibmcloud cr login](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_login) commands. For more information, see [Targeting a local region](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions).