vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For users with accounts that have access to file shares, a new dp2 profile is now available when [creating](https://cloud.ibm.com/apidocs/vpc-betacreate-share) and [updating](https://cloud.ibm.com/apidocs/vpc-betaupdate-share) a file share. Profiles in the existing custom and tiered families have been deprecated and will remain available only to accounts that have already provisioned file shares with those profiles. The deprecated profiles also will not be included in the upcoming general availability release for file shares.

The dp2 profile belongs to a new defined_performance file share profile family, which provides similar functionality to the deprecated custom file share profile family. While existing file shares using profiles in the custom and tiered families will continue to work, you are encouraged to update all your file shares to the new dp2 profile in preparation for general availability of the file share service. Bulk migration of existing file shares is not supported. For more information, see [dp2 file storage profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesdp2-profile).







 14 February 2023 



 For all version dates 

Exporting custom images. Accounts that have been granted special approval to preview this feature can now [export custom images](https://cloud.ibm.com/apidocs/vpc-betacreate-image-export-job) to an authorized IBM Cloud Object Storage bucket. Specify the target storage_bucket to export the image to. The image will be exported as qcow2 unless you specify another value using the format property.

For more information, see [Exporting a custom image to IBM Cloud Object Storage](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-custom-images&interface=apicustom-image-export-to-cos-api), or start using the new [export jobs](https://cloud.ibm.com/apidocs/vpc-betalist-image-export-jobs) methods.

This feature is now generally available.
* UI
* CLI
* API
* Terraform







 Creating backup policies and plans 

You can create backup policies for your Block Storage for VPC volumes in the UI, from the CLI, with the API, or Terraform. You can create up to four backup plans to schedule backup creation and retention. Specify user tags in the policy to make sure that your data is backed up regularly. Create backups on schedule when the tags that are applied to a volume match the tags in a backup policy.



 Before you begin 



1. Establish IAM user roles to grant [service-to-service authorizations](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-s2s-authbackup-s2s-auth-overview) so the backup service can detect volume tags and create backups.
2. Create user tags for new or existing data volumes that you can associate with a backup policy. For more information about adding tags, see [Apply tags to resources for backup policies](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-use-policies). For more information about creating tags, see [Working with tags](https://cloud.ibm.com/docs/account?topic=account-tag).



You're not required to create a backup plan when you create a backup policy, but it's good practice to create at least one backup plan with your policy.





 Creating a backup policy and plan in the UI 

You can use the UI to create a backup policy and plan.



 Creating a backup policy in the UI 

Use the following steps to create a backup policy by using the UI.



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Backup policies. The Create tab is selected by default.

The UI diplays a notification message when service-to-service authorizations are incorrect or missing on your account.
<br><br> * [Working with Spark SQL and an external metastore](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-external-metastore)<br><br><br> 
 Running applications with resource overcommitment There is a quota associated with each Analytics Engine Serverless instance. When applications are submitted on an instance, they are allocated resources from the instance quota. If an application requests resources beyond the available quota, the application will either not start or will run with less than the requested resources, which might result in the application running slower than expected or, in some cases, in the application failing. You should always monitor the current resource consumption on an instance to ensure that your applications are running comfortably within the given limits. You can adjust the limits through a support ticket if required. <br><br> * [Default limits and quotas](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-limits)<br> * [Get current resource consumption](https://cloud.ibm.com/apidocs/ibm-analytics-engine/ibm-analytics-engine-v3get-current-resource-consumption)<br><br><br> 
 Static allocation of resources versus autoscaling When you submit applications, you can specify the number of executors upfront (static allocation) or use the autoscaling option (dynamic allocation). Before you decide whether to use static allocation or autoscaling, you might want to run a few benchmarking tests by varying different data sets with both static and autoscaling to find the right configuration. General considerations:<br><br><br><br> * If you know the number of resources (cores and memory) required by your application and it doesn't vary across different stages of the application run, it is recommended to allocate static resources for better performance.<br> * If you want to go for an optimized resource utilization, you can opt for autoscaling of executors where the executors are allotted based on the application's actual demand.
A script and tool will assist you to simulate the transmission of web server log messages from a static file to Event Streams.

Object Storage Event Streams

+3

Analytics Engine,Data Engine,Key Protect



* 3 hours
* 2023-05-05



[Getting started with Secrets Manager](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-getting-started)Getting started with Secrets Manager

This tutorial focuses on storing and managing a username and password in IBM Cloud® Secrets Manager. With Secrets Manager, you can create, lease, and centrally manage secrets that are used in IBM Cloud services or your custom-built applications. Secrets are stored in a dedicated Secrets Manager instance, built on open source HashiCorp Vault.

Secrets Manager



* 10 minutes
* 2023-03-01



[Access a storage bucket by using a dynamic secret](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-tutorial-access-storage-bucket)Access a storage bucket by using a dynamic secret

In this tutorial, you learn how to use IBM Cloud® Secrets Manager to create and lease an IAM credential that can be used to access a bucket in Cloud Object Storage.

Secrets Manager Object Storage



* 1 hour
* 2023-05-30



[Secure secrets for apps that run in your Kubernetes cluster](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-tutorial-kubernetes-secrets)Secure secrets for apps that run in your Kubernetes cluster

This tutorial is for the Classic flavor of Kubernetes Service clusters. External Secrets is also available as an OpenShift operator.

Secrets Manager



* 45 minutes
* 2023-06-15



[Part 2: Create a GitHub issue when your certificates are about to expire](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-tutorial-expiring-secrets-part-2)Part 2: Create a GitHub issue when your certificates are about to expire
: The directory in the repository that contains the buildpacks file or the Dockerfile. This value is optional.

--dockerfile, --df
: The path to the Dockerfile. Specify this option only if the name is other than Dockerfile. This value is optional. The default value is Dockerfile.

--force, -f
: Do not verify the existence of specified secret references. Secret references are specified with the --get-repo-secret or --registry-secret options. This value is optional. The default value is false.

--git-repo-secret, --grs, --repo, -r
: The name of the SSH secret, which contains the credentials to access the private repository that contains the source code to build your container image. To create this SSH secret, use the secret create --format SSH command. An SSH secret is also used as a Git repository access secret. This value is optional.

--git-repo-secret-clear, --grsc
: Clear the SSH secret. This value is optional. The default value is false.

--image, -i
: The location of the image registry. The format is REGISTRY/NAMESPACE/REPOSITORY:TAG where TAG is optional. If TAG is not specified, the default is latest. This value is optional.

--output, -o
: Specifies the format of the command output. Valid values are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.

--registry-secret, --rs
: The name of the registry secret. The registry secret is used to authenticate with a private registry when you download the container image.
: Required: Specify a name for the secret. Make sure that you don't create the secret with the same name as the IBM-provided Ingress secret, which you can find by running ibmcloud ks cluster get --cluster <cluster_name_or_ID> | grep Ingress.

--field CRN
: Required for non-TLS secrets. Add a field to the secret. You can specify more than one field at a time. For more information, see [Managing non-TLS secret fields](https://cloud.ibm.com/docs/containers?topic=containers-secretsnon-tls-field). This option is not supported for TLS secrets.



* To pull in the secret with the default field name for the secret type, use the default field option: --field <crn>. This option is available for all non-TLS secret types.
* To specify the field name, use the named field option: --field name=<crn>. This option is available for arbitrary and IAM credential secret types.
* To use the IBM Cloud Secrets Manager secret as the prefix, use the prefixed field option: --field prefix=<crn>. This option is available for IAM credential, username and password, and key value secret types.



--namespace NAMESPACE
: Optional: Specify the namespace that your Ingress resource is deployed to. If your ALB runs the Kubernetes Ingress image, this value is required, because the ALB can identify secrets only in the same namespace as your Ingress resource. If your ALB runs the IBM Cloud Kubernetes Service Ingress image, and you don't specify a namespace, the certificate secret is created in a namespace called ibm-cert-store. A reference to this secret is then created in the default namespace, which any Ingress resource in any namespace can access. While processing requests, the ALB follows the reference to pick up and use the certificate secret from the ibm-cert-store namespace.

--persist
: Optional: Persist the secret data in your cluster.
You can specify more than one field at a time. For more information, see [Managing non-TLS secret fields](https://cloud.ibm.com/docs/containers?topic=containers-secretsnon-tls-field).



* To pull in the secret with the default field name for the secret type, use the default field option: --field <crn>. This option is available for all non-TLS secret types.
* To specify the field name, use the named field option: --field name=<crn>. This option is available for arbitrary and IAM credential secret types.
* To use the IBM Cloud Secrets Manager secret as the prefix, use the prefixed field option: --field prefix=<crn>. This option is available for IAM credential, username and password, and key value secret types.



--namespace NAMESPACE
: Required. The namespace that the secret is deployed to.

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

Example to add default, named, and prefixed fields to a set of IAM credentials:

ibmcloud ks ingress secret field add --cluster example-cluster --name example-iam-secret --namespace default --field crn:v1:bluemix:public:secrets-manager:us-south:a/1aa111aa1a11111aaa1a1111aa1aa111:111a1111-11a1 --field unique_iam_name=crn:v1:bluemix:public:secrets-manager:us-south:a/1aa111aa1a11111aaa1a1111aa1aa111:111a1111-11a1 --field prefix=crn:v1:bluemix:public:secrets-manager:us-south:a/1aa111aa1a11111aaa1a1111aa1aa111:111a1111-11a1





 ibmcloud ks ingress secret field ls 

Virtual Private Cloud

Classic infrastructure

View the CRN fields of an Ingress secret. This command applies only to Opaque secrets.
Accelerate a dynamic website using Dynamic Content Acceleration 

This tutorial may incur costs. Use the [Cost Estimator](https://cloud.ibm.com/estimator/review) to generate a cost estimate based on your projected usage.

Web applications are composed of static content like text, images, cascading style sheets, and JavaScript files. The tutorial [Accelerate delivery of static files using a CDN](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-static-files-cdn) shows how to host and serve static assets (images, videos, and documents) of a website from IBM Cloud Object Storage with [IBM® Content Delivery Network (CDN)](https://cloud.ibm.com/catalog/infrastructure/cdn-powered-by-akamai).

Applications also contain personalized and dynamically changing contents that can’t be cached at CDN. A common example of non-cacheable dynamic content is adding an item to a cart in an e-commerce website that might be generated from JavaScript on the base page. Before Dynamic Content Acceleration is available, a CDN will pass every request for a non-cacheable object through to the owner’s origin server, and pass the result back to the user.

To stop these dynamic contents from being a performance bottleneck, you can utilize the new Dynamic Content Acceleration (DCA) capability of [IBM® Content Delivery Network (CDN)](https://cloud.ibm.com/catalog/infrastructure/cdn-powered-by-akamai) to optimize the performance of dynamic contents:



* the DCA capability of CDN will choose the optimal routes for requests
* proactively pre-fetch contents from origin servers so that users can access these contents rapidly from the edge
* extend the duration of TCP connections for multiple requests
* automatically compress images for lower latency.





 Objectives 



* Deploy a sample dynamic web application to a Kubernetes Service cluster.
* Make static content globally available with IBM® Content Delivery Network.
* Enable the Dynamic Content Acceleration (DCA) capability for performance optimization of non-static content.



Zoom

!
If the type of build is local, then the --source, --commit, and --git-repo-secret options are not valid. This value is optional. The default value is git.

--commit, --cm, --revision
: The commit, tag, or branch in the source repository to pull. The commit option is allowed if the --build-type option is git and not allowed if the --build-type option is local. This value is optional.

--context-dir, --cdr
: The directory in the repository that contains the buildpacks file or the Dockerfile. This value is optional.

--dockerfile, --df
: The path to the Dockerfile. Specify this option only if the name is other than Dockerfile. This value is optional. The default value is Dockerfile.

--force, -f
: Do not verify the existence of specified secret references. Secret references are specified with the --get-repo-secret or --registry-secret options. This value is optional. The default value is false.

--git-repo-secret, --grs, --repo, -r
: The name of the SSH secret, which contains the credentials to access the private repository that contains the source code to build your container image. To create this SSH secret, use the secret create --format SSH command. An SSH secret is also used as a Git repository access secret. This option is allowed if the --build-type option is git and not allowed if the --build-type option is local. This value is optional.

--image, -i
: The location of the image registry. The format is REGISTRY/NAMESPACE/REPOSITORY:TAG where TAG is optional. If TAG is not specified, the default is latest. This value is optional.

--output, -o
: Specifies the format of the command output.
run show configuration commands | grep name-server
set system name-server '10.0.80.11'
set system name-server '10.0.80.12'

The hash mark () indicates configuration mode. Beginning a command with run indicates to the VRA shell that an operational command is being presented. The previous example also illustrates the ability to "grep" against the output of commands.





 Command exploration 

The VRA command shell includes tab completion capabilities. If you are curious about which commands are available, press the Tab key for a list and a short explanation. This works both at the shell prompt and while typing a command. For instance:

$show log dns [Press tab]
Possible completions:
dynamic Show log for Dynamic DNS
forwarding Show log for DNS Forwarding





 Sample configuration 

Configurations are laid out in a hierarchical pattern of nodes. Consider this static route block:

show protocols static

protocols {
static {
route 10.0.0.0/8 {
next-hop 10.60.63.193 {
}
}
route 192.168.1.0/24 {
next-hop 10.0.0.1 {
}
}
}
}

This is generated by the commands:

set protocols static route 10.0.0.0/8 next-hop 10.60.63.193
set protocols static route 192.168.1.0/24 next-hop 10.0.0.1

This example illustrates that it is possible for a node (static) to have multiple child nodes. To remove the route for 192.168.1.0/24 the command delete protocols static route 192.168.1.0/24 is used. If 192.168.1.0/24 was left off the command, then both route nodes are marked for deletion.

Remember that the configuration is not actually changed until the commit command is issued. To compare the current running configuration to any changes that are present in the configuration buffer, use the compare command. To flush the configuration buffer, use discard.





 Users and Role-based Access Control (RBAC)
If you do not have a Secrets Manager instance and your secrets are instead written directly to your cluster, your secrets do not have the required CRN value and you must manage them with oc commands.

ibmcloud oc ingress secret create --cert-crn CERTIFICATE_CRN --cluster CLUSTER --name SECRET_NAME [--namespace NAMESPACE] [--field CRN] [--persist] [--type] [-q]

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

Command options:

--cert-crn CERTIFICATE_CRN
: Required: The certificate CRN.

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

--name SECRET_NAME
: Required: Specify a name for the secret. Make sure that you don't create the secret with the same name as the IBM-provided Ingress secret, which you can find by running ibmcloud oc cluster get --cluster <cluster_name_or_ID> | grep Ingress.

--field CRN
: Required for non-TLS secrets. Add a field to the secret. You can specify more than one field at a time. For more information, see [Managing non-TLS secret fields](https://cloud.ibm.com/docs/containers?topic=containers-secretsnon-tls-field). This option is not supported for TLS secrets.



* To pull in the secret with the default field name for the secret type, use the default field option: --field <crn>. This option is available for all non-TLS secret types.
* To specify the field name, use the named field option: --field name=<crn>. This option is available for arbitrary and IAM credential secret types.
* To use the IBM Cloud Secrets Manager secret as the prefix, use the prefixed field option: --field prefix=<crn>. This option is available for IAM credential, username and password, and key value secret types.



--namespace NAMESPACE
If a service access secret does exist, to create a new service access secret with a new service credential for this binding, select New secret. Complete the following steps.



1. Select the Role for the service instance credential.
2. Expand Advanced options.
3. Select the service credential to use with this service access secret.
4. (optional) Specify a custom prefix for the service binding. If you do not specify a custom prefix, Code Engine automatically generates a prefix. The prefix is used to distinguish environment variables that are created for this service binding.



7. Click Add to create the service binding.
8. Now that your service binding to your app or job is created from the console, you can view a list of all defined service bindings between service instances and Code Engine apps and jobs from the Service bindings page.



Alternatively, you can also create and manage service bindings to specific apps and jobs from the specific Code Engine app or job page in the console. To work with service bindings within the context of your app or job, go to the Service bindings tab for your specific app or job.





 Binding a service instance with an existing service access secret 

You can reuse service access secrets in service bindings. For a specific IBM Cloud service instance, you can reuse service access secrets with different apps or jobs. You cannot reuse a service access secret for the same app or job that the service access secret was originally created for. Since the service credential is stored within the service access secret, it is important to consider the following points:



* You can have more than one app or job that is bound to the same IBM Cloud service instance with the same service access secret.
* A service access secret cannot be reused in a service binding for the same app or job. However, you can reuse the same service access secret in a different app or job. Because a service access secret is associated with a specific IBM Cloud service instance, you can reuse only the service access secret in a different app or job, if you are binding to the same service instance.



Let's create a service binding to bind a service instance to a job that uses an existing service access secret.
--build-commit-clear, --commit-clear, --bcmc, --cmc
: Clear the commit, tag, or branch in the source repository to pull. The commit clear option is allowed only if your job currently has an associated build. This value is optional. The default value is false.

--build-context-dir, --context-dir, --bcdr, --cdr
: The directory in the repository that contains the buildpacks file or the Dockerfile. The build context directory option is allowed only if the --build-source option is set on this job update command, or your job currently has an associated build. This value is optional.

--build-dockerfile, --dockerfile, --bdf, --df
: The path to the Dockerfile. Specify this option only if the name is other than Dockerfile. The build dockerfile option is allowed if the --build-source option is set on this job update command, or your job currently has an associated build. This value is optional. The default value is Dockerfile.

--build-git-repo-secret, --git-repo-secret, --bgrs, --grs, --repo
: The name of the SSH secret, which contains the credentials to access the private repository that contains the source code to build your container image. To create this SSH secret, use the secret create --format SSH command. An SSH secret is also used as a Git repository access secret. This option is allowed only if the --build-source option is set to the URL of a Git repository on this job update command, or your job currently has an associated build from a Git repository source. This value is optional.

--build-git-repo-secret-clear, --git-repo-secret-clear, --bgrsc, --grsc
: Clear the SSH secret. This option is allowed if your job currently has an associated build. This value is optional.