vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: The buildpack contains an updated version of the Liberty profile based on the [8.5.5.6 release](https://developer.ibm.com/wasdev/blog/2015/06/25/java-ee-7-has-landed-in-was-liberty/). With this release all the Java EE 7 Liberty features previous available as beta features, are now available as production-ready features. Due to port and other restrictions in the IBM Cloud, some features such as for example remote EJBs are not be fully supported in the platform.



* The buildpack recognizes and runs apps packaged in the [distZip-style](https://docs.gradle.org/current/userguide/application_plugin.html).
* The buildpack contains an updated data collector for the Monitoring and Analytics service and WebSphere eXtreme Scale Client that support the new Liberty runtime version.







 30 June 2015 

Updated Liberty buildpack v1.19.1-20150622-1509
: This version of the buildpack contains an updated IBM JRE with a security fix for the [LogJam vulnerability](https://www.ibm.com/support/pages/node/531245).



* The New Relic agent was updated to version 3.17. The new version provides improved integration with the Liberty profile runtime.







 15 June 2015 

Updated Node.js buildpack v2.0-20150608-1503
: In this release, we synced our Node.js buildpack with the latest [CF community Node.js buildpack](https://github.com/cloudfoundry/nodejs-buildpack), which comes with a number of new features from the community.

In addition, we revamped the App Management feature in the Node.js buildpack, which enables utilities like shell, node-inspector, IBM Cloud Live Sync, and more. See [Managing Liberty and Node.js apps](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_management) for details.





 14 June 2015 

Updated Liberty buildpack v1.19-20150608-1717
(https://cloud.ibm.com/docs-content/v1/content/e0c3acba1296ff980e76d5db456d53adefaabba4/EventStreams/concepts_producers.png)

Figure 6. The diagram shows a producer publishing messages to one topic across three brokers.





 Consumers 

A consumer reads messages from one or more topics and processes them. The difference between a consumer's current position and the newest message on a partition is known as the offset lag.

If the lag increases over time, it is a sign that the consumer is not able to keep up. Over the short term, this is not an issue but eventually the consumer might miss messages if the retention period is exceeded.

For more information, see [Consuming messages](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-consuming_messagesconsuming_messages).

Zoom

![Consumers diagram.](https://cloud.ibm.com/docs-content/v1/content/e0c3acba1296ff980e76d5db456d53adefaabba4/EventStreams/concepts_consumers.png)

Figure 7. The diagram shows a consumer processing messages from one topic across three brokers.





 Consumer groups 

A consumer group contains one or more consumers that work together to process the messages. The messages from a single partition are processed by one consumer in each group.

At any time, each partition is assigned to only one consumer in the group. This assignment ensures that the messages on each partition are processed in order.

If more partitions than consumers exist in a group, some consumers have multiple partitions. If more consumers than partitions exist, some consumers have no partitions.

Zoom

![Consumer groups diagram.](https://cloud.ibm.com/docs-content/v1/content/e0c3acba1296ff980e76d5db456d53adefaabba4/EventStreams/concepts_consumer_groups.png)
"resources": [
{
"name": "encrypted-root-key",
"type": "application/vnd.ibm.kms.key+json",
"payload": "'"$ENCRYPTED_KEY"'",
"extractable": false,
"encryptionAlgorithm": "RSAES_OAEP_SHA_1",
"encryptedNonce": "'"$ENCRYPTED_NONCE"'",
"iv": "'"$IV"'"
}
]
}' > createRootKeyResponse.json
Show more

In the request body, you provide the encryption key that you prepared in the previous step. You also supply the encrypted nonce and the IV values that are required to verify the request. Finally, the extractable value set to false designates your new key as a root key in the service that you can use for envelope encryption.

If the API request fails with an import token expired error, [return to step 1](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-tutorial-import-keystutorial-import-create-token) to create a new import token. Remember that import tokens and their associated public keys expire based on the policy that you specify at creation time.
Use the IBM Key Protect CLI

ibmcloud kp key create new-imported-key --key-material "$ENCRYPTED_KEY" --encrypted-nonce "$ENCRYPTED_NONCE" --iv "$IV" --sha1 -o json > createRootKeyResponse.json

Behind the scenes, Hyper Protect Crypto Services receives your encrypted packet over a TLS 1.2 connection. Within a hardware security module, the system uses the private key to decrypt the symmetric key. Finally, the system uses the symmetric key and the IV to decrypt the nonce and verify the request.
* You can either use curl commands or an API REST Client such as [Postman](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-postman) to access the [Key Protect API](https://cloud.ibm.com/docs/key-protect?topic=key-protect-set-up-api).



3. Retrieve the CRN of the root key you use to enabled Key Protect on your bucket. The CRN looks similar to below:



crn:v1:bluemix:public:kms:us-south:a/3d624cd74a0dea86ed8efe3101341742:90b6a1db-0fe1-4fe9-b91e-962c327df531:key:0bg3e33e-a866-50f2-b715-5cba2bc93234





 Creating a bucket with key-protect enabled 

COS_KP_ALGORITHM = "<algorithm>"
COS_KP_ROOTKEY_CRN = "<root-key-crn>"

 Create a new bucket with key protect (encryption)
def create_bucket_kp(bucket_name):
print("Creating new encrypted bucket: {0}".format(bucket_name))
try:
cos.Bucket(bucket_name).create(
CreateBucketConfiguration={
"LocationConstraint":COS_BUCKET_LOCATION
},
IBMSSEKPEncryptionAlgorithm=COS_KP_ALGORITHM,
IBMSSEKPCustomerRootKeyCrn=COS_KP_ROOTKEY_CRN
)
print("Encrypted Bucket: {0} created!".format(bucket_name))
except ClientError as be:
print("CLIENT ERROR: {0}n".format(be))
except Exception as e:
print("Unable to create encrypted bucket: {0}".format(e))
Encrypt the nonce using the AES-CBC encryption algorithm. This algorithm method is only supported for HPCS. The default encryption algorithm is AES-GCM.

This option is used to generate an encrypted nonce that can only be used in a request with the HPCS API. Do not use this option to create Key Protect root keys.

Hyper Protect Crypto Services (HPCS) is a dedicated key management service and hardware security module (HSM). HPCS integrates with Key Protect to generate and encrypt keys. The Keep Your Own Key (KYOK) function is also enabled by HPCS.







 Notes 

For more information about HPCS, see [Getting started with IBM Cloud Hyper Protect Crypto Services](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-get-started).







 kp import-token show 

[Retrieve the import token](https://cloud.ibm.com/docs/key-protect?topic=key-protect-create-import-tokensretrieve-import-token-api) that is associated with your Key Protect instance.

The import token contains a public encryption key and a nonce. Provide the retrieved public key and nonce as arguments for ibmcloud kp import-token nonce-encrypt and ibmcloud kp import-token key-encrypt.

ibmcloud kp import-token show
-i, --instance-id INSTANCE_ID



 Example 

This example creates an import token and shows the results.

 create an import token that expires in 5 minutes and allows 10 retrievals
$ ibmcloud kp import-token create -e 300 -m 10

 show the created token
$ ibmcloud kp import-token show

{
"nonce": "8rf2ldP/zWm1Tjrb",
"payload":
"LS0tLS1CRUdJTiBQVUJMSUMgS0VZLS0t ...<redacted>... QyBLRVktLS0tLQo="
}
This option is used to generate an encrypted key that can only be used in a request with the HPCS API. Do not use this option to create Key Protect root keys.

Hyper Protect Crypto Services (HPCS) is a dedicated key management service and hardware security module (HSM). HPCS integrates with Key Protect to generate and encrypt keys. The Keep Your Own Key (KYOK) function is also enabled by HPCS.







 Notes 

For more information about HPCS, see [Getting started with IBM Cloud Hyper Protect Crypto Services](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-get-started).







 kp import-token nonce-encrypt 

Encrypt the nonce that is distributed by Key Protect with the key material that you import into to the service.

Then, provide the retrieved encrypted nonce and IV values when you run ibmcloud kp key create to import the key.

ibmcloud kp import-token nonce-encrypt
-i, --instance-id INSTANCE_ID
-k, --key KEY_MATERIAL
-n, --nonce NONCE
[-c, --cbc]



 Example 

This example encrypts the nonce using the key material.

A nonce is an arbitrary number that can be used just once in a cryptographic communication.

 create an import token that expires in 5 minutes and allows 10 retrievals
$ ibmcloud kp import-token create -e 300 -m 10

 create a random, base64-encoded, 32-byte key material
$ KEY_MATERIAL=$(openssl rand -base64 32)

 extract the nonce that was created by the "kp import-token create" command
$ NONCE=$(ibmcloud kp import-token show | jq -r '.["nonce"]')

 encrypt the nonce
$ ibmcloud kp import-token nonce-encrypt -k $KEY_MATERIAL -n $NONCE

Encrypted Nonce IV
If you want to create an encrypted PVC by using one of the IBM-provided storage classes, you can do this by [referencing the Key Protect credentials directly in your PVC](https://cloud.ibm.com/docs/containers?topic=containers-block_storagepvc_encrypt_label).



1. [Decide on a storage configuration](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_predefined_storageclass).
2. Create a custom storage class that provisions an encrypted block storage instance by using one of the IBM-provided storage classes as the basis. You can retrieve the details a storage class by running kubectl get storageclass <storageclass_name> -o yaml. The following example is based on the ibmc-block-retain-bronze storage class.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: <name> Enter the name of the storage class. Example: my_custom_storageclass
parameters:
billingType: hourly
classVersion: "2"
fsType: ext4
iopsPerGB: "2"
sizeRange: '[20-12000]Gi'
type: Endurance
encrypted: "true" Enter "true" to enable encryption.
encryptionKeySecret: <secret_name> nter the name of the secret that you created earlier.Example: my_secret
encryptionKeyNamespace: <namespace> nter the namespace where you created your secret. Example: default
provisioner: ibm.io/ibmc-block
reclaimPolicy: Delete
volumeBindingMode: Immediate
Show more
3. Create the storage class in your cluster.

kubectl apply -f storageclass.yaml
4. [Add Block Storage for Classic to your app by using your custom storage class to create a PVC](https://cloud.ibm.com/docs/containers?topic=containers-block_storageadd_block).
Complete the following steps to create the user-data.yamlfile that is used as the contract.



1. Copy the following workload section of the contract that is generated via an automated process, into the user-data.yamlfile. This workload section contains the encrypted details of the SBS image. Use the following workload section of the contract for the IBM Hyper Protect Container Runtime image version ibm-hyper-protect-container-runtime-1-0-s390x-9.

hyper-protect-basic.JNNGRfeic/H4j5XcOLMMCA2KrAUpUu5+gcO54oTZwBbMjYbH9divTW3zBBBO/p/RnhBsVYiA5HAYPmz0JLkKuRWu75MZwGuV+j8Sc+TxpRSLznRdHbZfSNCfzOxjkiWwKweDZrHkzVVulwXXAQmL7/+JyxTt+AWYsQcRuUfQSnrKmbNQ74HKaEXQF0sV1S8zGtPZbDrx5jbcgb3fr98rACklxBdygZg22a+mZiJh6BsGcgRGcM73TCkrawRNGUDJpSSuo4YJc4z+qwa0jZeyNOUCBl5kM02IFvQQX5SrRwOU/+qcoMNxmB1u4Tf5WZcetn+b9hLeV9nx/4Tg/jLk7xq0QkBqt7Po/aA7qKFIaXjD9NWC6sKUTw/xvgzDqK1UhBfRIsWBiMGAm5C8yfHrrloN0cx1cKab5laswDFANqTOZH6TpkUmKbJt1
CRN crn:v1:bluemix:public:is:us-east-1:a/a10d63fa66daffc9b9b5286ce1533080::volume:r014-3984600c-6f4d-4940-82de-519a867fa3c0
Status pending
Attachment state unattached
Capacity 300
IOPS 1500
Bandwidth(Mbps) 3145
Profile custom
Encryption key crn:v1:bluemix:public:kms:us-east:a/a10d63fa66daffc9b9b5286ce1533080:3b05b403-8f51-4dac-9114-c777d0a760d4:key:7a8a2761-08e3-455f-a348-144ed604bba9
Encryption user_managed
Resource group defaults
Created 2023-06-29T20:10:52+00:00
Zone us-east-1
Health State inapplicable
Volume Attachment Instance Reference -
Active false
Unattached capacity update supported false
Unattached iops update supported false
Busy false
Tags -

You can also create volumes with customer-managed encryption during instance provisioning. For more information, see [Provisioning instances with customer-managed encrypted volumes from the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-instances-byokprovision-byok-cli).





 Creating customer-managed encryption data volumes with the API 

You can create data volumes with customer-managed encryption by calling the [Virtual Private Cloud (VPC) API](https://cloud.ibm.com/apidocs/vpc).

Make a POST /volumes request to create a volume encrypted using your own encryption keys. Use the encryption_key parameter to specify your customer root key (CRK), shown in the example as crn:[...key:...].
: Removed outdated [subnet IP addresses for IBM Cloud Container Registry](https://cloud.ibm.com/docs/containers?topic=containers-firewallvyatta_firewall).





 17 February 2020 

Kubernetes version 1.17
: [Kubernetes 1.17 release is certified](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsk8s_version_archive).

Version change logs
: Master and worker node patch updates.
: Kubernetes [1.17.3_1516](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog1173_1516), [1.16.7_1524](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog1167_1524), [1.15.10_1531](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog11510_1531), [1.14.10_1547](https://cloud.ibm.com/docs/containers?topic=containers-114_changelog11410_1547), and [1.13.12_1550](https://cloud.ibm.com/docs/containers?topic=containers-113_changelog11312_1550)





 14 February 2020 

Istio add-on
: [Version 1.4.4 of the Istio managed add-on](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog144) is released.





 10 February 2020 

New! Kubernetes version 1.17
: You can now create clusters that run Kubernetes version 1.17. To update an existing cluster, see the [Version 1.17 preparation actions](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsk8s_version_archive).

Deprecated: Kubernetes version 1.14
IBM Cloud Container Registry N/A N/A Added private-only registry support for ca.icr.io, br.icr.io and jp2.icr.io. 
 Ubuntu 18.04 packages N/A N/A Updated worker node images with package updates for [CVE-2017-8779](https://nvd.nist.gov/vuln/detail/CVE-2017-8779), [CVE-2017-8872](https://nvd.nist.gov/vuln/detail/CVE-2017-8872), [CVE-2018-16869](https://nvd.nist.gov/vuln/detail/CVE-2018-16869), [CVE-2019-20388](https://nvd.nist.gov/vuln/detail/CVE-2019-20388), [CVE-2020-24977](https://nvd.nist.gov/vuln/detail/CVE-2020-24977), [CVE-2021-3516](https://nvd.nist.gov/vuln/detail/CVE-2021-3516), [CVE-2021-3517](https://nvd.nist.gov/vuln/detail/CVE-2021-3517)[CVE-2021-3518](https://nvd.nist.gov/vuln/detail/CVE-2021-3518), [CVE-2021-3537](https://nvd.nist.gov/vuln/detail/CVE-2021-3537), [CVE-2021-3580](https://nvd.nist.gov/vuln/detail/CVE-2021-3580). 







 Change log for worker node fix pack 1.18.19_1554, released 7 June 2021 

The following table shows the changes that are in the worker node fix pack 1.18.19_1554.
IBM Cloud Container Registry N/A N/A Added private-only registry support for ca.icr.io, br.icr.io and jp2.icr.io. 
 Ubuntu 18.04 packages N/A N/A Updated worker node images with package updates for [CVE-2017-8779](https://nvd.nist.gov/vuln/detail/CVE-2017-8779), [CVE-2017-8872](https://nvd.nist.gov/vuln/detail/CVE-2017-8872), [CVE-2018-16869](https://nvd.nist.gov/vuln/detail/CVE-2018-16869), [CVE-2019-20388](https://nvd.nist.gov/vuln/detail/CVE-2019-20388), [CVE-2020-24977](https://nvd.nist.gov/vuln/detail/CVE-2020-24977), [CVE-2021-3516](https://nvd.nist.gov/vuln/detail/CVE-2021-3516), [CVE-2021-3517](https://nvd.nist.gov/vuln/detail/CVE-2021-3517)[CVE-2021-3518](https://nvd.nist.gov/vuln/detail/CVE-2021-3518), [CVE-2021-3537](https://nvd.nist.gov/vuln/detail/CVE-2021-3537), [CVE-2021-3580](https://nvd.nist.gov/vuln/detail/CVE-2021-3580). 







 Change log for worker node fix pack 1.20.7_1542, released 7 June 2021 

The following table shows the changes that are in the worker node fix pack 1.20.7_1542.
IBM Cloud Container Registry N/A N/A Added private-only registry support for ca.icr.io, br.icr.io and jp2.icr.io. 
 Ubuntu 18.04 packages N/A N/A Updated worker node images with package updates for [CVE-2017-8779](https://nvd.nist.gov/vuln/detail/CVE-2017-8779), [CVE-2017-8872](https://nvd.nist.gov/vuln/detail/CVE-2017-8872), [CVE-2018-16869](https://nvd.nist.gov/vuln/detail/CVE-2018-16869), [CVE-2019-20388](https://nvd.nist.gov/vuln/detail/CVE-2019-20388), [CVE-2020-24977](https://nvd.nist.gov/vuln/detail/CVE-2020-24977), [CVE-2021-3516](https://nvd.nist.gov/vuln/detail/CVE-2021-3516), [CVE-2021-3517](https://nvd.nist.gov/vuln/detail/CVE-2021-3517)[CVE-2021-3518](https://nvd.nist.gov/vuln/detail/CVE-2021-3518), [CVE-2021-3537](https://nvd.nist.gov/vuln/detail/CVE-2021-3537), [CVE-2021-3580](https://nvd.nist.gov/vuln/detail/CVE-2021-3580). 







 Change log for worker node fix pack 1.17.17_1565, released 7 June 2021 

The following table shows the changes that are in the worker node fix pack 1.17.17_1565.
IBM Cloud Container Registry N/A N/A Added private-only registry support for ca.icr.io, br.icr.io and jp2.icr.io. 
 Ubuntu 18.04 packages N/A N/A Updated worker node images with package updates for [CVE-2017-8779](https://nvd.nist.gov/vuln/detail/CVE-2017-8779), [CVE-2017-8872](https://nvd.nist.gov/vuln/detail/CVE-2017-8872), [CVE-2018-16869](https://nvd.nist.gov/vuln/detail/CVE-2018-16869), [CVE-2019-20388](https://nvd.nist.gov/vuln/detail/CVE-2019-20388), [CVE-2020-24977](https://nvd.nist.gov/vuln/detail/CVE-2020-24977), [CVE-2021-3516](https://nvd.nist.gov/vuln/detail/CVE-2021-3516), [CVE-2021-3517](https://nvd.nist.gov/vuln/detail/CVE-2021-3517)[CVE-2021-3518](https://nvd.nist.gov/vuln/detail/CVE-2021-3518), [CVE-2021-3537](https://nvd.nist.gov/vuln/detail/CVE-2021-3537), [CVE-2021-3580](https://nvd.nist.gov/vuln/detail/CVE-2021-3580). 







 Change log for worker node fix pack 1.19.11_1549, released 7 June 2021 

The following table shows the changes that are in the worker node fix pack 1.19.11_1549.
IBM Cloud Container Registry N/A N/A Added private-only registry support for ca.icr.io, br.icr.io and jp2.icr.io. 
 RHEL 7 Packages 3.10.0-1160.25 3.10.0-1160.31 Updated worker node image with kernel package updates for [CVE-2020-8648](https://nvd.nist.gov/vuln/detail/CVE-2020-8648), [CVE-2020-12362](https://nvd.nist.gov/vuln/detail/CVE-2020-12362)[CVE-2020-12363](https://nvd.nist.gov/vuln/detail/CVE-2020-12363)[CVE-2020-12364](https://nvd.nist.gov/vuln/detail/CVE-2020-12364)[CVE-2020-27170](https://nvd.nist.gov/vuln/detail/CVE-2020-27170)[CVE-2021-3347](https://nvd.nist.gov/vuln/detail/CVE-2021-3347), [CVE-2020-24489](https://nvd.nist.gov/vuln/detail/CVE-2020-24489), [CVE-2020-24511](https://nvd.nist.gov/vuln/detail/CVE-2020-24511)[CVE-2020-24512](https://nvd.nist.gov/vuln/detail/CVE-2020-24512), [CVE-2020-24513](https://nvd.nist.gov/vuln/detail/CVE-2020-24513) and [CVE-2021-25217](https://nvd.nist.gov/vuln/detail/CVE-2021-25217). 







 Change log for worker node fix pack 4.5.40_1541_openshift, released 7 June 2021
IBM Cloud Container Registry N/A N/A Added private-only registry support for ca.icr.io, br.icr.io and jp2.icr.io. 
 Ubuntu 18.04 packages N/A N/A Updated worker node images with package updates for [CVE-2017-8779](https://nvd.nist.gov/vuln/detail/CVE-2017-8779), [CVE-2017-8872](https://nvd.nist.gov/vuln/detail/CVE-2017-8872), [CVE-2018-16869](https://nvd.nist.gov/vuln/detail/CVE-2018-16869), [CVE-2019-20388](https://nvd.nist.gov/vuln/detail/CVE-2019-20388), [CVE-2020-24977](https://nvd.nist.gov/vuln/detail/CVE-2020-24977), [CVE-2021-3516](https://nvd.nist.gov/vuln/detail/CVE-2021-3516), [CVE-2021-3517](https://nvd.nist.gov/vuln/detail/CVE-2021-3517)[CVE-2021-3518](https://nvd.nist.gov/vuln/detail/CVE-2021-3518), [CVE-2021-3537](https://nvd.nist.gov/vuln/detail/CVE-2021-3537), [CVE-2021-3580](https://nvd.nist.gov/vuln/detail/CVE-2021-3580). 







 Change log for worker node fix pack 1.21.1_1520, released 9 June 2021 

The following table shows the changes that are in the worker node fix pack 1.21.1_1520.
Define the deployment and the image to use from your namespace in IBM Cloud Container Registry.

apiVersion: apps/v1
kind: Deployment
metadata:
name: <deployment>
spec:
replicas: <number_of_replicas>
selector:
matchLabels:
app: <app_name>
template:
metadata:
labels:
app: <app_name>
spec:
containers:
- name: <app_name>
image: <region>.icr.io/<namespace>/<image>:<tag>
Show more

<deployment>
: Give your deployment a name.

<number_of_replicas>
: Enter the number of replica pods that the deployment creates.

app: <app_name>
: Use the name of your app as a label for the container.

name: <app_name>
: Give your container a name, such as the name of your app label.

image: <region>.icr.io/namespace>/image>:tag>
: Replace the image URL variables with the information for your image:
: region>: The regional IBM Cloud Container Registry API endpoint for the registry domain. To list the domain for the region that you are logged in to, run ibmcloud cr api.
: namespace>: The registry namespace. To get your namespace information, run ibmcloud cr namespace-list.
: image>:tag>: The image and tag that you want to use for your container. To list the images that are available in your registry namespace, run ibmcloud cr images.
3. Create the deployment in your cluster.

kubectl apply -f <deployment>.yaml







 Referring to the image pull secret in your pod deployment 

If the cluster administrator did not [store the image pull secret in the Kubernetes service account](https://cloud.ibm.com/docs/containers?topic=containers-registryuse_imagePullSecret), all deployments that don't specify a service account can't use the image pull secret to deploy containers.
* Log in to IBM Cloud by running ibmcloud login. Then, log in to the IBM Cloud Container Registry CLI by running [ibmcloud cr login](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_login).
* [Review quota limits and usage](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota_get). For more information, see [Staying within quota limits](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota_freeup).
* Upgrade to a standard plan. For more information, see [Upgrading your service plan](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overview&interface=uiregistry_plan_upgrade).