vania-janet/multiturn-rag-retrieval-data huggingface dataset:
IBM Cloud File Storage for Classic plug-in and monitor 375 377 Fixed a bug that prevents persistent volume claim (PVC) creation failures from being retried. Updated to use Go version 1.13.8. 
 IBM Cloud RBAC Operator 8882606 d80b738 Updated image for [CVE-2020-12049](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12049) and to use Go version 1.13.14. 
 Key Management Service provider v1.0.0 v2.0.2 Updated image for [CVE-2020-15586](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15586). 
 Kubernetes configuration N/A N/A The Kubernetes API server audit policy configuration is updated to include auditing of all API groups except apiregistration.k8s.io and coordination.k8s.io. 
 Red Hat OpenShift Control Plane Operator v4.4.0-20200615 v4.4.0-20200805 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.4.0+20200805). 
 Red Hat OpenShift 4.4.11 4.4.16 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.4/release_notes/ocp-4-4-release-notes.htmlocp-4-4-16). 
 Red Hat OpenShift on IBM Cloud toolkit v4.4.0+20200615 v4.4.0+20200805 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.4.0+20200805).
IBM Cloud File Storage for Classic plug-in and monitor 408 410 Updated universal base image (UBI) to version 8.6-751 to resolve CVEs. 
 IBM Cloud RBAC Operator 8c8c82b 8c96932 Updated Go to version 1.18.1 
 Key Management Service provider v2.5.4 v2.5.5 Updated Go to version 1.17.10 and updated the golang dependencies. 
 Load balancer and load balancer monitor for IBM Cloud Provider 1916 1998 Updated Go to version 1.17.10 and updated dependencies. 
 OpenVPN Operator image v1.4.3 v1.4.5 Updated base image to v1.21.0 for CVE remediation. 
 Portieris admission controller v0.10.3 v0.12.4 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.12.4). 
 Red Hat OpenShift on IBM Cloud. 4.7.48 4.7.50 See the [Red Hat OpenShift on IBM Cloud release notes](https://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-release-notes.htmlocp-4-7-50). 
 Red Hat OpenShift on IBM Cloud Control Plane Operator v4.7.0-20220411 v4.7.0-20220509 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20220509). 
 Red Hat OpenShift on IBM Cloud Metrics Server v4.7.0-20220411 v4.7.0-20220509 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20220509).
IBM Cloud File Storage for Classic plug-in and monitor 420 421 Updated universal base image (UBI) to resolve [CVE-2022-42898](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42898). Updated Go to version 1.18.8 
 Key Management Service provider v2.5.11 v2.5.12 Updated Go dependencies. 
 Load balancer and load balancer monitor for IBM Cloud Provider 2110 2325 Update Go to version 1.19.1 and update dependencies. 
 OpenVPN Operator image v1.4.11 v1.4.13 Updated the ansible operator base image to v1.25.2 to resolve CVEs. 
 Red Hat OpenShift on IBM Cloud Control Plane Operator v4.7.0-20221104 v4.7.0-20221205 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20221205). 
 Red Hat OpenShift on IBM Cloud. 4.7.59 4.7.60 See the [Red Hat OpenShift on IBM Cloud Release Notes](https://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-release-notes.htmlocp-4-7-60). 
 Red Hat OpenShift on IBM Cloud Metrics Server and toolkit v4.7.0-20221104 v4.7.0-20221205 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20221205). 







 Change log for worker node fix pack 4.7.60_1591_openshift, released 05 December 2022 

