vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Tekton](https://www.ibm.com/cloud/blog/tekton-a-modern-approach-to-continuous-delivery) is an open source, vendor-neutral, Kubernetes-native framework that you can use to build, test, and deploy apps. Tekton provides a set of shared components for implementing [continuous delivery](https://www.ibm.com/garage/method/practices/deliver/practice_continuous_delivery/) systems. As an open source project, Tekton is managed by the [Continuous Delivery Foundation](https://cd.foundation/). The goal is to modernize continuous delivery by providing industry specifications for pipelines, workflows, and other building blocks. With Tekton, you can build, test, and deploy across cloud providers or on-premises systems by abstracting the underlying implementation details. Tekton pipelines are built into [Continuous Delivery](https://www.ibm.com/cloud/blog/announcements/build-and-deliver-using-tekton-enabled-pipelines). For more information about the IBM Cloud® Kubernetes Service, see [IBM Cloud® Kubernetes Service](https://www.ibm.com/garage/method/practices/run/tool_ibm_container).

The template that is used in this tutorial works with the Standard plan for Red Hat OpenShift.



 Before you begin 

Before you start this tutorial, make sure that you have the following resources in place:



* An [IBM Cloud account](https://cloud.ibm.com/registration). Depending on your IBM Cloud account type, access to certain resources might be limited. Depending on your account plan limits, certain capabilities that are required by some of the deployment strategies might not be available. For more information about IBM Cloud accounts, see [Setting up your IBM Cloud account](https://cloud.ibm.com/docs/account?topic=account-account-getting-started) and [Upgrading your account](https://cloud.ibm.com/docs/account?topic=account-upgrading-account).
31 August 2022 

Choose from dark or light themes in the console
: Enjoy a customized experience in the console that matches your preferences. By default, the console uses the mode that you already have set for your device. We'd like you to be able to experience IBM Cloud using a theme of your choosing. Use the Avatar icon from the console menu bar to find the options for changing your theme.







 July 2022 



 21 July 2022 

Monitoring context-based restrictions
: To help you predict how context-based restrictions might affect users, applications, and workflows, IBM Cloud is excited to release report-only mode for rules. You can enable context-based restrictions during creation, or choose to set the rule to report-only mode. Using Activity Tracker, you can monitor the impact of enabled rules, or view report-only rules to see how they will affect your users, applications, and workflows without enforcing the rule. For more information, see [Monitoring context-based restrictions](https://cloud.ibm.com/docs/account?topic=account-cbr-monitor).





 08 July 2022 

Streamlined process for updating published support information in Partner Center
: You can update support information for your published products by editing your already approved support information and then requesting an approval. After your changes are approved, you can publish the updates. For more information, see [Updating your product's support information](https://cloud.ibm.com/docs/sell?topic=sell-saas-support-detailsservice-support-include-update-support-details).







 June 2022 



 23 June 2022 

Onboarding software to sell on IBM Cloud by using the API
: To sell your products on IBM Cloud, you can now onboard and publish by using the Partner Center Sell API, in addition to using the Partner Center experience in the console. For more information, see [Partner Center Sell API](https://cloud.ibm.com/apidocs/partner-center-sell).





 22 June 2022 

Identify inactive identities
* Health data, extra conditions apply to be covered in the [IBM Cloudant Dedicated Cluster Service Description](https://www-03.ibm.com/software/sla/sladb.nsf/pdf/6756-04/$file/i126-6756-04_05-2018_en_US.pdf) and [IBM Cloud® Additional Service Description](https://www-03.ibm.com/software/sla/sladb.nsf/sla/saas?OpenDocument).



If you're storing healthcare data, you must complete the following tasks:



* Notify IBM Cloudant before you write any data.
* Request a HIPAA-compliant Dedicated Cluster.



For more information about supported classifications of Personal Data, see the [Data Sheet Addendum (DSA) under 2. Personal Data](https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=2EBB5860B34311E7A9EB066095601ABB).





 Data about me 

IBM Cloudant records some data about its users, and is a Data Controller for said Personal Information (PI) data. The data that IBM Cloudant records depends on the type of account you have.

If you have an IBM Cloudant Dedicated Cluster or IBM Cloudant Enterprise Cluster, IBM Cloudant records data about you and are considered a Data Controller for your data within the context of GDPR. If you have an IBM Cloudant Dedicated Cluster or IBM Cloudant Enterprise Cluster, IBM Cloudant stores the following information about you:



* Name
* Email



The data that IBM Cloudant holds can be viewed and updated through the IBM Cloudant Dashboard.

If you have an account that is provisioned by IBM Cloud (including a dedicated instance), IBM Cloudant does not collect the personal data that was discussed earlier. This data is held by IBM Cloud.

Do not use sensitive data for IBM Cloudant instance names when you provision by using IBM Cloud, such as: Personal Information (PI), Personal Identifying Information (PII), and Customer-specific Data.
* UI
* CLI
* Terraform







 Provisioning IBM Cloud Backup for Classic 

Backups ensure that your data is safely stored outside of your device and stays protected. IBM Cloud® Backup for Classic is an automated agent-based backup system that is managed through the Cloud Backup Portal browser-based management utility. You can provision your IBM Cloud® Backup for Classic instance in the UI, from the CLI, with the API, or Terraform.

Each server must have its own IBM Cloud Backup for Classic Account. One IBM Cloud Backup for Classic license cannot be used for multiple servers.



 Provisioning IBM Cloud Backup for Classic in the UI 

You can provision IBM Cloud Backup for Classic service in two ways in the console.



* [Provision backup space when you order a server](https://cloud.ibm.com/docs/Backup?topic=Backup-orderingpurchasingwithserver).
* [Provision backup space as an upgrade](https://cloud.ibm.com/docs/Backup?topic=Backup-orderingpurchasingasupgrade).





 Purchasing IBM Cloud Backup for Classic when you order a server 



1. Log in to the [IBM Cloud catalog](https://cloud.ibm.com/catalog).
2. Order a monthly Bare Metal Server. For more information about ordering bare metal servers, see [Building a custom Bare Metal Server](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-ordering-baremetal-server).



1. Select quantity, billing option. Enter host and domain names. You can choose any hostname and domain that you like.

IBM Cloud Backup for Classic service isn't available when you're ordering an hourly billed server. However, the service can be added later as an upgrade.
2. Select location.
3. Select Server configuration and OS Image type. You can also choose multiple add-ons.
4. Under the Storage Disks section, click Add-ons, and select IBM Cloud Backup for Classic. Choose the option that matches what you need.
5.
IBM Cloud is built by following many data, finance, health, insurance, privacy, security, technology, and other international compliance standards. For more information, see [IBM Cloud compliance](https://cloud.ibm.com/docs/overview?topic=overview-compliance).

To view detailed system requirements, you can run a [software product compatibility report for Red Hat OpenShift on IBM Cloud](https://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html). Note that compliance depends on the underlying [infrastructure provider](https://cloud.ibm.com/docs/openshift?topic=openshift-infrastructure_providers) for the cluster worker nodes, networking, and storage resources.

Classic infrastructure: Red Hat OpenShift on IBM Cloud implements controls commensurate with the following security standards:



* EU-US Privacy Shield and Swiss-US Privacy Shield Framework
* Health Insurance Portability and Accountability Act (HIPAA)
* Service Organization Control standards (SOC 1 Type 2, SOC 2 Type 2)
* International Standard on Assurance Engagements 3402 (ISAE 3402), Assurance Reports on Controls at a Service Organization
* International Organization for Standardization (ISO 27001, ISO 27017, ISO 27018)
* Payment Card Industry Data Security Standard (PCI DSS)



VPC infrastructure: Red Hat OpenShift on IBM Cloud implements controls commensurate with the following security standards:



* EU-US Privacy Shield and Swiss-US Privacy Shield Framework
* Health Insurance Portability and Accountability Act (HIPAA)
* International Standard on Assurance Engagements 3402 (ISAE 3402), Assurance Reports on Controls at a Service Organization



Satellite: See the [IBM Cloud Satellite documentation](https://cloud.ibm.com/docs/satellite?topic=satellite-faqsstandards).





 Can I use IBM Cloud and other services with my cluster? 

You can add IBM Cloud platform and infrastructure services as well as services from third-party vendors to your Red Hat OpenShift on IBM Cloud cluster to enable automation, improve security, or enhance your monitoring and logging capabilities in the cluster.
Transitioning to updated plans 

In 2023, the original IBM Cloud® Internet Services plans are being updated to reflect new plans and associated features.

Migrating from one plan to another is considered a modification of an existing resource, and not a destruction or creation of a resource.



 Transitioning from a Standard plan to a Standard Next plan 

Starting 30 April 2023, the CIS current Standard plan will no longer be available for new instances. Any instance that is created on or after this date will use the Standard Next plan.

By moving to a more metered model, the base cost of the Standard Next plan is smaller than the original Standard plans. The following table shows what changed from the Standard to the Standard Next plans.



Table 1. Comparison of CIS Standard and Standard Next plans

 Feature Standard Standard Next Overage 

 Domain 1 1 Each additional domain incurs a fee 
 Protected traffic <br>(TB) 5 0.5 Traffic over the limit (per TB) incurs a fee 
 Range traffic No No Not applicable 
 DNS queries <br>(million per domain) 10 1 Fees assessed per additional million queries 
 HTTP requests <br>(million) 10 5 Fees assessed per additional million requests 
 Edge function requests <br>(million) 1 1 Fees assessed per additional million queries 
 DDoS protection Yes Yes Not applicable 
 WAF <br>(million) Not applicable Yes Part of HTTP requests 
 IP Firewall Yes Yes Not applicable 
 DNS records per domain 3500 250 Upgrade plan to get more 
 GLB origin servers 6 3 Not applicable 
 Smart routing No No Not applicable 
 Rate limiting No No Not applicable 
 Logpush/Logpull No No Not applicable 
 Page rules per domain 50 50 Not applicable 
 Firewall rules 100 100 Not applicable 





 Migration to Standard Next plans 

To migrate from your current Standard plan to a Standard Next plan, take the following steps.



1. Enter your existing CIS instance
2. Navigate to the Plan page in left side panel
3. Select Standard Next plan
4. Check the box to acknowledge the terms and conditions
5. Click Create and follow any prompts that might block this plan change









 Transitioning to Enterprise Tier plans
[solution tutorial icon](https://cloud.ibm.com/media/docs/images/homepage/solution-tutorial.svg) [VPC landing zone - Standard variation](https://cloud.ibm.com/docs/deployable-reference-architectures?topic=deployable-reference-architectures-vpc-ra)VPC landing zone - Standard variation Reference architecture

The Standard variation of the VPC landing zone deployable architecture uses two Virtual Private Clouds (VPC), a Management VPC, and a Workload VPC to manage the environment and the deployed workload. Each VPC is a multi-zoned, multi-subnet implementation that keeps your workloads secure. A transit gateway connects the VPCs to each other and Virtual Private Endpoints are used connect to IBM Cloud services.

Deployable![ref architecture icon](https://cloud.ibm.com/media/docs/images/homepage/reference-architecture.svg) [VPN into a secure private network](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-configuring-IPSEC-VPN)VPN into a secure private network Solution tutorial

The need to create a private connection between a remote network environment and servers on the private network of the IBM Cloud is a common requirement. Most typically this connectivity supports hybrid workloads, data transfers, private workloads or administration of systems on the IBM Cloud. A site-to-site Virtual Private Network (VPN) tunnel is the usual approach to securing connectivity between networks.

![solution tutorial icon](https://cloud.ibm.com/media/docs/images/homepage/solution-tutorial.svg) [VSI on VPC landing zone - QuickStart variation](https://cloud.ibm.com/docs/deployable-reference-architectures?topic=deployable-reference-architectures-vsi-ra-qs)VSI on VPC landing zone - QuickStart variation Reference architecture
Queue manager sizes 

Learn about the characteristics of IBM queue managers available to deploy on IBM Cloud.



 Lite queue managers 

To give you a taste of MQ as a managed service, the IBM MQ on Cloud service offers a Lite queue manager. If you do not currently have a Lite queue manager deployed, you can create one by following the [creating a queue manager](https://cloud.ibm.com/docs/services/mqcloud?topic=mqcloud-mqoc_create_qm) guide.

Note:



* You can deploy up to two Lite queue managers per Lite service instance
* You can delete an existing Lite queue manager and deploy a new one at any time
* Lite queue managers will automatically be deleted after 30 days of inactivity but you are welcome to deploy a new one
* A Lite queue manager is considered active if you have sent a message (using a non-SYSTEM queue), or have logged in to the service instance via the IBM Cloud user interface
* You will never be charged for a Lite queue manager
* Whilst all billable queue managers have regular backups taken, please note that backups of Lite queue managers are not taken and therefore user configuration is non-recoverable







 Billable queue managers 

The IBM MQ on Cloud service offers the following billable queue manager sizes:



* Extra Small: Appropriate for very light or occasional workloads with modest throughput requirements
* Small: Appropriate for light workloads such as supporting an individual department or application
* Medium: Appropriate for shared use by a number of light to moderate workload applications
* Large: Appropriate for heavy throughput scenarios where transaction performance is critical



A billable queue manager is charged based on the number of Virtual Processor Core (VPC) hours that it is active - for example, a Large size queue manager is charged at four times (4x) the rate of a Small size queue manager. The hourly cost is dependent on your local currency and can be seen in the Pricing Plan at the bottom of the [MQ service catalog page](https://cloud.ibm.com/catalog/services/mq), where you can select your country or region.
Customizing an IBM Cloud deployable architecture 

You can take advantage of a IBM®-curated customization bundle to extend and customize an IBM Cloud®

deployable architecture. Each deployable architecture provides its own customization bundle. With the bundle, you can edit the deployable architecture on your local computer, use your own pipelines to test, and extend your own products to fit your enterprise's needs. To customize an architecture, you must have familiarity with Terraform.

The customization bundle also includes an automation directory that includes starter scripts to help you manage the lifecycle of your customized deployable architecture from onboarding and validation to publishing it to a private catalog on IBM Cloud. Currently, two pipeline methods are included in this directory: GitHub actions or a Toolchain from IBM Cloud.

The following guidance provides an overview of the customization bundle and some examples of customization that you can do. It is not all inclusive and you can make any changes that you need. After you modify the architecture, you can add it to a private catalog and use IBM's tools to check for vulnerabilities, ensure security and compliance, and share the architecture with your enterprise.

Depending on your level of customization, IBM Cloud might not support the deployable architecture. The components of the architecture that are supplied in the customization bundle are supported by IBM Cloud, but any customized code that's used to extend is not.



 Before you begin 



1. Create a repository to store the customized deployable architecture, for example, a GitHub repository. For more information, see [Creating a new repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-new-repository).
2. Make sure that you have an editor of your choice to modify the deployable architecture, for example, Visual Studio Code. For more information, see [Visual Studio Code](https://code.visualstudio.com/).
3. Make sure that you have tools of your choice to test your deployable architecture and ensure that it works. For example, you can use Terraform runtime, which supplies the Terraform command line.
Services For Bare Metal Servers, there are fixed plans to choose from, and those plans are charged at a fixed monthly rate. 
 Metered Usage is a unit-based pricing model in which you pay for what you consume. In this case, the number of GB hours that are consumed for runtimes and the number of IP addresses and storage that is consumed for containers. Services, Compute, and Containers For Push Notifications, any usage that is consumed over the free monthly allowance of 100,000 digital messages per month, will be charged. 
 Tiered In this pricing model, you get a volumed-based discount according to your actual usage. Tiered pricing is typically used for charge metrics that are expected to have high quantities per month, such as API calls. Services might offer simple, graduated, or block tier pricing plans. Services For API Connect, one of the tiered plans charges $10,000 for the first 25 million monthly API calls and $40.00 USD per 100,000 API calls per month thereafter. 
 Reserved Reserved pricing is based on a long-term commitment for a service, so you can get a discounted price. With a reserved plan, you get a dedicated service instance that is easy to set up, deploy, and deliver in the public IBM Cloud environment. Services Db2 on Cloud has reserved plans. 





 Understanding monthly and hourly tags 

On the usage dashboard, your products and resources can be labeled with Monthly, Hourly, or a combination of both tags to signify how often charges are updated.

The Monthly tag signifies that resources within your account have a fixed cost. These charge show up immediately after purchase and are prorated in proportion to how many days are left in the month. Any recurring monthly fixed costs are then shown at the first of every month.

The Hourly tag signifies that resources within your account have variable costs. These resources are updated daily.





 Lite plans 

Lite plans are structured as a free quota. You can work on your projects worry free, without the risk of generating an accidental bill. The quota might operate for a specific time period, for example a month, or on a one-off usage basis. The following list provides some examples of Lite plan quotas:



* Maximum number of registered devices
* Maximum number of application bindings
* The IBM Cloud web user interfaces rely on cascading style sheets to render content properly and to provide a usable experience. The application provides an equivalent way for low-vision users to use a user’s system display settings, including high-contrast mode. You can control font size by using the device or web browser settings.
* The IBM Cloud web user interface includes WAI-ARIA navigational landmarks that you can use to quickly navigate to functional areas in the application.







 Related accessibility information 

The IBM Cloud web user interface accessibility compliance status is specifically for the IBM Cloud product platform. There are subsections of the user interface that are owned by third-party products or services that host content within the platform, for which the IBM Cloud compliance record does not maintain or own the accessibility compliance status. If you are accessing any user interface or documentation for a service, you must request the compliance statements for that service. For example, if you are using an interface for IBM Cloud Kubernetes Service, the administration console for a local or dedicated environment, or an IoT service, you must request [product accessibility information](https://www.ibm.com/able/product_accessibility/) for that interface or documentation.

The IBM Cloud documentation accessibility compliance is specifically for the IBM Cloud core platform information, and it does not extend to any services. The available documentation for IBM Cloud is managed and reported in the IBM Cloud product accessibility information that is available upon request. For compliance status for any service, you must request [product accessibility information](https://www.ibm.com/able/product_accessibility/).

In addition to standard IBM help desk and support websites, IBM has established a TTY telephone service for use by deaf or hard of hearing customers to access sales and support services:

TTY service 800-IBM-3383 (800-426-3383) (within North America)





 IBM and accessibility 

For more information about the commitment that IBM has to accessibility, see [IBM Accessibility](http://www.ibm.com/able).
For more information, see the [IAM guide](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-managing-access-for-cloudant) or the legacy [Authentication API document](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-work-with-your-accountauthentication). 
 Authorization IBM Cloudant supports both legacy and IAM access controls. The IBM Cloudant team recommends that you use IAM access controls for authentication whenever possible. If you're using IBM Cloudant legacy authentication, IBM Cloudant team recommends that you use [API keys](https://cloud.ibm.com/apidocs/cloudantintroduction) rather than account-level credentials for programmatic access and replication jobs. For more information, see the [IAM guide](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-managing-access-for-cloudant) or the legacy [Authentication document](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-work-with-your-accountauthentication) and the legacy [Authorization document](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-work-with-your-accountauthorization). 
 At-rest encryption All data that is stored in an IBM Cloudant instance is encrypted at rest by using LUKS1 with 256-bit Advanced Encryption Standard (AES-256). By default, IBM Cloudant manages the encryption keys for all environments. If you require bring-your-own-key (BYOK) encryption for encryption-at-rest, BYOK is enabled by using your encryption key that is stored in an IBM Cloud Key Protect instance. IBM Cloudant supports the BYOK feature for new IBM Cloudant Dedicated Hardware plan instances that are deployed in all regions.