vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you haven't already, clone the app in one of the available languages to your local environment from your console by using the following command

git clone -b <language> git@github.com:IBM-Cloud/clouddatabases-helloworld-kubernetes-examples.git
7. cd into this newly created directory, and cd into the database folder. The code for connecting to the service, and reading from and updating the database can be found in server.js. See [Code Structure](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-tutorial-k8s-appcode-structures) and the code comments for information on the app's functions. A public directory contains the html, stylesheets, and JavaScript for the web app. However, to get the application to work, we first need to push the Docker image of this application to our Container Registry.
8. Build and push the application's Docker image to your Container Registry. Specify the appropriate region and give the container a name.

ibmcloud cr build -t <region>.icr.io/<namespace>/<container_name> .

You can view the image in container registry by using

ibmcloud cr images

You get something like the following response

REPOSITORY TAG DIGEST NAMESPACE CREATED SIZE SECURITY STATUS
<region>.icr.io/mynamespace/container_name latest 81c3959ea657 mynamespace 4 hours ago 28 MB No Issues
9. Update the Kubernetes deployment configuration file clouddb-deployment.yaml.

Change the image name to the repository name that you got from the previous step:

image: "<region>.icr.io/mynamespace/<container_name>" Edit me

Now, under secretKeyRef, change the name of <db-secret-name> to match the name of the secret that was created when you bound your database deployment to your Kubernetes cluster.

secretKeyRef:
name: <db-secret-name> Edit me
If you haven't already, clone the app in one of the available languages to your local environment from your console by using the following command