The following table shows the changes that are in the worker node fix pack 4.7.60_1591_openshift.
Automated 2 [Not checked](https://cloud.ibm.com/docs/openshift?topic=openshift-benchmarks_413_coco-benchmark-413-remdiations) 







 5.4 Secrets management 



Section 5.4 Secrets management benchmark results

 Section Recommendation Manual/Automated Level Result 

 5.4.1 Prefer to use secrets as files over secrets as environment variables. Manual 1 Not checked 
 5.4.2 Consider external secret storage. Manual 2 Not checked 







 5.5 Extensible admission control 



Section 5.5 Extensible admission control benchmark results

 Section Recommendation Manual/Automated Level Result 

 5.5.1 Configure image provenance by using image controller configuration parameters. Manual 2 Not checked 







 5.7 General policies 



Section 5.7 General policies benchmark results

 Section Recommendation Manual/Automated Level Result 

 5.7.1 Create administrative boundaries between resources by using namespaces. Manual 1 Not checked 
 5.7.2 Ensure that the seccomp profile is set to docker/default in your pod definitions. Manual 2 Not checked 
 5.7.3 Apply security context to your pods and containers. Manual 2 Not checked 
 5.7.4 Do not use the default namespace. Automated 2 Not checked 









 Remediations and explanations 



Remediations and explanations

 Section Recommendation/Explanation 

 1.2.23 Red Hat OpenShift on IBM Cloud can optionally enable Kubernetes API server auditing. 
 1.2.33 Red Hat OpenShift on IBM Cloud can optionally enable a Kubernetes Key Management Service (KMS) provider. 
 1.2.34 Red Hat OpenShift on IBM Cloud can optionally enable a Kubernetes Key Management Service (KMS) provider. 
 2.7 Red Hat OpenShift on IBM Cloud configures a unique Certificate Authority for etcd. 
 5.2.8 Red Hat OpenShift on IBM Cloud installs custom SCCs. 
 5.3.2 Red Hat OpenShift on IBM Cloud has a set of default Calico network policies defined and additional network policies can optionally be added.
machine-name-3 ccccc3c33ccccc3333cc assigned Ready mycluster12345 sat-virtualser-948b454ea091bd9aeb8f0542c2e8c19b82c5bf7a 169.xx.xxx.xxx
3. Remove the worker nodes or clusters by referring to the following options. The corresponding hosts in your Satellite location become unassigned and require a reload before you can use them for other Satellite resources.



* [Resize worker pools](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersresize_pool) to reduce the number of worker nodes in the cluster.
* [Remove individual worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_worker_rm) from the cluster.
* [Remove the cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-remove).



4. For each worker node that you removed, decide what to do with the corresponding host in your Satellite location.



* Reload the host operating system so that you can re-attach and re-assign the host to other Satellite resources such as the location control plane or other clusters. For more information, see the update process in [Updating Satellite location control plane hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-host-update-location).
* Delete the hosts from your underlying infrastructure provider. For more information, refer to the infrastructure provider documentation.









 Limitations for Red Hat OpenShift clusters in IBM Cloud Satellite 

See [Satellite cluster limitations](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_limitationssatellite_limits).





 Pricing for clusters in Satellite 

Review the table for information on charges related to Red Hat OpenShift clusters in IBM Cloud Satellite.
: Version [1.15.1](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1151) is available.





 11 October 2022 

Block Storage for VPC add-on version 5.0.
: For more information, see [the change log](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_bs_changelog).





 10 October 2022 

Worker node fix pack
: Red Hat OpenShift [4.10.35_1538_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_410),[4.9.49_1558_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49), [4.8.50_1575_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_48), [4.7.59_1584_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_47), and [4.6.61_1602_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_46).

Cluster autoscaler add-on version 1.0.6_828.
: For more information, see [Cluster autoscaler add-on change log](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog).





 5 October 2022 

Red Hat Enterprise Linux version 8 is available for Red Hat OpenShift on IBM Cloud 4.9 and 4.10 clusters
: You can now create Red Hat OpenShift on IBM Cloud 4.9 and 4.10 clusters using Red Hat Enterprise Linux version 8 worker nodes.
: Updated the [required IP addresses and ports](https://cloud.ibm.com/docs/openshift?topic=openshift-firewallfirewall_outbound) that you must open in a public gateway device firewall.

IAM issuer details
: Added a [reference topic](https://cloud.ibm.com/docs/openshift?topic=openshift-access_reference) for the IAM issuer details of RBAC users.





 16 March 2020 

New! CLI 1.0
: Updated the Red Hat OpenShift on IBM Cloud CLI plug-in change log page for the [release of version 1.0.0](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelog10). This version contains permanent syntax and behavior changes that are not compatible with earlier versions, so before you update be sure to follow the guidance in [Using version 1.0 of the plug-in](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelogchangelog_beta).

Default service settings
: Added a page to describe the [default service settings for Red Hat OpenShift components](https://cloud.ibm.com/docs/openshift?topic=openshift-service-settings).

Image build errors
: Added a troubleshooting topic for [build errors due to image pull authentication](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-app-build-img-pull).

Installing SGX drivers
: Added a topic for [installing SGX drivers and platform software on SGX-capable worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersinstall-sgx).

Sizing workloads
: Enhanced the topic with a [How do I monitor resource usage and capacity in my cluster?]
[Auto deployment button](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/autodeploy_button.png)[Deploy to IBM Cloud](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/Cloud-Schematics/multizone-iks-on-vpc-cluster&terraform_version=terraform_v0.12) <br> 
 [Red Hat OpenShift on IBM Cloud cluster on classic infrastructure](https://github.com/Cloud-Schematics/openshift-cluster) Provision of a simple Red Hat OpenShift cluster on Classic infrastructure. ![Auto deployment button](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/autodeploy_button.png)[Deploy to IBM Cloud](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/Cloud-Schematics/openshift-cluster&terraform_version=terraform_v0.13) <br> 
 [Red Hat OpenShift on IBM Cloud cluster on Classic infrastructure for development environment](https://github.com/Cloud-Schematics/openshift-dev-cluster) Provision of a Red Hat OpenShift cluster on Classic infrastructure for a development team with IBM Cloud operation, Red Hat CodeReady. !
: For more locations, see [Single and multizone locations in Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zones).





 3 September 2019 

New! Red Hat OpenShift on IBM Cloud plug-in version 0.4
: Updated the IBM Cloud Kubernetes Service CLI plug-in change log page for multiple changes in the [release of version 0.4.1](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelog).

Version change log
: Worker node patch updates are available for Kubernetes [1.15.3_1516](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog1153_1516_worker), [1.14.6_1532](https://cloud.ibm.com/docs/containers?topic=containers-114_changelog1146_1532_worker), [1.13.10_1535](https://cloud.ibm.com/docs/containers?topic=containers-113_changelog11310_1535_worker), [1.12.10_1566](https://cloud.ibm.com/docs/containers?topic=containers-112_changelog11210_1566_worker), and Red Hat OpenShift [3.11.135_1523](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311135_1523_worker).







 August 2019 



 30 August 2019 

New! Paris, France par01 single zone location for Red Hat OpenShift clusters
: For more locations, see [Single and multizone locations in Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zones).





 29 August 2019 

Forwarding Kubernetes API audit logs to IBM Log Analysis
Debugging your Portworx installation 

Virtual Private Cloud

Classic infrastructure

 What’s happening 

When you create a Portworx service instance from the IBM Cloud catalog, the Portworx installation in your cluster fails and the service instance shows a status of Provision failure.

 Why it’s happening 

Before Portworx is installed in your cluster, a number of checks are performed to verify the information that you provided on the Portworx service page of the IBM Cloud catalog.

If one of these checks fails, the status of the Portworx service is changed to Provision failure. You can't see the details of what check failed or what information is missing to complete the installation.

 How to fix it 

Follow this guide to start troubleshooting your Portworx installation and to verify the information that you entered in the IBM Cloud catalog.

If you find information that you entered incorrectly or you must change the setup of your cluster, correct the information or the cluster setup. Then, create a new Portworx service instance to restart the installation.



 Step 1: Verifying the IBM Cloud catalog information 

Start by verifying that the information that you entered in the IBM Cloud catalog is correct. If information was entered incorrectly, the installation does not pass the pre-installation checks and fails without starting the installation.



1. Verify that the cluster where you want to install Portworx is located in the IBM Cloud region and resource group that you selected.

ibmcloud ks cluster get --cluster <cluster_name_or_ID>
2. Verify that the IBM Cloud API key that you entered has sufficient permissions to work with your cluster. You must be assigned the Editor platform access role and the Manager service access role for IBM Cloud Kubernetes Service. For more information, see [User access permissions](https://cloud.ibm.com/docs/containers?topic=containers-access_reference).
3. Verify that you entered the etcd API endpoint for your Databases for etcd service instance in the correct format.



1.
All security groups for VPC](https://cloud.ibm.com/docs-content/v1/content/f89cc64b006ca59b35404693959c83d5747fee3e/sap//images/quickstudy-intel-vs-gen2-image5.png)

Figure 14. All security groups for VPC





 Installing SAP software 

After you download the installation media, follow the standard SAP installation procedure that is documented in the [SAP installation guides](https://help.sap.com/viewer/index) for your SAP version and components. Also, review the corresponding SAP notes. See more detailed information about SAP NetWeaver installation that uses Db2 as the RDBMS in [Considerations about IBM Db2](https://cloud.ibm.com/docs/sap?topic=sap-anydb-ibm-db2).





 Relevant SAP Notes 



* [SAP Note 2002167 - Red Hat Enterprise Linux 7.x: Installation and Upgrade](https://launchpad.support.sap.com//notes/2002167).
* [SAP Note 2923773 - Linux on IBM Cloud (IaaS): Adaption of your SAP License](https://launchpad.support.sap.com//notes/2923773).
Are you unable to install the IBM Log Analysis agent on Red Hat Linux? 

Installation of the IBM® Log Analysis agent fails on Red Hat Linux.

  What’s happening 

When you install the IBM Log Analysis agent with the [agent installation instructions](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-config_agent_rhel3), the installation fails when the sudo yum install logdna-agent command is run.

  Why it’s happening 

You need to update the crypto policies default to SHA1 for the logdna-agent before you install the agent.

To resolve this issue, run the following commands before you run the sudo yum install logdna-agent command.

update-crypto-policies --set DEFAULT:SHA1
dnf install logdna-agent
update-crypto-policies --set DEFAULT:NO-SHA1
Why are Istio components missing? 

Virtual Private Cloud

Classic infrastructure

  What’s happening 

One or more of the Istio control plane components, such as istiod, does not exist in your cluster.

  Why it’s happening 

Review the following possible causes:



*  You deleted one of the Istio deployments that is installed in your cluster Istio managed add-on.
*  You changed the default IstioOperator (IOP) resource. When you enable the managed Istio add-on, you can't use IstioOperator (iop) resources to customize the Istio control plane installation. Only the IstioOperator resources that are managed by IBM for the Istio control plane are supported. Changing the control plane settings might result in an unsupported control plane state. If you create an IstioOperator resource for custom gateways in your Istio data plane, you are responsible for managing those resources.



  How to fix it 

To verify the control plane components installation:



1.  Check the values of any customizations that you specified in the customization ConfigMap. For example, if the value of the istio-components-pilot-requests-cpu setting is too high, control plane components might not be scheduled.

kubectl describe cm managed-istio-custom -n ibm-operators

{: pre}
2.  Check the logs of the Istio operator. If any logs indicate that the operator is failing to reconcile your customization settings, verify your settings for the [customized Istio installation](https://cloud.ibm.com/docs/containers?topic=containers-istiocustomize) again.

kubectl logs -n ibm-operators -l name=managed-istio-operator
3.  Optional: To refresh your managed-istio-custom ConfigMap resource, delete the ConfigMap from your cluster. After about 5 minutes, a default ConfigMap that contains the original installation settings is created in your cluster. The Istio operator reconciles the installation of Istio to the original add-on settings, including the core components of the Istio control plane.

kubectl delete cm managed-istio-custom -n ibm-operators
4.  If Istio control plane components or other Istio resources are still unavailable, refresh the cluster master.

ibmcloud ks cluster master refresh -c <cluster_name_or_ID>
prod-HyTrustCC-shortID-@domainName Used for installation and configuration of the Entrust CloudControl™ service. 
 prod-HyTrustDC-shortID-@domainName Used for configuration of the Entrust DataControl® service. 
 prod-HyTrustKC-shortID-@domainName Used for installation and configuration of the Entrust KeyControl™ service. 
 prod-KMIPAdapter-dynamicID-@domainName Used for installation and configuration of the KMIP™ for VMware service. 
 prod-ICP-dynamicID-@domainName Used for installation and configuration of the IBM Cloud Private Hosted service. 
 prod-SPPlus-dynamicID-@domainName Used for installation and configuration of the IBM Spectrum® Protect Plus service. 
 prod-Veeam-dynamicID-@domainName Used for installation and configuration of the Veeam® service. 
 prod-HCX-dynamicID-@domainName Used for installation and configuration of the VMware HCX™ service. 
 prod-Zerto-dynamicID-@domainName Used for installation and configuration of the Zerto service. 



In the [previous table](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-audit_user_idsaudit_user_ids-services-table), the following notations are used:



* dynamicID The 8 - 10 characters that generated dynamically during the service installation.
* shortID The 5 characters that generated dynamically during the service installation.
* domainName The domain name of your instance.







 Related links 



* [Considerations about changing vCenter Server artifacts](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcenter_chg_impactvcenter_chg_impact-automation-id)
* [Auditing events for VMware Solutions](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-at-eventsat-events)
[Plan your environment](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-plan) for Satellite by choosing your infrastructure, thinking about the services that you want to use, and setting up the hosts that you want to use. Make sure your hosts meet the [minimum requirement](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs) and that you consider the [size of your location](https://cloud.ibm.com/docs/satellite?topic=satellite-location-sizing).

Zoom

![Plan for your Satellite location.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite//images/1-plan-location.svg)

Figure 2. Planning for your Satellite location
2. Create your location that runs on your host infrastructure. [Choose an installation method](https://cloud.ibm.com/docs/satellite?topic=satellite-locations) for your location, based on what is available for your infrastructure provider.

Zoom

![Create your location.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite//images/2-create-location.svg)

Figure 3. Creating your Satellite location
3. [Attach hosts to your location](https://cloud.ibm.com/docs/satellite?topic=satellite-locationslocation-create-manual) by running the installation scripts (RHEL) or ingestion scripts (RHCOS). If you are using a Schematics template, this step is done for you. After your hosts are attached, they are in an unassigned state.

Zoom

![Attach hosts to your location.]
For more information about accessing the tenant portal, see [Log in to the VMware Cloud Director tenant portal](https://docs.vmware.com/en/VMware-Cloud-Director/10.1/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-28972197-D45B-4156-A733-5966730B5E03.html).

For more information about creating and modifying tenant portal users, see [Managing users](https://docs.vmware.com/en/VMware-Cloud-Director/10.1/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-FE38C285-7605-4473-870C-6AD44D8BF42E.html).





 Modifying your email settings 

The Organization Administrator must modify email notification settings to the organization SMTP server.

For more information about modifying SMTP server settings, see [Modify your email settings](https://docs.vmware.com/en/VMware-Cloud-Director/10.1/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-726D40D7-4251-47AD-B945-2030E489165F.html).









 Catalogs 

A catalog is a container for vApp templates and media files in an organization. Organization administrators and catalog authors can create catalogs in an organization. Catalog contents can be shared with other users or organizations in the VMware Shared installation. Or they can be published externally for access by organizations outside the VMware Shared installation.

VMware Shared contains private catalogs, shared catalogs, and externally accessible catalogs. Private catalogs include vApp templates and media files that you can share with other users in the organization. If a system administrator enables catalog-sharing for your organization, you can share an organization catalog to create a catalog accessible to other organizations in the VMware Shared installation.

If a system administrator enables external catalog publishing for your organization, you can publish an organization catalog for access by organizations outside the VMware Shared installation.