vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: Master fix pack update change log documentation is available for version [4.6.16_1532_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464616_1532), [4.5.31_1530_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4531_1530), [4.4.33_1534_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4433_1534), [4.3.40_1555_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4340_1555), and [3.11.380_1581_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311380_1581).





 20 February 2021 

Certified Kubernetes
: Version [4.6 (Kubernetes 1.19)](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions) release is now certified.





 17 February 2021 

New! Red Hat OpenShift 4.6
: You can create or [update](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versions) your cluster to Red Hat OpenShift version 4.6, which includes Kubernetes 1.19. With Red Hat OpenShift 4.6, you get the latest stable enhancements from the community. For more information, see the [blog announcement](https://www.ibm.com/cloud/blog/announcements/openshift-version-46-now-available-in-red-hat-openshift-on-ibm-cloud).

Deprecated Red Hat OpenShift 4.4
If you want to use a different IBM Cloud Monitoring service instance to send metrics to, use the [ibmcloud ob monitoring config replace](https://cloud.ibm.com/docs/containers?topic=containers-observability_climonitoring_config_replace) command.
* Red Hat OpenShift clusters in Satellite can't currently use the Red Hat OpenShift on IBM Cloud console or the observability plug-in CLI to enable monitoring for Satellite clusters. You must manually deploy monitoring agents to your cluster to forward metrics to Monitoring.
* If you created a Monitoring configuration in your cluster without using the Red Hat OpenShift on IBM Cloud observability plug-in, you can use the [ibmcloud ob monitoring agent discover](https://cloud.ibm.com/docs/containers?topic=containers-observability_climonitoring_agent_discover) command to make the configuration visible to the plug-in. Then, you can use the observability plug-in commands and functionality in the IBM Cloud console to manage the configuration.



Before you begin:



* Verify that you are assigned the Editor platform access role and Manager server access role for IBM Cloud Monitoring.
* Verify that you are assigned the Administrator platform access role and the Manager service access role for all Kubernetes namespaces in IBM Cloud Kubernetes Service to create the monitoring configuration. To view a monitoring configuration or launch the Monitoring dashboard after the monitoring configuration is created, users must be assigned the Administrator platform access role and the Manager service access role for the ibm-observe Kubernetes namespace in IBM Cloud Kubernetes Service.
* If you want to use the CLI to set up the monitoring configuration:



* [Install the Red Hat OpenShift on IBM Cloud observability CLI plug-in (ibmcloud ob)](https://cloud.ibm.com/docs/containers?topic=containers-cli-install).
* [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).





To set up a monitoring configuration for your cluster:



1.
Setting up disaster recovery with Portworx 

You can configure disaster recovery for your data that you store in your Red Hat OpenShift clusters by using Portworx. When one of your clusters becomes unavailable, Portworx automatically fails over to another cluster so that you can still access your data.

Disaster recovery with Portworx requires at least two Red Hat OpenShift clusters where Portworx is installed and configured for disaster recovery. One of the two clusters is considered the active cluster where your data is primarily stored. All data is then replicated to the standby cluster. If your active cluster becomes unavailable, Portworx automatically fails over to the standby cluster and makes the standby cluster the new active cluster so that data can continue to be accessed.

If you installed Portworx in one of your clusters without the Portworx disaster recovery plan, you must re-install Portworx with the disaster recovery plan so that you can include this cluster in your disaster recovery configuration.

Depending on your cluster setup, Portworx offers the following two disaster recovery configurations:



* [Metro DR](https://docs.portworx.com/portworx-install-with-kubernetes/disaster-recovery/1-metro-dr-nodes-are-in-the-metro-area-network-man): Your Red Hat OpenShift clusters are in the same metro location, such as both clusters are deployed in one or multiple zones of the us-south region. All clusters are configured to use the same Portworx cluster and share the same Portworx key-value store. Data is automatically replicated between the clusters because the Portworx storage layer is shared. RPO (Recovery Point Objective) and RTO (Recovery Time Objective) for this configuration is less than 60 seconds.
* [Asynchronous DR](https://docs.portworx.com/portworx-install-with-kubernetes/disaster-recovery/2-asynchronous-dr-nodes-are-across-different-regions-datacenters): Your Red Hat OpenShift clusters are deployed in different regions, such as us-south and us-east.
[Provisioning an IBM Cloud virtual server for classic infrastructure](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-sample_infrastructure_config)Provisioning an IBM Cloud virtual server for classic infrastructure

You can provision your virtual server for classic infrastructure by using the IBM Cloud Provider plug-in. Similar to the IBM Cloud virtual server for VPC provision that you provisioned. You need to create another configuration file with the specification for your virtual server instance.

Kubernetes service Red Hat OpenShift on IBM Cloud

+2

Red Hat OpenShift on IBM Cloud,Terraform on IBM Cloud



* 2 hours
* 2023-03-07



[Creating single and multizone Kubernetes and OpenShift clusters](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-tutorial-tf-clusters)Creating single and multizone Kubernetes and OpenShift clusters

Create a classic IBM Cloud Kubernetes Service or Red Hat OpenShift on IBM Cloud cluster by using Terraform on IBM Cloud.

Kubernetes service Red Hat OpenShift on IBM Cloud

+2

Red Hat OpenShift on IBM Cloud,Terraform on IBM Cloud



* 2 hours
* 2023-05-11



[Resetting the ingestion key that is used by a Kubernetes cluster](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-kube_reset_ingestion)Resetting the ingestion key that is used by a Kubernetes cluster

If the ingestion key that you use to forward logs from a cluster to an IBM Log Analysis instance in the IBM Cloud is compromised, you must reset the key and update the Kubernetes cluster configuration to use the new ingestion key.

Kubernetes service Log Analysis



* 1 hour
* 2021-03-28
To expose services and apps to the public internet, you can leverage the [VPC load balancer and Ingress ALB support](https://cloud.ibm.com/docs/containers?topic=containers-cs_network_planningpattern_public_vpc) to securely make your services publicly available. Ensure that only necessary services are exposed, and revisit the list of exposed apps regularly to ensure that they are still valid. 
 Limit public network egress to one subnet with a public gateway If pods on your worker nodes need to connect to a public external endpoint, you can attach a public gateway to the subnet that those worker nodes are on. 



Depending on the network that you want to connect your worker nodes to, you can [choose a VPN solution](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-vpnaas).





 Securely expose apps with routes 

If you want to allow incoming network traffic from the internet, you can expose your apps by using [routes](https://docs.openshift.com/container-platform/4.11/networking/routes/route-configuration.html).

Every Red Hat OpenShift cluster is automatically set up with a Red Hat OpenShift router that is assigned a unique domain name and secured with a TLS certificate. When you expose your app by using a route, your app is assigned a URL from the Red Hat OpenShift router.

When you create a route for your app, you can decide to create a secured (HTTPS) or unsecured (HTTP) route. For secured routes, you can decide where you want to implement the TLS termination, such as at the router or at the pod. For more information, see [Exposing apps with routes](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_routes).





 Securely expose apps with LoadBalancer and Ingress services 

You can use network load balancer (NLB) and Ingress application load balancer (ALB) networking services to connect your apps to the public internet or to external private networks.
Make sure that the IBM Cloud Kubernetes Service or Red Hat OpenShift Administrator role is assigned to your user account.
3. You need both a classic infrastructure API key and IBM Cloud VPC API key.
4. HMAC keys (Access Key ID and Secret Access Key) are required when you add a VPC account for workload backup and restore.





 Limitations 

Review the following limitations:



* Private clusters cannot be migrated.
* Only PVC with block storage is supported.
* For any services that rely on IPs, the IPs must be updated post-migration (for example, DNS, load balancers, security rules, etc.).









 Migrating to VPC 



1. Log in to the VPC+ tool.
2. Add your classic and VPC accounts. When you add your VPC account, make sure to provide the Access Key ID and Secret Access Key, which are required to migrate your cluster.
3. Select the Migrate Infrastructure option in the VPC+ Cloud Migration interface, and click Discover.
4. Select your IBM Cloud classic account, and then click Create VPC Migration Workspace.
5. You can now select the resource group, region, and zone where you want to migrate in VPC and the IBM Cloud Kubernetes Service or Red Hat OpenShift cluster that needs to be migrated.
6. Review the requirements and considerations for the following components:



* Address prefix - Classic address prefixes are not supported in VPC. Make sure to create a new address prefix and enable the public gateway.
* IBM Cloud Kubernetes Service or Red Hat OpenShift cluster name - The cluster name must be a new and unique.
* Worker nodes - Classic worker pool flavors are not supported in VPC.



7. After you select the appropriate resources and components, you can migrate your cluster to VPC.
8. After you migrate your clusters, verify and validate the clusters. You might need to do some fixes or redeployments on the migrated clusters, especially for Red Hat OpenShift clusters if you are using tooling specific to Red Hat OpenShift, such as internal image registry or operators.
The exact location of the installation configuration directory on the bastion is shown on the service details page.





 SSH key 

The SSH key on the bastion is installed on all Red Hat OpenShift cluster VMs, which allows SSH login from the bastion into any cluster VM. The full path to the SSH key is displayed on the service details page. For security purposes, it is highly recommended that you generate a new SSH key and update the cluster VMs with the new key. For more information, see [Changing the SSH key on the Red Hat OpenShift bastion](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-ocp_managingocp_managing-change-ssh-key).

When you log in to a cluster VM from the bastion, you must connect as the core user as shown in the following example: root@bastion ssh core@control-plane0.





 High availability 

The Red Hat OpenShift VMs are deployed with DRS rules to ensure that they are on physically separate hosts. If a host must be replaced or redeployed, you must adjust the preconfigured DRS rules before you proceed.





 Installation configuration files 

The installation configuration file install-config.yaml.bak is located in the installation directory on the bastion. The file is a copy of the original install-config.yaml file that was used by the openshift-install program to generate the ignition files. The generated ignition files can also be found in the installation directory on the bastion.

The oc and kubectl command-line tools from the Red Hat OpenShift client software are on the bastion. The installer program, named openshift-install, is used to install Red Hat OpenShift and can also be used to generate fresh ignition files.

The bastion also holds a file that is named auth/kubeconfig, needed for authentication. This file holds the initial kubeadmin credentials that are created during installation. Before you initially use the oc or kubectl tools, you must set the KUBECONFIG environment variable with the path to this file.
Quickly set up and manage gateways, control access on a per-resource basis, configure TLS encryption and mutual authentication, and monitor all of your traffic.
* [Aspera High Speed Transfer Server](https://www.ibm.com/blogs/bluemix/2018/12/enable-hybrid-cloud-data-movement-with-aspera-for-ibm-cloud-private/) - Send large files and data sets virtually anywhere, reliably, and at maximum speed. Accelerate collaboration and meet the demands of complex global teams, without compromising performance or security.







 Before you begin 

This documentation applies to installing the Cloud Pak on managed Red Hat OpenShift clusters provided by IBM Cloud® only. For more information about other methods of installation, see [Installation Options](https://www.ibm.com/docs/en/cloud-paks/cp-integration/latest?topic=installing-installation-options).

Before you can install the Cloud Pak on IBM Cloud®, you must set up a Red Hat OpenShift cluster using the [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/kubernetes/catalog/openshiftcluster) service.

The smallest cluster size that should be created to run CP4I is 1 worker with 32 vCPUs & 128GB memory. This will give you enough capacity to run Cloud Pak for Integration Common Services, Platform Navigator and a few small capabilities. For full details on the minimum required resources to run capabilities, see the [Cloud Pak for Integration Readme](https://cloud.ibm.com/catalog/content/ibm-cp-integrationabout).

Installation of Cloud Pak for Integration on IBM Cloud using the IBM software catalog does not support MZR clusters. See [Known limitations](https://cloud.ibm.com/docs/cloud-pak-integrationknown-limitations) for more details.





 Step 1. Obtain a license 

If you don't already have a license, you can:



* Purchase a license through [IBM Passport Advantage](https://www.ibm.com/software/passportadvantage/index.html)
To check whether a VRF is already enabled, use the ibmcloud account show command.
2. [Enable your IBM Cloud account to use service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointservice-endpoint).



Now, IBM Cloud Container Registry automatically uses the private cloud service endpoint. You don't need to enable the private cloud service endpoint for your Red Hat OpenShift on IBM Cloud clusters.

Do I have to use the private icr.io registry addresses for anything else?
: Yes, if you [sign your images for trusted content](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_trustedcontent), the signatures contain the registry domain name. If you want to use the private icr.io domain for your signed images, resign your images with the private icr.io domains.







 Updating existing clusters to use the API key image pull secret 

New Red Hat OpenShift on IBM Cloud clusters store an API key in [image pull secrets to authorize access to IBM Cloud Container Registry](https://cloud.ibm.com/docs/openshift?topic=openshift-registrycluster_registry_auth). With these image pull secrets, you can deploy containers from images that are stored in the icr.io registry domains. You can add the image pull secrets to your cluster if your cluster was not created with the secrets.

Before you begin



1. [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).
2. Make sure that you have the following permissions: IBM Cloud IAM Operator or Administrator platform access role for Red Hat OpenShift on IBM Cloud. The account owner can give you the role by running the following command.

ibmcloud iam user-policy-create <your_user_email> --service-name containers-kubernetes --roles <(Administrator|Operator)>
3.
[More info](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-LogDNA) 



To see the list of IBM Log Analysis locations where you can send logs, see [Container services](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-regions).





 Container services 

The following table lists services that send logs to IBM Log Analysis:



Table 3. List of container services

 Service Description More info 

 [IBM Cloud® Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-getting-started) You can use the IBM Cloud Kubernetes Service service to deploy highly available apps in Docker containers that run in Kubernetes clusters. [More info](https://cloud.ibm.com/docs/containers?topic=containers-healthlogdna) 
 [Red Hat® OpenShift® on IBM Cloud®](https://cloud.ibm.com/docs/openshift?topic=openshift-getting-started) With Red Hat OpenShift on IBM Cloud, you can deploy apps on highly available clusters that come installed with the Red Hat OpenShift on IBM Cloud Container Platform software installed on Red Hat Enterprise Linux. [More info](https://cloud.ibm.com/docs/openshift?topic=openshift-health) 
 [IBM Cloud Satellite®](https://cloud.ibm.com/docs/satellite?topic=satellite-getting-started) With IBM Cloud Satellite, you can bring your own compute infrastructure to run IBM Cloud services and consistently deploy, manage, and control your app workloads. [More info](https://cloud.ibm.com/docs/satellite?topic=satellite-health) 



To see the list of IBM Log Analysis locations where these services send logs, see [Container services](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-cloud_services_locationscs_locations_container).
By provisioning a single-node cluster, you accept that you are more likely to experience downtime and disruptions in your workload.



 Limitations 

Any cluster with fewer than three worker nodes lacks high availability. By provisioning a single-node cluster, you accept that you are more likely to experience downtime and disruptions in your workload, and that regular worker node upgrades result in your workload going offline. Additionally, if a cluster is provisioned as a single-node cluster, it can not later be converted to a standard, highly available cluster. You can add more nodes, but standard deployments do not increase in replica size and the cluster does not become highly available.



* OpenShift Data Foundation is not supported on single-node clusters.
* Portworx is not supported on single-node clusters.







 Requirements 

Single-node clusters must meet the following requirements:



* Must run on a Satellite location with [CoreOS enabled](https://cloud.ibm.com/docs/satellite?topic=satellite-locationsverify-coreos-location).
* Control plane hosts on your location and the host you assign to your single-node cluster must run either the RHEL 8 or RHCOS operating systems.
* Only supported for Satellite clusters that run version 4.11 or later.







 Creating a single-node cluster 

You can create a single-node cluster by including the --infrastructure-topology option and specifying the single-replica value when [creating a Satellite cluster in the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clicluster). If this option is not included, the cluster is provisioned with the highly available setup of three worker nodes by default.







 Accessing and working with your Satellite clusters 

After you created your Red Hat OpenShift cluster, you can use the capabilities in Red Hat OpenShift on IBM Cloud to work with your cluster.

Review common tasks that you might be interested in:



* [Accessing Red Hat OpenShift clusters on Satellite](https://cloud.ibm.com/docs/openshift?topic=openshift-access_clusteraccess_cluster_sat)
Quickly set up and manage gateways, control access on a per-resource basis, configure TLS encryption and mutual authentication, and monitor all of your traffic.
* [Aspera High Speed Transfer Server](https://www.ibm.com/blogs/bluemix/2018/12/enable-hybrid-cloud-data-movement-with-aspera-for-ibm-cloud-private/) - Send large files and data sets virtually anywhere, reliably, and at maximum speed. Accelerate collaboration and meet the demands of complex global teams, without compromising performance or security.







 Before you begin 

This documentation applies to installing the Cloud Pak on managed Red Hat OpenShift clusters provided by IBM Cloud® only. For more information about other methods of installation, see [Installation Options](https://www.ibm.com/docs/en/cloud-paks/cp-integration/latest?topic=installing-installation-options).

Before you can install the Cloud Pak on IBM Cloud®, you must set up a Red Hat OpenShift cluster using the [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/kubernetes/catalog/openshiftcluster) service.

The smallest cluster size that should be created to run CP4I is 1 worker with 32 vCPUs & 128GB memory. This will give you enough capacity to run Cloud Pak for Integration Common Services, Platform Navigator and a few small capabilities. For full details on the minimum required resources to run capabilities, see the [Cloud Pak for Integration Readme](https://cloud.ibm.com/catalog/content/ibm-cp-integrationabout).

Installation of Cloud Pak for Integration on IBM Cloud using the IBM software catalog does not support MZR clusters. See [Known limitations](https://cloud.ibm.com/docs/cloud-pak-integration?topic=cloud-pak-integration-getting-startedknown-limitations) for more details.





 Step 1. Obtain a license 

If you don't already have a license, you can:



* Purchase a license through [IBM Passport Advantage](https://www.ibm.com/software/passportadvantage/index.html)
5.2.2 Red Hat OpenShift on IBM Cloud can optionally [configure security context constraints](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc). 
 5.2.3 Red Hat OpenShift on IBM Cloud can optionally [configure security context constraints](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc). 
 5.2.4 Red Hat OpenShift on IBM Cloud can optionally [configure security context constraints](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc). 
 5.2.5 Red Hat OpenShift on IBM Cloud can optionally [configure security context constraints](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc). 
 5.2.6 Red Hat OpenShift on IBM Cloud can optionally [configure security context constraints](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc). 
 5.2.7 Red Hat OpenShift on IBM Cloud can optionally [configure security context constraints](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc). 
 5.2.8 Red Hat OpenShift on IBM Cloud can optionally [configure security context constraints](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc). 
 5.2.9 Red Hat OpenShift on IBM Cloud can optionally [configure security context constraints](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc).
Find the hosts to add to your Red Hat OpenShift cluster worker pool.

ibmcloud sat hosts --location <locationID>
2. Assign the Bare Metal Server to the Red Hat OpenShift cluster worker pool

ibmcloud sat host assign --location <locationID> --cluster <clusterID> --host <hostID> --worker-pool default --zone <zone>



Repeat this tutorial to attach more Bare Metal Servers to your location and cluster.

Now that your Bare Metal Server is assigned to a worker pool, you can [set up Red Hat OpenShift virtualization](https://cloud.ibm.com/docs/satellite?topic=satellite-virtualization-location).