git clone -b <language> git@github.com:IBM-Cloud/clouddatabases-helloworld-kubernetes-examples.git
7. cd into this newly created directory, and cd into the database folder. The code for connecting to the service, and reading from and updating the database can be found in server.js. See [Code Structure](https://cloud.ibm.com/docs/databases-for-mongodb?topic=databases-for-mongodb-tutorial-k8s-appcode-structures) and the code comments for information on the app's functions. A public directory contains the html, stylesheets, and JavaScript for the web app. However, to get the application to work, we first need to push the Docker image of this application to our Container Registry.
8. Build and push the application's Docker image to your Container Registry. Specify the appropriate region and give the container a name.

ibmcloud cr build -t <region>.icr.io/<namespace>/<container_name> .

You can view the image in container registry by using

ibmcloud cr images

You get something like the following response

REPOSITORY TAG DIGEST NAMESPACE CREATED SIZE SECURITY STATUS
<region>.icr.io/mynamespace/container_name latest 81c3959ea657 mynamespace 4 hours ago 28 MB No Issues
9. Update the Kubernetes deployment configuration file clouddb-deployment.yaml.

Change the image name to the repository name that you got from the previous step:

image: "<region>.icr.io/mynamespace/<container_name>" Edit me

Now, under secretKeyRef, change the name of <db-secret-name> to match the name of the secret that was created when you bound your database deployment to your Kubernetes cluster.

secretKeyRef:
name: <db-secret-name> Edit me
If you haven't already, clone the app in one of the available languages to your local environment from your console by using the following command

git clone -b <language> git@github.com:IBM-Cloud/clouddatabases-helloworld-kubernetes-examples.git
7. cd into this newly created directory, and cd into the database folder. The code for connecting to the service, and reading from and updating the database can be found in server.js. See [Code Structure](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-tutorial-k8s-appcode-structures) and the code comments for information on the app's functions. A public directory contains the html, stylesheets, and JavaScript for the web app. However, to get the application to work, we first need to push the Docker image of this application to our Container Registry.
8. Build and push the application's Docker image to your Container Registry. Specify the appropriate region and give the container a name.

ibmcloud cr build -t <region>.icr.io/<namespace>/<container_name> .

You can view the image in container registry by using

ibmcloud cr images

You get something like the following response

REPOSITORY TAG DIGEST NAMESPACE CREATED SIZE SECURITY STATUS
<region>.icr.io/mynamespace/container_name latest 81c3959ea657 mynamespace 4 hours ago 28 MB No Issues
9. Update the Kubernetes deployment configuration file clouddb-deployment.yaml.

Change the image name to the repository name that you got from the previous step:

image: "<region>.icr.io/mynamespace/<container_name>" Edit me

Now, under secretKeyRef, change the name of <db-secret-name> to match the name of the secret that was created when you bound your database deployment to your Kubernetes cluster.

secretKeyRef:
name: <db-secret-name> Edit me
If you haven't already, clone the app in one of the available languages to your local environment from your console by using the following command

git clone -b <language> git@github.com:IBM-Cloud/clouddatabases-helloworld-kubernetes-examples.git
7. cd into this newly created directory, and cd into the database folder. The code for connecting to the service, and reading from and updating the database can be found in server.js. See [Code Structure](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-tutorial-k8s-appcode-structures) and the code comments for information on the app's functions. A public directory contains the html, stylesheets, and JavaScript for the web app. However, to get the application to work, we first need to push the Docker image of this application to our Container Registry.
8. Build and push the application's Docker image to your Container Registry. Specify the appropriate region and give the container a name.

ibmcloud cr build -t <region>.icr.io/<namespace>/<container_name> .

You can view the image in container registry by using

ibmcloud cr images

You get something like the following response

REPOSITORY TAG DIGEST NAMESPACE CREATED SIZE SECURITY STATUS
<region>.icr.io/mynamespace/container_name latest 81c3959ea657 mynamespace 4 hours ago 28 MB No Issues
9. Update the Kubernetes deployment configuration file clouddb-deployment.yaml.

Change the image name to the repository name that you got from the previous step:

image: "<region>.icr.io/mynamespace/<container_name>" Edit me

Now, under secretKeyRef, change the name of <db-secret-name> to match the name of the secret that was created when you bound your database deployment to your Kubernetes cluster.

secretKeyRef:
name: <db-secret-name> Edit me
If you haven't already, clone the app in one of the available languages to your local environment from your console by using the following command

git clone -b <language> git@github.com:IBM-Cloud/clouddatabases-helloworld-kubernetes-examples.git
7. cd into this newly created directory, and cd into the database folder. The code for connecting to the service, and reading from and updating the database can be found in server.js. See [Code Structure](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-tutorial-k8s-appcode-structures) and the code comments for information on the app's functions. A public directory contains the html, stylesheets, and JavaScript for the web app. However, to get the application to work, we first need to push the Docker image of this application to our Container Registry.
8. Build and push the application's Docker image to your Container Registry. Specify the appropriate region and give the container a name.

ibmcloud cr build -t <region>.icr.io/<namespace>/<container_name> .

You can view the image in container registry by using

ibmcloud cr images

You get something like the following response

REPOSITORY TAG DIGEST NAMESPACE CREATED SIZE SECURITY STATUS
<region>.icr.io/mynamespace/container_name latest 81c3959ea657 mynamespace 4 hours ago 28 MB No Issues
9. Update the Kubernetes deployment configuration file clouddb-deployment.yaml.

Change the image name to the repository name that you got from the previous step:

image: "<region>.icr.io/mynamespace/<container_name>" Edit me

Now, under secretKeyRef, change the name of <db-secret-name> to match the name of the secret that was created when you bound your database deployment to your Kubernetes cluster.

secretKeyRef:
name: <db-secret-name> Edit me
If you haven't already, clone the app in one of the available languages to your local environment from your console by using the following command

git clone -b <language> git@github.com:IBM-Cloud/clouddatabases-helloworld-kubernetes-examples.git
7. cd into this newly created directory, and cd into the database folder. The code for connecting to the service, and reading from and updating the database can be found in server.js. See [Code Structure](https://cloud.ibm.com/docs/databases-for-etcd?topic=databases-for-etcd-tutorial-k8s-appcode-structures) and the code comments for information on the app's functions. A public directory contains the html, stylesheets, and JavaScript for the web app. However, to get the application to work, we first need to push the Docker image of this application to our Container Registry.
8. Build and push the application's Docker image to your Container Registry. Specify the appropriate region and give the container a name.

ibmcloud cr build -t <region>.icr.io/<namespace>/<container_name> .

You can view the image in container registry by using

ibmcloud cr images

You get something like the following response

REPOSITORY TAG DIGEST NAMESPACE CREATED SIZE SECURITY STATUS
<region>.icr.io/mynamespace/container_name latest 81c3959ea657 mynamespace 4 hours ago 28 MB No Issues
9. Update the Kubernetes deployment configuration file clouddb-deployment.yaml.

Change the image name to the repository name that you got from the previous step:

image: "<region>.icr.io/mynamespace/<container_name>" Edit me

Now, under secretKeyRef, change the name of <db-secret-name> to match the name of the secret that was created when you bound your database deployment to your Kubernetes cluster.

secretKeyRef:
name: <db-secret-name> Edit me
If you haven't already, clone the app in one of the available languages to your local environment from your console by using the following command

git clone -b <language> git@github.com:IBM-Cloud/clouddatabases-helloworld-kubernetes-examples.git
7. cd into this newly created directory, and cd into the database folder. The code for connecting to the service, and reading from and updating the database can be found in server.js. See [Code Structure](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=cloud-databases-tutorial-k8s-appcode-structures) and the code comments for information on the app's functions. A public directory contains the html, stylesheets, and JavaScript for the web app. However, to get the application to work, we first need to push the Docker image of this application to our Container Registry.
8. Build and push the application's Docker image to your Container Registry. Specify the appropriate region and give the container a name.

ibmcloud cr build -t <region>.icr.io/<namespace>/<container_name> .

You can view the image in container registry by using

ibmcloud cr images

You get something like the following response

REPOSITORY TAG DIGEST NAMESPACE CREATED SIZE SECURITY STATUS
<region>.icr.io/mynamespace/container_name latest 81c3959ea657 mynamespace 4 hours ago 28 MB No Issues
9. Update the Kubernetes deployment configuration file clouddb-deployment.yaml.

Change the image name to the repository name that you got from the previous step:

image: "<region>.icr.io/mynamespace/<container_name>" Edit me

Now, under secretKeyRef, change the name of <db-secret-name> to match the name of the secret that was created when you bound your database deployment to your Kubernetes cluster.

secretKeyRef:
name: <db-secret-name> Edit me
If you haven't already, clone the app in one of the available languages to your local environment from your console by using the following command

git clone -b <language> git@github.com:IBM-Cloud/clouddatabases-helloworld-kubernetes-examples.git
7. cd into this newly created directory, and cd into the database folder. The code for connecting to the service, and reading from and updating the database can be found in server.js. See [Code Structure](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-tutorial-k8s-appcode-structures) and the code comments for information on the app's functions. A public directory contains the html, stylesheets, and JavaScript for the web app. However, to get the application to work, we first need to push the Docker image of this application to our Container Registry.
8. Build and push the application's Docker image to your Container Registry. Specify the appropriate region and give the container a name.

ibmcloud cr build -t <region>.icr.io/<namespace>/<container_name> .

You can view the image in container registry by using

ibmcloud cr images

You get something like the following response

REPOSITORY TAG DIGEST NAMESPACE CREATED SIZE SECURITY STATUS
<region>.icr.io/mynamespace/container_name latest 81c3959ea657 mynamespace 4 hours ago 28 MB No Issues
9. Update the Kubernetes deployment configuration file clouddb-deployment.yaml.

Change the image name to the repository name that you got from the previous step:

image: "<region>.icr.io/mynamespace/<container_name>" Edit me

Now, under secretKeyRef, change the name of <db-secret-name> to match the name of the secret that was created when you bound your database deployment to your Kubernetes cluster.

secretKeyRef:
name: <db-secret-name> Edit me
If you haven't already, clone the app in one of the available languages to your local environment from your console by using the following command

git clone -b <language> git@github.com:IBM-Cloud/clouddatabases-helloworld-kubernetes-examples.git
7. cd into this newly created directory, and cd into the database folder. The code for connecting to the service, and reading from and updating the database can be found in server.js. See [Code Structure](https://cloud.ibm.com/docs/databases-for-redis?topic=databases-for-redis-tutorial-k8s-appcode-structures) and the code comments for information on the app's functions. A public directory contains the html, stylesheets, and JavaScript for the web app. However, to get the application to work, we first need to push the Docker image of this application to our Container Registry.
8. Build and push the application's Docker image to your Container Registry. Specify the appropriate region and give the container a name.

ibmcloud cr build -t <region>.icr.io/<namespace>/<container_name> .

You can view the image in container registry by using

ibmcloud cr images

You get something like the following response

REPOSITORY TAG DIGEST NAMESPACE CREATED SIZE SECURITY STATUS
<region>.icr.io/mynamespace/container_name latest 81c3959ea657 mynamespace 4 hours ago 28 MB No Issues
9. Update the Kubernetes deployment configuration file clouddb-deployment.yaml.

Change the image name to the repository name that you got from the previous step:

image: "<region>.icr.io/mynamespace/<container_name>" Edit me

Now, under secretKeyRef, change the name of <db-secret-name> to match the name of the secret that was created when you bound your database deployment to your Kubernetes cluster.

secretKeyRef:
name: <db-secret-name> Edit me
You can choose from the following set of virtual machine profiles:



* CX2-16x32 to CX2-128x256
* BX2-16x64 to BX2-128x512
* MX2-16x128 to MX2-128x1024



Depending on the memory required per core, you might pick the MX2 configuration, which can support up to 1 TB on the MX2-128x1024 profile.

If the memory required per core is less than 2 GB, an appropriate CX2 profile might give you the best price and performance. The advantages of faster communication over shared memory help with the performance if the workload can run on a single virtual machine.

Some examples of such workloads:



* Local area weather forecasting, not high resolution, large models but modest in size
* OpenFOAM computational fluid dynamics, size of the problem between 2 million - 10 million grid cells
* Design rule checking (DRC) in Electronic Design Automation (EDA) as part of chip designs
* EDA single component simulation and verification jobs







 Scale out use case with multiple virtual machines 

This is the second category of workloads where the requirement is to have multiple virtual machines for execution. Even for this category, depending on the network bandwidth and latency requirements, a significant set of HPC workloads would scale well on IBM Cloud.

There are cases where small updates might be needed to the application code to adjust it well to run in a cloud-like environment, and these changes are not specific to IBM Cloud but would be desirable to burst to any cloud provider.

IBM carries deep HPC expertise and can provide specific recommendations to get you the best price and performance for an HPC cloud environment.

IBM Cloud has been successful in the following examples:



* Optical Proximity Correction (OPC) in EDA
* Full chip Integrated Circuit Validator (ICV) in EDA
* Any Hadoop map/reduce or Spark workload
* MPI workloads that cannot fit on a single virtual machine



The recommendation for such workloads is to start with BX2-16x64 as it gives the best performance in tests so far. Based on your results, you might get insight into alternative options that might better suit your specific workload.
: As of 13 December 2021, alerts are deprecated in favor of [Event Notifications](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-event-notifications). The ability to create alerts within the Security and Compliance Center is no longer supported. You can continue to view, enable, disable, or delete your existing alerts until 15 March 2021. After this date, any existing alerts will be deleted, and the feature will be removed from the UI.

To enable the new notifications capability, you can go to the Global settings > Event Notifications section of the Security and Compliance Center UI. For more information, see [Enabling event notifications](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-event-notifications).





 9 December 2021 

Customer-managed collectors can now be installed on a cluster
: You can now install your customer-managed collector on to an IBM Cloud Kubernetes Service or OpenShift cluster.

New service available in Configuration Governance
: IBM Cloud Container Registry is now available as part of the Configuration Governance component. You can create guardrails for Container Registry such as restricting an account so that it can push and pull images only over private connections.





 22 November 2021 

New goals
: You might notice that your compliance score changed even though you didn't update any of your configurations. New goals were added to the Security and Compliance Center profiles that your resources are automatically scanned for. For detailed descriptions of the new goals, you can review the IBM Best Practices Controls 1.0 profile. All the goals with ID's in the following ranges are new.



* Goal ID's: 3000542 - 3000544 and 3000321.







 1 November 2021 

Scan your OpenShift clusters
: The ability to scan your OpenShift clusters is now available through the OpenShift Compliance Operator(OSCO) integration





 27 October 2021 

Deprecation of the bookmarks capability
: The ability to create bookmarks or direct connections within the Security and Compliance Center will be deprecated on 30 November 2021, when the feature will be removed from the UI.
You can take advantage of the IAM wildcarding facility to set policies for groups of resources on Event Streams. For example, if you give all your topics names like Dept1_Topic1 and Dept1_Topic2, you can set policies for topics that are called Dept1_* and these policies are applied to all topics with that prefix. For more information, see [Assigning access by using wildcard policies](https://cloud.ibm.com/docs/account?topic=account-wildcard).





 Connecting to Event Streams 

For more information about how to get a security key credential for an external application, see [Connecting to Event Streams](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-connecting).





 Managing access to the schema registry 

The authorization model for the schema registry used the same style of policies that are described in the [Managing Access To Event Streams Resources](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-securitysecurity) section of this document.



 IAM resources 

With the new schema IAM resource type, it is possible to create policies that control access by using varying degrees of granularity, as in the following examples.



* A specific schema.
* A set of schemas selected by a wildcard expression.
* All of the schemas stored by an instance of IBM Event Streams.
* All of the schemas stored by all of the instances of IBM Event Streams in an account.



Event Streams already has the concept of a cluster resource type. It is used to control all access to the service instance, with the minimum role of Reader being required to access any Kafka or HTTPS endpoint. This use of the cluster resource type is also applied to the schema registry whereby a minimum role of Reader is required to access the registry.





 Example authorization scenarios 

The following table describes some examples of scenarios for interacting with the Event Streams schema registry, together with the roles that are required by the actors involved. The process of managing schemas is handled separately to deploying applications.
To check on the status of your deployments, make sure to refer to your Kubernetes dashboard. If the box on a node does not turn green, or turns gray at some point, you can check on its status by making sure you’re in the correct resource group and clicking on your deployments. The Kubernetes dashboard is also how you will extend resources in your cluster, as needed. When the CA is ready, you’ll see the gray box turn green, indicating that the CA has been deployed.

But before we can use the CA to register identities for org 1, we need to enroll an admin for this CA. Which we can do by clicking on the CA and clicking on associate identity. From there, enter the enroll ID and secret you used when creating the CA: admin and adminpw. Then give this identity the name Org1 CA Admin. Then click associate identity. If you click over to your wallet, you can see that the CA Admin is there, indicating it has been enrolled successfully. The CA is now ready to be used to register and enroll identities.

We’ll start by registering the admin of org1. Because it will be an admin, use an enroll ID of org1admin and a secret of org1adminpw. Then give it a type of admin. Do not use the peer or orderer type. Use the default affiliation for now, and ignore the enrollments and attributes. If you want to learn about affiliations and enrollments and attributes you can read about them in our documentation. Now that the admin identity of org1 has been registered we need to register the identity for the peer itself. Remember that nodes have identities just as admins and users do. So we'll use peer1 and peer1pw as the enroll id and secret of the peer. This is a peer so we need to use the “peer” type, again using default affiliations and ignoring enrollments and attributes.

So now that we have registered the two identities we can create the definition of org1, which is represented by an MSP. We do that through the Organizations tab. Click create.