vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Collecting availability metrics by using the Prometheus Blackbox exporter](https://cloud.ibm.com/docs/monitoring?topic=monitoring-blackbox)Collecting availability metrics by using the Prometheus Blackbox exporter

The Prometheus Blackbox exporter allows blackbox probing of endpoints over HTTP, HTTPS, DNS, TCP and ICMP. The monitoring agent can be used in conjunction with the Blackbox exporter to collect availability metrics. The availability metrics can then be alerted upon within IBM Cloud Monitoring to alert users on the availability of the endpoints.

Monitoring



* 1 hour
* 2021-03-28



[Collecting IPMI device sensor metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-ipmi)Collecting IPMI device sensor metrics

In addition to the set of metrics that are automatically collected by the monitoring agent, you might want to collect other metrics such as sensor metrics. You can use the Prometheus IPMI Exporter to perform the collection of Intelligent Platform Management Interface (IPMI) device sensor metrics.

Monitoring



* 1 hour
* 2022-01-20



Networking[Accelerate a dynamic website using Dynamic Content Acceleration](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-dynamic-content-cdn)Accelerate a dynamic website using Dynamic Content Acceleration

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

Content Delivery Network (CDN) Kubernetes service

+2

Container Registry,Domain Name Registration



* 2 hours
* 2023-06-14



[Accelerate delivery of static files using a CDN](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-static-files-cdn)Accelerate delivery of static files using a CDN
* For Topic, select the topic you created. For example, MonitorSecretExpiry.
* For Destination, select IBM Cloud email service.
* For Recipients, enter a valid email address, for example, [MyEmail@MyCompany.com](mailto:MyEmail@MyCompany.com).



4. Click Create. Your subscription is added to the Subscriptions list.







 Step 8: Sending test event from Secrets Manager 

Send a test event as follows:



1. Click the menu icon > Resource list.
2. Open Services and software.
3. Open the Secrets Manager instance that you created.
4. Click Settings.
5. Click send test event.



You should start receiving notifications at the email address that you configured whenever the criteria defined in both Secrets Manager and Event Notifications match.
: The entitled registry path from which the service pulls images for the PostgreSQL datastore has changed. The registry location changed from cp.icr.io/cp/watson-speech to cp.icr.io/cp/cpd. This change is transparent to users.

Secrets for Minio and PostgreSQL datastores
: The Minio and PostgreSQL datastores require the following hard-coded values for their secrets:



* For Minio, use minio.
* For PostgreSQL, use user-provided-postgressql.



You cannot use your own values for these secrets. The secrets must be created before you install the Speech services.

Deletions from speech-override.yaml file
: The following entries have been removed from the speech-override.yaml file. They were added to work around a problem that has now been fixed.

sttRuntime:
images:
miniomc:
tag:
1.0.5
sttAMPatcher:
images:
miniomc:
tag:
1.0.5
ttsRuntime:
images:
miniomc:
tag:
1.0.5

The abbreviated speech-override.yaml file has generally been reduced further by fine-tuning its contents to the essential elements.





 Version 1.2 (9 December 2020) 

Version 1.2 is available
: Speech to Text for IBM Cloud Pak for Data version 1.2 is now available. Installation and administration of the service include many changes. This version supports IBM Cloud Pak for Data versions 3.5 and 3.0.1, and Red Hat OpenShift versions 4.5 and 3.11.

New Australian and French Canadian models
: The service now offers broadband and narrowband models for Australian English and Canadian French:



* Australian English: en-AU_BroadbandModel and en-AU_NarrowbandModel
* Canadian French: fr-CA_BroadbandModel and fr-CA_NarrowbandModel



The new models are generally available, and they support both language model and acoustic model customization.
* You have five public certificate secrets that expire in 10 days.
* You have 100 imported certificate secrets that expire in 30 days.



You can be notified of a maximum 100 secrets in a single event notification.





 Before you begin 

You need an IBM Cloud® account. If you don't have an account, then [Create an IBM Cloud account](https://cloud.ibm.com/registration/).





 Step 1: Create an Event Notifications service instance 



1. Log in to your [IBM Cloud®](https://cloud.ibm.com) account.
2. In the [IBM Cloud catalog](https://cloud.ibm.com/catalogservices), search Event Notifications > Event Notifications.
3. Select a Location from the list of supported locations and select a pricing plan.
4. Enter a service name.
5. Select a resource group.
6. Accept the license agreement terms and click Create.







 Step 2: Create an Secrets Manager service instance 



1. In the [IBM Cloud catalog](https://cloud.ibm.com/catalogservices), search Secrets Manager > Secrets Manager.
2. Select a Location from the list of supported locations and select a pricing plan.
3. Enter a service name.
4. Select a resource group.
5. Accept the license agreement terms and click Create.







 Step 3: Connecting to Event Notifications in the Secrets Manager user interface 



1. From the Secrets Manager instance, click Settings.
2. In the Event Notifications section, click Connect.
3. In the side panel, review the source details for the connection. Optionally, provide a description.
4. Select the resource group and Event Notifications service instance that you want to connect to.



If an IAM authorization between Secrets Manager and Event Notifications doesn't exist in your account, a dialog is displayed. Follow the prompts to grant access between the services:



1. To grant access, click Authorize.
2.
[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



[Getting started with Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-getting-started)Getting started with Security and Compliance Center

For highly regulated industries, such as financial services, achieving continuous compliance within a cloud environment is an important first step toward protecting customer and application data. Historically, that process was difficult and manual, which placed your organization at risk. But, with IBM Cloud® Security and Compliance Center, you can integrate daily, automatic compliance checks into your development lifecycle to help minimize that risk.

Security and Compliance Center Object Storage

+2

Event Notifications,



* 5 minutes
* 2023-07-11



[Onboarding a virtual server image with Terraform to a private catalog](https://cloud.ibm.com/docs/sell?topic=sell-vsimage-onboard)Onboarding a virtual server image with Terraform to a private catalog

This tutorial walks you through how to onboard a virtual server image with Terraform to a private catalog. By completing this tutorial, you learn how to import the virtual server image from a GitHub repository, configure the deployment and other details, and validate that you can deploy the image to a target IBM Cloud® Virtual Private Cloud (VPC).

Object Storage Virtual Private Cloud (VPC)

+1

Selling on IBM Cloud



* 45 minutes
* 2022-08-02



[Onboarding a virtual server image for Power Systems to a private catalog](https://cloud.ibm.com/docs/sell?topic=sell-vsipower-onboard)Onboarding a virtual server image for Power Systems to a private catalog
: Optional: The timeout value, in seconds, for the load balancer to receive the PROXY protocol headers that contain the client connection information. This option is supported only for ALBs that run the community Kubernetes Ingress image. Default: 5

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

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



 Example ingress lb proxy-protocol enable command 

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







 ibmcloud oc ingress secret create 

Virtual Private Cloud

Classic infrastructure

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

The previous alias for this command, ibmcloud oc ingress alb cert deploy, is deprecated. In CLI version 1.0.157 and later, the ibmcloud oc ingress alb cert category is deprecated, and these commands are now listed in the ibmcloud oc ingress secret subcategory. For more information, see the [CLI change log](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelog10).

To use the ibmcloud oc ingress secret create command, you must have a default [Secrets Manager](https://cloud.ibm.com/docs/openshift?topic=openshift-secrets-mgr) instance registered to your cluster. 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
Importing SSL certificates into IBM Cloud Secrets Manager 

You can apply a security protocol to provide communication privacy for your app to prevent eavesdropping, tampering, and message forgery. If you have a Lite account, you must upgrade your account to upload a certificate.

When an expired or expiring certificate must be renewed, and after the new certificate is ready, delete the existing certificate and then add the new one.



 Import your existing credentials into IBM Cloud Secrets Manager 

IBM Cloud Foundry uses customer owned IBM Cloud Secrets Manager to manage [SSL certificates.](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-certificates) permitting customers to have better control of their secrets. If you are using custom domains,IBM Cloud Secrets Manager will be used as storage for your SSL certificates and you will have control of certificates access via IAM service authorizations. We suggest you, to store your custom domains TLS certificates in a dedicated secrets group because will give increased flexibility when configuring [service to service authorization.](https://cloud.ibm.com/docs/account?topic=account-serviceauth)

Before configuring IBM Cloud Foundry to use IBM Cloud Secrets Manager, you need to [import your existing certificates into IBM Cloud Secrets Manager.](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-certificatesimport-certificates)





 Authorizing IBM Cloud Foundry to operate on imported certificates 

Before you can map your SSL certificate to a custom domain, you must authorize IBM Cloud Foundry to use certificates [in IBM Cloud Secrets Manager.](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-certificatesimport-certificates)



1. [Log in the IBM Cloud.](https://cloud.ibm.com/)
2. Click Manage > Access(IAM) > Authorizations.
3. Click Create.
4. For Source account select This account.
5. For Source service select Cloud Foundry for Custom Domain and leave How do you want to scope the access? as All resources.
6.
* There exist use cases in which the registry is not known when the workload section is pre-encrypted, for example, when the workload provider wants to allow the deployer to use a registry mirror or a private container registry. In such a case, it's possible to dynamically override the registry and the pull credentials - which is coordinated between the workload provider and the deployer. For more information, see [Using a dynamic registry reference](https://cloud.ibm.com/docs/vpc?topic=vpc-hyper-protect-virtual-server-use-dynamic-registry-reference).







 16 March 2023 

Client-to-site VPN server private certificate support
: VPN servers now support the use of Secrets Manager private certificates. Private certificates are SSL/TLS certificates that you can sign, issue, and manage in the Secrets Manager service. For VPN server considerations, see [Using a private certificate](https://cloud.ibm.com/docs/vpc?topic=vpc-client-to-site-authenticationusing-private-certificate). For Secrets Manager information, see [Creating a private certificate](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-certificates&interface=uicreate-certificates).





 10 March 2023 

Client-server timeout for application load balancers
: You can now configure the client and server timeout parameters for IBM Cloud Application Load Balancer for VPC by using the UI, CLI, and API. The maximum timeout period for each listener is 2 hours, and the minimum is 50 seconds. If you need a timeout amount greater than 2 hours, open a [support case](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-help) with IBM Support. For more information about setting the client and server timeout period, see [Creating an application load balancer](https://cloud.ibm.com/docs/vpc?topic=vpc-load-balancers&interface=ui). This functionality is only available for application load balancers.







 February 2023 



 14 February 2023
* An instance of the [Continuous Delivery](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-getting-started) service.
* Optional. A set of secrets that are stored in a secrets management vault and managed centrally from a single location. For more information about selecting a secrets management and data protection offering, see [Managing IBM Cloud secrets](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-manage-secrets-ibm-cloud). If you don't already have an instance of the secrets management vault provider of your choice, create one.





 Related content 



* [Getting started with Continuous Delivery](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-getting-started)
* [Getting started with clusters](https://cloud.ibm.com/docs/containers?topic=containers-getting-started)
* [Getting started with toolchains](https://cloud.ibm.com/devops/getting-started)









 Step 1: Create the toolchain 

In this step, you create a Develop and Deploy application to VPC using deployment strategies toolchain. The target virtual machines are configured during the toolchain setup by using your SSH keys. You can change these settings later by updating the Delivery Pipeline configuration. Any code that is merged into the target Git repo branch is automatically built, validated, and deployed into the virtual machines.

To create a Develop and Deploy application to VPC using deployment strategies toolchain, click

[!
ibmcloud resource service-instance-create test-sm-instance-tutorial secrets-manager lite us-south

The provisioning process for Secrets Manager takes 5 - 15 minutes to complete.
5. Export environment variables with the IDs of both service instances.

export COS_INSTANCE_ID=ibmcloud resource service-instance "test-cos-instance-tutorial" --output json | jq -r ".[].guid"; echo $COS_INSTANCE_ID

export SM_INSTANCE_ID=ibmcloud resource service-instance "test-sm-instance-tutorial" --output json | jq -r ".[].guid"; echo $SM_INSTANCE_ID
6. (Optional) Verify that your services were created successfully by clicking the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/icon_hamburger.svg)> Resource List in your IBM Cloud console.







 Set up access permissions 

Next, define the access hierarchy that you need to be able to run operations against the Secrets Manager and Cloud Object Storage services.



1. Create a test access group in your IBM Cloud account.

By creating an access group, you're able to assign access to the set of users and service IDs that require access to your Secrets Manager and Cloud Object Storage instances. From the command line, run the following command to create a new access group called test-cos-admin-group.

export ACCESS_GROUP_ID=ibmcloud iam access-group-create test-storage-admin-group -d "An access group for testing Secrets Manager and Cloud Object Storage." --output json | jq -r ".id"; echo $ACCESS_GROUP_ID
2. Set up your account credentials.

Create a service ID and set it as an environment variable.
For each app deployment that you want to expose, create a Kubernetes ClusterIP service. Your app must be exposed by a Kubernetes service to be included in the Ingress load balancing.



oc expose deploy <app_deployment_name> --name my-app-svc --port <app_port> -n <namespace>





 Step 2: Set up TLS termination with TLS certificates and Kubernetes secrets 

Your TLS certificate must be stored as a Kubernetes secret in each namespace where your apps exist.



 TLS secrets for custom domains 

To set up TLS secrets for a domain that you created yourself, such as a domain registered with an external provider, see [Setting up TLS secrets for custom subdomains](https://cloud.ibm.com/docs/openshift?topic=openshift-secretstls-custom). These steps apply for both classic and VPC clusters.





 TLS secrets for the IBM-managed domain 



Classic clusters

To use the IBM-managed Ingress domain in a classic cluster, see [Setting up TLS secrets for the IBM-provided Ingress subdomain](https://cloud.ibm.com/docs/containers?topic=containers-secretstls-default).
VPC clusters

To use the IBM-managed Ingress domain in a VPC cluster, follow these steps.





1. List the existing subdomains in your cluster. In the Subdomain column of the output, copy the subdomain that has the highest 000<n> value.

ibmcloud oc nlb-dns ls --cluster <cluster_name_or_id>

In this example output, the mycluster-a1b2cdef345678g9hi012j3kl4567890-0002.us-south.containers.appdomain.cloud subdomain has the highest 000<n> value of 0002.

Subdomain Load Balancer Hostname Health Monitor SSL Cert Status SSL Cert Secret Name
* UI
* CLI
* API
* Terraform







 Ordering SSL/TLS public certificates 

You can use IBM Cloud® Secrets Manager to store, request, and generate public SSL/TLS certificates that you can use for your apps or services.

An SSL/TLS certificate is a type of digital certificate that is used to establish communication privacy between a server and a client. Certificates are issued by

certificate authorities (CA)and contain information that is used to create trusted and secure connections between endpoints. After you add a certificate to your Secrets Manager instance, you can use it to secure network communications for your cloud or on-premises deployments. Your certificate is stored securely in your dedicated Secrets Manager service instance, where you can centrally manage its lifecycle.

In Secrets Manager, Certificates that you order through Secrets Manager from a third-party certificate authority are public certificates. Certificates that you import to the service are [imported certificates](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-certificates) (imported_cert). Certificates that you create by using a private certificate authority are [private certificates](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-private-certificates) (private_cert).



 Before you begin 

Before you get started, be sure that you have the required level of access. To create or add secrets, you need the [Writer service role or higher](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-iam).

Before you order a certificate, be sure that you:



* [Prepare your instance to order certificates](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-prepare-order-certificates).
* Review the certificate authority and DNS provider configurations that are available. To view the configurations that are defined for your instance, go to the Secrets engines > Public certificates page in the Secrets Manager UI.



To work with a DNS provider that is not currently integrated with the service, you do not need to add a configuration to order your public certificate.





 Ordering public certificates
* The name of the Portworx block storage class has changed from portworx-shared-gp3 to portworx-db-gp3-sc.
* The createSecret property has been removed for the MinIO and PostgreSQl datastores. The property is only used internally. The Speech services always use a secrets object if you create one, and they always automatically create the object if none is provided.



User-provided secrets object now supported for RabbitMQ datastore
: You can now provide security credentials for the RabbitMQ datastore, just as you can for the MinIO and PostgreSQL datastores. The documented process is similar for all three datastores.

New Italian it-IT_Multimedia next-generation model
: The service now offers a next-generation multimedia model for Italian: it-IT_Multimedia. The new model is generally available. It does not support low latency, but it does support language model customization and grammars. For more information about all available next-generation models, see [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng).

Updated Korean telephony and multimedia next-generation models
: The existing Korean next-generation models have been updated:



* The ko-KR_Telephony model has been updated for improved low-latency support for speech recognition.
* The ko-KR_Multimedia model has been updated for improved speech recognition. The model now also supports low latency.



Both models are generally available, and both support language model customization and grammars. You do not need to upgrade custom language models that are based on these models. For more information about all available next-generation models, see [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng).

Updates to multiple next-generation telephony models
: The following next-generation English language telephony models have been updated for improved speech recognition:



* en-AU_Telephony