vania-janet/multiturn-rag-retrieval-data huggingface dataset:
FAQs about selling software 

FAQs about selling third-party software on IBM Cloud® might include questions about the types of software you can add to the catalog, pricing plans, and updating and restoring software versions.

To find all FAQs for IBM Cloud, see our [FAQ library](https://cloud.ibm.com/docs/faqs).



 What types of software can I add to the IBM Cloud catalog? 

See the following list for the types of third-party software that you can currently add to the catalog:



* Helm charts on Kubernetes and Red Hat OpenShift on IBM Cloud clusters
* Terraform templates
* OVA images deployed on VMware Solutions Dedicated - vCenter Server
* Virtual server images with Terraform deployed on VPC infrastructure or Power Systems Virtual Server
* Operators with a TGZ file from GitHub or GitLab repositories
* Operator bundles from Red Hat OpenShift registries







 What account do I use to onboard my software? 

Use your IBM Cloud account to onboard software to the catalog. In some cases an IBM representative, with their own account, might be helping you with the onboarding process. If you want the representative to access your software in your test environment, you can add them to your account. For more details, see [Inviting users to an account](https://cloud.ibm.com/docs/account?topic=account-iamuserinv).





 What's the difference between onboarding an Operator from my repository and onboarding an Operator from Red Hat? 

One major difference is the packaging format. You can review the following example formats:



* Node-RED Operator: [https://github.com/IBM-Cloud/operator-bundle-sample/archive/refs/tags/v0.0.3.tar.gz](https://github.com/IBM-Cloud/operator-bundle-sample/archive/refs/tags/v0.0.3.tar.gz)
* Operator bundle from a Red Hat OpenShift on IBM Cloud registry: For an example, select the Akka Cluster Operator from the list of available Operators in the Certified repository.
[IBM Developer<br><br>Visit IBM Developer for technical articles, code patterns, tutorials, and more.<br><br>![112-Developer-tools.svg](https://cloud.ibm.com/media/docs/images/homepage/112-Developer-tools.svg)](https://developer.ibm.com/depmodels/cloud/)[Architecture Center<br><br>Discover the architecture references available for this product.<br><br>![190-Application-Platform.svg](https://cloud.ibm.com/media/docs/images/homepage/190-Application-Platform.svg)](https://www.ibm.com/cloud/architecture)[IBM Training<br><br>Build your skills with IBM Cloud training.<br><br>![83-Elements-of-the-cloud.svg](https://cloud.ibm.com/media/docs/images/homepage/83-Elements-of-the-cloud.svg)](https://www.ibm.com/training/cloud)[Community<br><br>Join the IBM Cloud community and collaborate with others.<br><br>![35-Connectivity.svg](https://cloud.ibm.com/media/docs/images/homepage/35-Connectivity.svg)](https://community.ibm.com/community/user/publiccloud/home)

 Latest updates 

[View more](https://cloud.ibm.com/docs/key-protect?topic=key-protect-releases)5 August 2021 | Updates to the Key Protect console and Key purge feature

The ability to purge keys that have been deleted after four hours using the UI has been added. Also, the ability to view your instance ID and cloud resource name (CRN) has been made easier.

30 June 2021 | Updates to the Key Protect CLI plugin

The IBM Cloud Key Protect CLI plugin has been updated to version 0.6.3. Minor changes include support for HPCS and Key rotate.
: A distributed cloud provides consistent security and services across environments, centralized workload visibility, reduced latency, easier compliance and higher application development velocity. See blog post announcement [here](https://www.ibm.com/cloud/blog/announcements/deploy-managed-cloud-native-databases-anywhere-with-ibm-cloud-satellite).





 21 July 2020 

IBM Cloud Messages for RabbitMQ 3.8 is Now Preferred
: RabbitMQ 3.8 Preferred status. See blog post announcement [here](https://www.ibm.com/cloud/blog/announcements/ibm-cloud-messages-for-rabbitmq-38-is-now-preferred).





 13 April 2020 

IBM Cloud® Messages for RabbitMQ autoscaling
: We are excited to announce that autoscaling of your deployments based on disk capacity and disk I/O utilization is now available for IBM Cloud® Messages for RabbitMQ via the UI, API, and CLI. See blog post announcement [here](https://www.ibm.com/cloud/blog/announcements/ibm-cloud-databases-portfolio-introduces-autoscaling).





 6 August 2019 

New Regions Available for IBM Cloud Database Services
: IBM Cloud® Messages for RabbitMQ is now available to be deployed in Seoul; South Korea; and Chennai, India. See blog post announcement [here](https://www.ibm.com/cloud/blog/announcements/new-regions-available-for-ibm-cloud-database-services).





 19 December 2018 

General Availability of IBM Cloud® Messages for RabbitMQ
: IBM Cloud® Messages for RabbitMQ added to the [IBM Cloud Databases](https://www.ibm.com/cloud/databases) family. See blog post announcement [here](https://www.ibm.com/cloud/blog/ibm-cloud-databases-for-etcd-elasticsearch-and-messages-for-rabbitmq-are-now-generally-available).
* Capital expense budgets are under tight control, and IT feels they don't have the budget or staff to create the needed testing and staging landscapes with their in-house systems.







 Solution 

Compute, storage, and I/O services run in the public cloud with secure access to on-premises enterprise assets. Implement a CI/CD process and other parts of the IBM Garage Method to dramatically shorten delivery cycles.



 Step 1: Secure the compute platform 



* From that core, Vulnerability Advisor provides image, policy, container, and packaging scanning vulnerability scanning.
* Consistently enforce policy-driven authentication to your services and APIs with a simple Ingress annotation. With declarative security you can ensure user authentication and token validation by using App ID.







 Step 2: Lift and shift 



* Migrate virtual machine images to container images that run in Red Hat OpenShift on IBM Cloud in the public cloud.
* Deploy IBM Cloud Pak for Data, so that developers have their familiar analytics tools on the cloud.
* Provide standardized DevOps dashboards and practices through Kubernetes.
* Enable scaling compute resources for batch and other back-office workloads that run infrequently.
* Use IBM® Secure Gateway for IBM Cloud® to maintain secure connections to on-premises DBMS.
* Private data center / on-premises capital costs are greatly reduced and replaced with a utility computing model that scales based on workload demand.







 Step 3: Microservices and Garage Method 



* Reconfigure apps into a set of cooperative microservices. That set runs within Red Hat OpenShift on IBM Cloud that is based on functional areas of the app with the most quality problems.
* Use IBM Cloudant with customer provided keys for caching data in the cloud.
* Adopt continuous integration and delivery (CI/CD) practices so that Developers version and release a microservice on its own schedule as needed. IBM Cloud® Continuous Delivery provides for workflow toolchains for CI/CD process along with image creation and vulnerability scanning of container images.
* Adopt the agile and iterative development practices from the IBM Garage Method to enable frequent releases of new functions, patches, and fixes without downtime.



Technical solution



* Red Hat OpenShift on IBM Cloud
Because IBM does not support using Hyperledger Composer for production implementation, you are encouraged to engage with [Hyperledger Composer community](https://chat.hyperledger.org/channel/composer) and [Stack Overflow](https://stackoverflow.com/questions/tagged/hyperledger-composer) when you work on demos and proofs of concept.





 Submitting support cases 

For issues that are related to IBM Blockchain Platform for IBM Cloud, you can submit a support case in the [IBM Cloud Service Portal](https://cloud.ibm.com/unifiedsupport/supportcenter).

If you need help with Hyperledger Fabric or your applications, you can make use of the community resources or engage [IBM Blockchain Services](https://www.ibm.com/blockchain/services). It is recommended to use Hyperledger Composer solely for demos and proofs of concept. IBM does not support networks that use Hyperledger Composer in production, including the Composer CLI, JavaScript APIs, REST server, and Web Playground.

The response to your support case depends on your [IBM Cloud support plan](https://cloud.ibm.com/docs/get-support?topic=get-support-support-planssupport-plans).



* If you purchased Premium Support or Advanced Support, you can specify a severity level on your ticket from Sev-1 to Sev-4. Sev-1 is the highest level of severity. Support cases with higher severity levels indicate more urgency and are responded to more quickly by the support team. Ensure that the ticket severity is assigned based on the published criteria that is defined in [Case severity and response times](https://cloud.ibm.com/docs/get-support?topic=get-support-support-case-severity). For more information, see [IBM Cloud support plan offerings](https://cloud.ibm.com/docs/get-support?topic=get-support-support-planssupport-plans).
* If you do not purchase support, your IBM Cloud Pay-As-You-Go or Subscription account comes with a free Basic Support plan.
If you're interested in programmer interfaces, the [REST API](https://cloud.ibm.com/docs/cloud-object-storage/api-reference?topic=cloud-object-storage-compatibility-api) will provide an in-depth look at operations and configurations.





 Provision and configure IBM Cloud Object Storage 



1. If you haven't already, create an instance of IBM Cloud Object Storage from the [Console](https://cloud.ibm.com/catalog/services/cloud-object-storage).
2. Create any buckets that you anticipate will be needed to store your transferred data. If you haven't already, read through the [getting started guide](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage) to familiarize yourself with key concepts such as [endpoints](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-endpoints) and [storage classes](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-classes).
3. While Object Storage is compatible with the S3 API, it may be necessary to create new [Service credentials](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-service-credentials), or bring your own keys for your projects. In this guide, we will use [HMAC credentials](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-uhc-hmac-credentials-main) similar to the format of AWS credentials.
4. Managing [encryption](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-encryption) provides insights into security.
Applying Updates 

The deployment of IBM Cloud for VMware Solutions provides the following components:



*  VMware



*  vSphere Hypervisor (ESXi)
*  vCenter Server
*  NSX-T
*  VSAN
*  vRealize



*  Entrust
*  Caveonix
*  Veeam Backup and Replication



When applying patches, it is important to ensure version compatibility between each component is maintained. Compatibility matrixes are available at the following locations:



*  [VMware (includes vSphere Hypervisor, vCenter Server, NSX-T, and VSAN, vRealize)](https://interopmatrix.vmware.com/Interoperability?col=1,&row=2,%26670,%26175,%2688,%26116,&isHideGenSupported=true&isHideTechSupported=true&isHideCompatible=false&isHideNTCompatible=false&isHideIncompatible=true&isHideNotSupported=true&isCollection=false)
*  [Entrust](https://my.hytrust.com/s/article/KB10127)
*  [Caveonix](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-managingcaveonixmanagingcaveonix-update)
*  [Veeam Backup & Replication](https://www.veeam.com/kb2443)
* [Solution brief: NetApp Private Storage for IBM Cloud®](http://www.netapp.com/us/media/ds-3619_tcm10-127472.pdf)
* Recommended workloads - Tier 1
* Performance - Dependent on NetApp model
* Scalability - Supports extra of drives and frames for increased capacity and IOPS
* Protocols: - iSCSI, NFS, and SMB
* Cost - High for both CapEx and OpEx
* HA - Dual heads and controllers
* Replication - Supports SnapVault and SnapMirror, which is achieved by using [vRealize Automation](https://www.vmware.com/products/vrealize-automation.html).
* Reliability - High redundancy and MPIO support







 IBM Spectrum Accelerate 

The IBM Spectrum Accelerate private storage option is not available on the IBM Cloud catalog.



* Recommended workloads: Tier 1
* Performance: Dependent upon number of disks, SSD (optional), and amount of memory that is given to each “node” VM.
* Scalability: Scales 8 - 325 TB usable



* Minimum capacity: 3 VMs x 6 drives
* Maximum capacity: 15 VMs x 12 drives
* Scales up to 144 virtual arrays and more than 40 PB usable through IBM Hyper-Scale Manager
* Nondisruptive capacity expansion by adding more nodes
* 1 x 500 or 800 GB SSD per node supported



* Protocols: iSCSI only
* Cost: Dependent upon pricing model and physical machines that are deployed for nodes. High CapEx; medium to low OpEx depending on licensing.



* Priced per binary (TiB) of usable capacity
* Not tied to any specific hardware configuration. Example: 200 TiB license can be deployed various ways – one 200 TiB instance, two 100 TiB instances, or four 50 TiB instances
* Offered two ways: perpetual license [includes one year of subscription and service (S&S)] and monthly license (includes S&S)



* HA: Clustered solution
To host the HR site, they could easily design Kubernetes clusters to fit their CPU, RAM, and storage needs. Another factor for less personnel costs is that IBM manages Kubernetes, so the Developers can focus on delivering better employee experience for benefits enrollment.

IBM Cloud Kubernetes Service provides scalable compute resources and the associated DevOps dashboards to create, scale, and tear down apps and services as needed. Using industry-standard containers technology apps can be quickly developed and shared across multiple Development, Test, and Production environments. This setup provides the immediate benefit of scalability. Using Kubernetes rich set of deployment and runtime objects, the HR team can monitor and manage upgrades to apps reliably. They can also replicate and scale the apps, by using defined rules and the automated Kubernetes orchestrator.



 Step 1: Containers, microservices, and the Garage Method 



* Apps are built in a set of cooperative microservices that run in IBM Cloud Kubernetes Service. The architecture represents the functional areas of the app with the most quality problems.
* Deploy apps to container in IBM Cloud Kubernetes Service, continuously scanned with IBM Vulnerability Advisor.
* Provide standardized DevOps dashboards through Kubernetes.
* Adopt the essential agile and iterative development practices within the IBM Garage Method to enable frequent releases of new functions, patches, and fixes without downtime.







 Step 2: Connections to existing benefits back-end 



* IBM® Secure Gateway for IBM Cloud® is used to create a secure tunnel to on-premises systems that host the benefits systems.
* Combination of on-premises data and IBM Cloud Kubernetes Service lets them access sensitive data while they adhere to regulations.
* Chatbot conversations fed back into HR policies, allowing the benefits site to reflect which benefits were most and least popular, including targeted improvements to poorly performing initiatives.







 Step 3: Chatbot and personalization 

Watson Assistant provides tools to quickly scaffold a chatbot that can provide the correct benefits information to users.





 Step 4: Deliver continuously across the globe 



* IBM Cloud® Continuous Delivery helps Developers to quickly provision an integrated toolchain, by using customizable, shareable templates with tools from IBM, third parties, and open source.
Read the [announcement](https://www.ibm.com/cloud/blog/explore-deployment-strategies-with-ibm-cloud-continuous-delivery).





 30 September 2021 

Delivery Pipeline
: Upgraded to [Tekton Pipelines v0.27.2](https://github.com/tektoncd/pipeline/releases/tag/v0.27.2).





 9 July 2021 

IBM Cloud® Continuous Delivery is now available in the Toronto Region.
: Each location has three different data centers and provides a full cloud service stack to enable high availability, redundancy, and geographical dispersion.





 29 June 2021 

DevSecOps Reference Implementation
: A complete SDLC following NIST Configuration Management controls that you can configure in a few clicks by using toolchain templates. The workflow will build, scan, test, and deploy your cloud-native applications while ensuring security and compliance goals are met and evidence is retained for any future audits. The workflow can be customized to leverage other enterprise tools or implement custom policies.

Read the [announcement](https://www.ibm.com/cloud/blog/announcements/devsecops-reference-implementation-for-audit-ready-compliance-across-development-teams).





 24 May 2021 

Code Risk Analyzer now scans Terraform
: Misconfiguration of infrastructure and cloud service dependencies can put enterprise applications and data at risk. Now, Code Risk Analyzer looks for these issues by scanning Terraform Infrastructure as Code (IaC) files.

Read the [announcement](https://www.ibm.com/cloud/blog/announcements/code-risk-analyzer-adds-terraform-scanning).





 30 April 2021 

IBM Cloud® Continuous Delivery is now available in the Osaka region.
: Each location has three different data centers and provides a full cloud service stack to enable high availability, redundancy, and geographical dispersion.





 31 March 2021 

IBM Cloud® Continuous Delivery is now available in the Sydney region.
: Each location has three different data centers and provides a full cloud service stack to enable high availability, redundancy, and geographical dispersion.





 28 February 2021 

Delivery Pipeline
Added IBM® Event Streams for IBM Cloud® as a Satellite-enabled service
: See [Supported Satellite-enabled IBM Cloud services](https://cloud.ibm.com/docs/satellite?topic=satellite-managed-services) and [About IBM Cloud Satellite for Event Streams](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-satellite_about).

New location error message is added.
: For more information see [R0058: DNS registration is failing](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0058).





 12 May 2022 

New! Satellite configuration and assignment update commands
: You can now update and upgrade your Satellite storage configurations and assignments from the CLI. For more information, see the [Satellite storage commands](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencesat-storage-commands).







 April 2022 



 28 April 2022 

CLI change log
: Updated the CLI plug-in change log page for the [release of version 1.0.404](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-changelog).





 26 April 2022 

CLI change log
: Updated the CLI plug-in change log page for the [release of version 1.0.403](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-changelog).





 20 April 2022 

New! Osaka location
: You can now manage Satellite locations from the Osaka (osa, jp-osa) [IBM Cloud region](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-regions).





 18 April 2022 

Set up an HTTP proxy for your hosts
: In allowlisted accounts that have locations enabled for Red Hat CoreOS, you can configure an HTTP proxy.
FAQs 

Review frequently asked questions (FAQs) for using IBM Cloud® Kubernetes Service.



 What is Kubernetes? 

Kubernetes is an open source platform for managing containerized workloads and services across multiple hosts, and offers managements tools for deploying, automating, monitoring, and scaling containerized apps with minimal to no manual intervention. All containers that make up your microservice are grouped into pods, a logical unit to ensure easy management and discovery. These pods run on compute hosts that are managed in a Kubernetes cluster that is portable, extensible, and self-healing in case of failures.

For more information about Kubernetes, see the [Kubernetes documentation](https://kubernetes.io/docs/home/?path=users&persona=app-developer<=vel=foundational).





 How does IBM Cloud Kubernetes Service work? 

With IBM Cloud Kubernetes Service, you can create your own Kubernetes cluster to deploy and manage containerized apps on IBM Cloud. Your containerized apps are hosted on IBM Cloud infrastructure compute hosts that are called worker nodes. You can choose to provision your compute hosts as [virtual machines](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodesvm) with shared or dedicated resources, or as [bare metal machines](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodesbm) that can be optimized for GPU and software-defined storage (SDS) usage. Your worker nodes are controlled by a highly available Kubernetes master that is configured, monitored, and managed by IBM. You can use the IBM Cloud Kubernetes Service API or CLI to work with your cluster infrastructure resources and the Kubernetes API or CLI to manage your deployments and services.

For more information about how your cluster resources are set up, see the [Service architecture](https://cloud.ibm.com/docs/containers?topic=containers-service-arch).
Supported IBM Cloud and third-party integrations 

You can use various IBM®, IBM Cloud®, and external services with a standard cluster in IBM Cloud Kubernetes Service.



 Popular integrations 



Table 1. Popular integrations

 Service Category Description Classic VPC 

 IBM Cloud Activity Tracker Cluster activity logs Monitor the administrative activity that is made in your cluster by analyzing logs through Grafana. For more information about the service, see the [Activity Tracker](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-getting-started) documentation. For more information about the types of events that you can track, see [Activity Tracker events](https://cloud.ibm.com/docs/containers?topic=containers-at_events). Yes Yes 
 IBM Cloud App ID Authentication Add a level of security to your apps with [App ID](https://cloud.ibm.com/docs/appid?topic=appid-getting-started) by requiring users to sign in. To authenticate web or API HTTP or HTTPS requests to your app, you can integrate App ID with your Ingress service by using the [App ID authentication Ingress annotation](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsapp-id-auth). Yes Yes 
 IBM Cloud Classic Block Storage Block storage [IBM Cloud Block Storage](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-getting-startedgetting-started) is persistent, high-performance iSCSI storage that you can add to your apps by using Kubernetes persistent volumes (PVs). Use block storage to deploy stateful apps in a single zone or as high-performance storage for single pods. For more information about how to provision block storage in your cluster, see [Setting up IBM Cloud Block Storage](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_storage) Yes