vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Edit icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/edit-tagging.svg), and update the description with the following sentence:

Create and deploy a virtual server with ease by using a custom image.
2. Click Save > Next.







 Step 9: Validate the virtual server image 

Validate that you can deploy the virtual server image to your Power Systems Virtual Server instance.



1. From the Validate product tab, enter the name of your Schematics workspace, select a resource group, select a Schematics region, and click Next.

In the Tags field, you can enter a name of a specific tag to attach to your virtual server image. Tags provide a way to organize, track usage costs, and manage access to the resources in your account.
2. From the Deployment values section, review your parameter values, and click Next.
3. In the Validation product section, select I have read and agree to the following license agreements.
4. Click Validate.

To monitor the progress of the validation process, click View logs.







 Step 10: Manage compliance 

Controls are safeguards that are used to meet security and compliance requirements. Only controls that are supported by Security and Compliance Center, formatted correctly, and validated by Code Risk Analysis and Security and Compliance Center scans appear in the catalog. For more information, see [Adding compliance details](https://cloud.ibm.com/docs/account?topic=account-catalog-format-controls).



 Manage compliance controls 

You can review the controls that were added from your readme file and add additional controls.



1. Click Add controls.
2. Choose a profile.
3. Select the controls that you want to add to your version.
4. Click Add.







 Run Code Risk Analyzer scan 

Scan your source code with Code Risk Analyzer to identify any security vulnerabilities that you need to assess.



1. Click Run scan.
2.
RHEL 8 Packages 4.18.0-425.10.1 4.18.0-425.13.1 Worker node & kernel package updates for [CVE-2020-10735](https://nvd.nist.gov/vuln/detail/CVE-2020-10735), [CVE-2021-28861](https://nvd.nist.gov/vuln/detail/CVE-2021-28861), [CVE-2022-2873](https://nvd.nist.gov/vuln/detail/CVE-2022-2873), [CVE-2022-40897](https://nvd.nist.gov/vuln/detail/CVE-2022-40897), [CVE-2022-41222](https://nvd.nist.gov/vuln/detail/CVE-2022-41222), [CVE-2022-43945](https://nvd.nist.gov/vuln/detail/CVE-2022-43945), [CVE-2022-4415](https://nvd.nist.gov/vuln/detail/CVE-2022-4415), [CVE-2022-45061](https://nvd.nist.gov/vuln/detail/CVE-2022-45061), [CVE-2022-48303](https://nvd.nist.gov/vuln/detail/CVE-2022-48303). 
 Red Hat OpenShift 4.12.2 4.12.4 For more information, see the [change log](https://docs.openshift.com/container-platform/4.12/release_notes/ocp-4-12-release-notes.htmlocp-4-12-4).
RHEL 8 Packages 4.18.0-425.10.1 4.18.0-425.13.1 Worker node & kernel package updates for [CVE-2020-10735](https://nvd.nist.gov/vuln/detail/CVE-2020-10735), [CVE-2021-28861](https://nvd.nist.gov/vuln/detail/CVE-2021-28861), [CVE-2022-2873](https://nvd.nist.gov/vuln/detail/CVE-2022-2873), [CVE-2022-40897](https://nvd.nist.gov/vuln/detail/CVE-2022-40897), [CVE-2022-41222](https://nvd.nist.gov/vuln/detail/CVE-2022-41222), [CVE-2022-43945](https://nvd.nist.gov/vuln/detail/CVE-2022-43945), [CVE-2022-4415](https://nvd.nist.gov/vuln/detail/CVE-2022-4415), [CVE-2022-45061](https://nvd.nist.gov/vuln/detail/CVE-2022-45061), [CVE-2022-48303](https://nvd.nist.gov/vuln/detail/CVE-2022-48303). 
 Red Hat OpenShift on IBM Cloud. 4.11.26 4.11.28 For more information, see the [change log](https://docs.openshift.com/container-platform/4.11/release_notes/ocp-4-11-release-notes.htmlocp-4-11-28).
VRVDR-43307 Critical vyatta-ike-sa-daemon: TypeError: 'IKEConfig' object does not support indexing 
 VRVDR-42123 Major opd adds node.tag values under the wrong location in tab completion 







 Security Vulnerabilities Resolved 



Security vulnerabilities resolved for 1912g

 Issue Number CVSS score Advisory Summary 

 VRVDR-53323 7.5 DLA-2391-1 CVE-2020-25613: Debian DLA-2391-1 : ruby2.3 security update 
 VRVDR-53273 7.8 DLA-2385-1 CVE-2019-3874, CVE-2019-19448, CVE-2019-19813, CVE-2019-19816, CVE-2020-10781, CVE-2020-12888, CVE-2020-14314, CVE-2020-14331, CVE-2020-14356, CVE-2020-14385, CVE-2020-14386, CVE-2020-14390, CVE-2020-16166, CVE-2020-25212, CVE-2020-25284, CVE-2020-25285, CVE-2020-25641, CVE-2020-26088: Debian DLA-2385-1: linux-4.19 LTS security update 
 VRVDR-53272 9.8 DLA-2388-1 Debian DLA-2388-1 : nss security update 
 VRVDR-53231 N/A DLA-2382-1 CVE-2020-8231: Debian DLA-2382-1 : curl security update 
 VRVDR-53230 3.7 DLA-2378-1 CVE-2020-1968: Debian DLA-2378-1 : openssl1.0 security update 
 VRVDR-52817 6.4 N/A CVE-2020-15705: GRUB2 fails to validate kernel signature when booted directly without shim, allowing secure boot to be bypassed
RHEL 8 Packages 4.18.0-425.10.1 4.18.0-425.13.1 Worker node & kernel package updates for [CVE-2020-10735](https://nvd.nist.gov/vuln/detail/CVE-2020-10735), [CVE-2021-28861](https://nvd.nist.gov/vuln/detail/CVE-2021-28861), [CVE-2022-2873](https://nvd.nist.gov/vuln/detail/CVE-2022-2873), [CVE-2022-40897](https://nvd.nist.gov/vuln/detail/CVE-2022-40897), [CVE-2022-41222](https://nvd.nist.gov/vuln/detail/CVE-2022-41222), [CVE-2022-43945](https://nvd.nist.gov/vuln/detail/CVE-2022-43945), [CVE-2022-4415](https://nvd.nist.gov/vuln/detail/CVE-2022-4415), [CVE-2022-45061](https://nvd.nist.gov/vuln/detail/CVE-2022-45061), [CVE-2022-48303](https://nvd.nist.gov/vuln/detail/CVE-2022-48303). 
 Red Hat OpenShift on IBM Cloud. 4.10.51 4.10.52 For more information, see the [change log](https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.htmlocp-4-10-52).
OpenVPN server 2.5.4-r0-IKS-578 2.5.6-r0-IKS-591 Upgrade openvpn to version 2.5.6-r0. 







 Change log for worker node fix pack 1.20.15_1579, released 25 April 2022 



Changes since version 1.20.15_1577

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-175-generic 4.15.0-176-generic Kernel and package updates for [CVE-2018-16301](https://nvd.nist.gov/vuln/detail/CVE-2018-16301), [CVE-2019-18276](https://nvd.nist.gov/vuln/detail/CVE-2019-18276), [CVE-2020-8037](https://nvd.nist.gov/vuln/detail/CVE-2020-8037), [CVE-2021-31870](https://nvd.nist.gov/vuln/detail/CVE-2021-31870), [CVE-2021-31871](https://nvd.nist.gov/vuln/detail/CVE-2021-31871), [CVE-2021-31872](https://nvd.nist.gov/vuln/detail/CVE-2021-31872), [CVE-2021-31873](https://nvd.nist.gov/vuln/detail/CVE-2021-31873), [CVE-2021-43975](https://nvd.nist.gov/vuln/detail/CVE-2021-43975), [CVE-2022-1271](https://nvd.nist.gov/vuln/detail/CVE-2022-1271), [CVE-2022-24765](https://nvd.nist.gov/vuln/detail/CVE-2022-24765).
For more information on SDK Go or other languages, see the [VPC SDK reference](https://cloud.ibm.com/apidocs/vpc/latest?code=goupdate-ipsec-policy).





 Upgrading a VPN from a custom IKE policy with Terraform 

To upgrade the IKE policy by using Terraform, following these steps:



1. Run the terraform show command to find and get the name of the IKE policy that contains weak ciphers to be used in your Terraform.

terraform show
2. Find and update the .tf file of the IKE policy resource with secure ciphers in your Terraform, for example:

// main.tf
resource "ibm_is_ike_policy" "is_ike_policy" {
name = "my-ike-policy"
authentication_algorithm = "sha256"
encryption_algorithm = "aes128"
dh_group = 14
}

Where:



* name - The name of the IKE policy.
* authentication_algorithm - The authentication algorithm. One of: sha256, sha384, sha512.
* encryption_algorithm - The encryption algorithm. One of: aes128, aes192, aes256.
* dh_group - The Diffie-Hellman group. One of: 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 31.



3. Run the terraform apply command to update the IKE policy to use secure ciphers in your Terraform.

terraform apply



For more information, see the [Terraform registry](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_ike_policy).





 Upgrading a VPN from a custom IPsec policy with Terraform 

To upgrade the IPsec policy by using Terraform, follow these steps:



1. Run the terraform show command to find and get the name of the IPsec policy that contains weak ciphers to be used in your Terraform.

terraform show
2.
Component Previous Current Description 

 Kubernetes v1.14.8 v1.14.9 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.14.9). 
 Ubuntu 16.04 kernel and packages 4.4.0-166-generic 4.4.0-169-generic Updated worker node images with kernel and package updates for [CVE-2018-12207](https://nvd.nist.gov/vuln/detail/CVE-2018-12207), [CVE-2019-0154](https://nvd.nist.gov/vuln/detail/CVE-2019-0154), [CVE-2019-0155](https://nvd.nist.gov/vuln/detail/CVE-2019-0155), [CVE-2019-11135](https://nvd.nist.gov/vuln/detail/CVE-2019-11135), [CVE-2019-15098](https://nvd.nist.gov/vuln/detail/CVE-2019-15098), [CVE-2019-17052](https://nvd.nist.gov/vuln/detail/CVE-2019-17052), [CVE-2019-17053](https://nvd.nist.gov/vuln/detail/CVE-2019-17053), [CVE-2019-17054](https://nvd.nist.gov/vuln/detail/CVE-2019-17054), [CVE-2019-17055](https://nvd.nist.gov/vuln/detail/CVE-2019-17055), [CVE-2019-17056](https://nvd.nist.gov/vuln/detail/CVE-2019-17056), and [CVE-2019-17666](https://nvd.nist.gov/vuln/detail/CVE-2019-17666).
CVE-2019-20454](https://nvd.nist.gov/vuln/detail/CVE-2019-20454), [CVE-2019-19956](https://nvd.nist.gov/vuln/detail/CVE-2019-19956), [CVE-2019-20388](https://nvd.nist.gov/vuln/detail/CVE-2019-20388), [CVE-2020-7595](https://nvd.nist.gov/vuln/detail/CVE-2020-7595), [CVE-2019-13627](https://nvd.nist.gov/vuln/detail/CVE-2019-13627), [CVE-2018-20843](https://nvd.nist.gov/vuln/detail/CVE-2018-20843), [CVE-2019-15903](https://nvd.nist.gov/vuln/detail/CVE-2019-15903), and [CVE-2019-20387](https://nvd.nist.gov/vuln/detail/CVE-2019-20387). 
 IBM Cloud Controller Manager v1.19.3-3 v1.19.4-1 Updated to support the Kubernetes 1.19.4 release. Updated image for [DLA-2424-1](https://www.debian.org/lts/security/2020/dla-2424).
OpenVPN server 2.4.6-r3-IKS-121 2.4.6-r3-IKS-131 Updated image for [CVE-2019-1551](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1551). 
 Operator Lifecycle Manager Catalog v1.5.4 v1.5.6 See the [Operator Lifecycle Manager Catalog release notes](https://github.com/operator-framework/operator-registry/releases/tag/v1.5.6). 
 Ubuntu 18.04 packages 4.15.0-72-generic 4.15.0-74-generic Updated worker node images with package updates for [CVE-2019-13627](https://nvd.nist.gov/vuln/detail/CVE-2019-13627), [CVE-2019-14901](https://nvd.nist.gov/vuln/detail/CVE-2019-14901), [CVE-2019-14896](https://nvd.nist.gov/vuln/detail/CVE-2019-14896), [CVE-2019-14897](https://nvd.nist.gov/vuln/detail/CVE-2019-14897), [CVE-2019-14895](https://nvd.nist.gov/vuln/detail/CVE-2019-14895), [CVE-2019-18660](https://nvd.nist.gov/vuln/detail/CVE-2019-18660), [CVE-2019-19083](https://nvd.nist.gov/vuln/detail/CVE-2019-19083), and [CVE-2019-17006](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17006).
Version 4.4 change log (unsupported as of 31 May 2021) 

Version 4.4 is unsupported. You can review the following archive of the 4.4 change logs.



 Change log for worker node fix pack 4.4.33_1544_openshift, released 24 May 2021 

The following table shows the changes that are in the worker node fix pack 4.4.33_1544_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.4.33_1541_openshift

 Component Previous Current Description 

 HA proxy e0fa2f 26c5cc Updated image with fixes for [CVE-2020-26116](https://nvd.nist.gov/vuln/detail/CVE-2020-26116), [CVE-2020-27619](https://nvd.nist.gov/vuln/detail/CVE-2020-27619), [CVE-2021-23336](https://nvd.nist.gov/vuln/detail/CVE-2021-23336), [CVE-2021-3177](https://nvd.nist.gov/vuln/detail/CVE-2021-3177), [CVE-2019-3842](https://nvd.nist.gov/vuln/detail/CVE-2019-3842), [CVE-2020-13776](https://nvd.nist.gov/vuln/detail/CVE-2020-13776), [CVE-2019-18276](https://nvd.nist.gov/vuln/detail/CVE-2019-18276), [CVE-
Changes since version 1.21.11_1554

 Component Previous Current Description 

 Containerd v1.5.10 v1.5.11 See the [change log](https://github.com/containerd/containerd/releases/tag/v1.5.11) and the [security bulletin](https://www.ibm.com/support/pages/node/6572257). 
 Ubuntu 18.04 packages 4.15.0-173-generic 4.15.0-175-generic Kernel and package updates for [CVE-2018-25032](https://nvd.nist.gov/vuln/detail/CVE-2018-25032)[CVE-2021-3426](https://nvd.nist.gov/vuln/detail/CVE-2021-3426)[CVE-2021-4189](https://nvd.nist.gov/vuln/detail/CVE-2021-4189)[CVE-2022-0391](https://nvd.nist.gov/vuln/detail/CVE-2022-0391)[CVE-2022-21712](https://nvd.nist.gov/vuln/detail/CVE-2022-21712)[CVE-2022-21716](https://nvd.nist.gov/vuln/detail/CVE-2022-21716)[CVE-2022-25308](https://nvd.nist.gov/vuln/detail/CVE-2022-25308)[CVE-2022-25309](https://nvd.nist.gov/vuln/detail/CVE-2022-25309)[CVE-2022-25310](https://nvd.nist.gov/vuln/detail/CVE-2022-25310)[CVE-2022-27666](https://nvd.nist.gov/vuln/detail/CVE-2022-27666).
HAProxy 468c09 04f862 [CVE-2022-1271](https://nvd.nist.gov/vuln/detail/CVE-2022-1271). 
 containerd v1.6.4 v1.6.6 See the [change log](https://github.com/containerd/containerd/releases/tag/v1.6.6), the [security bulletin](https://www.ibm.com/support/pages/node/6597989) for [CVE-2022-31030](https://nvd.nist.gov/vuln/detail/CVE-2022-31030), and the [security bulletin](https://www.ibm.com/support/pages/node/6598049) for [CVE-2022-29162](https://nvd.nist.gov/vuln/detail/CVE-2022-29162). 
 Kubernetes 1.24.1 1.24.2 For more information, see the [change log](https://github.com/kubernetes/kubernetes/releases/tag/v1.24.2). 







 Change log for master fix pack 1.24.1_1523 and worker node fix pack 1.24.1_1522, released 9 June 2022 



Changes since version 1.23.7_1531 (master) and 1.23.7_1532 (worker node)

 Component Previous Current Description 

 Calico v3.21.5 v3.23.1 See the [Calico release notes](https://docs.tigera.io/archive/v3.23/release-notes/). The default BGP configuration found in the default[BGP Configuration](https://docs.tigera.io/calico/latest/reference/resources/bgpconfig) resource has been updated to set nodeMeshMaxRestartTime to 30m. This default change is only applied if the cluster does not have a custom BGP configuration. The previous default value was 120s.
1.4.0_3212_iks, released 12 December 2022 

Initial release of 1.4.0. For more information, see the [community release documentation](https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.4.0).







 Version 1.3.1 (unsupported) 

Version 1.3.1 is no longer supported.



 1.3.1_3807_iks, released 23 February 2023 



* Updates golang version to 1.20.1.
* Resolves [CVE-2022-41723](https://nvd.nist.gov/vuln/detail/CVE-2022-41723)







 1.3.1_3777_iks, released 20 February 2023 



* [CVE-2023-23914](https://nvd.nist.gov/vuln/detail/CVE-2023-23914)
* [CVE-2023-23915](https://nvd.nist.gov/vuln/detail/CVE-2023-23915)
* [CVE-2023-23916](https://nvd.nist.gov/vuln/detail/CVE-2023-23916)







 1.3.1_3754_iks, released 10 February 2023 



* [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304)
* [CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450)
* [CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215)
* [CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286)
Component Previous Current Description 

 Kubernetes v1.15.5 v1.15.6 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.15.6). 
 Ubuntu 16.04 kernel and packages 4.4.0-166-generic 4.4.0-169-generic Updated worker node images with kernel and package updates for [CVE-2018-12207](https://nvd.nist.gov/vuln/detail/CVE-2018-12207), [CVE-2019-0154](https://nvd.nist.gov/vuln/detail/CVE-2019-0154), [CVE-2019-0155](https://nvd.nist.gov/vuln/detail/CVE-2019-0155), [CVE-2019-11135](https://nvd.nist.gov/vuln/detail/CVE-2019-11135), [CVE-2019-15098](https://nvd.nist.gov/vuln/detail/CVE-2019-15098), [CVE-2019-17052](https://nvd.nist.gov/vuln/detail/CVE-2019-17052), [CVE-2019-17053](https://nvd.nist.gov/vuln/detail/CVE-2019-17053), [CVE-2019-17054](https://nvd.nist.gov/vuln/detail/CVE-2019-17054), [CVE-2019-17055](https://nvd.nist.gov/vuln/detail/CVE-2019-17055), [CVE-2019-17056](https://nvd.nist.gov/vuln/detail/CVE-2019-17056), and [CVE-2019-17666](https://nvd.nist.gov/vuln/detail/CVE-2019-17666).
Use the vSphere Web Client to log in to the VCSA.
2. Click Home > Update Manager.
3. On the Objects tab, select an Update Manager instance.
4. Click the Manage tab, click the Host Baselines tab, and then click New Baseline Group.
5. Enter a unique name for the baseline group and click Next.
6. Select a host upgrade baseline to include it in the baseline group.
7. Optionally, create a new host upgrade baseline by clicking Create a new Host Upgrade Baseline on the Upgrades page, and then complete the New Baseline wizard. Click Next.
8. Select the patch baselines that you want to include in the baseline group.
9. Optionally, create a new patch baseline by clicking Create a new Host Patch Baseline on the Patches page, and then complete the New Baseline wizard. Click Next.
10. Select the extension baselines to include in the baseline group.
11. Optionally, create a new extension baseline by clicking Create a new Extension Baseline on the Patches page, and then complete the New Baseline wizard.
12. Review the Ready to Complete page, and then click Finish. The host baseline group is displayed in the Baseline Groups pane.







 Step 2 



1. Create a virtual machine baseline group, containing the VMware Tools Upgrade to Match Host baseline and the VM Hardware Upgrade to Match Host baseline, VUM Administration view.
2. Attach the baseline group to a vCenter container object that contains the virtual machines you want to upgrade.
3. Scan the container object to view the compliance state of the virtual machines in the container. You can start the scan manually or schedule a scan task.
4. Review the scan results displayed in the VUM Client Compliance view.
5. Remediate the non-compliant virtual machines in the container object to make them compliant with the attached baseline group. You can start the remediation manually or schedule a remediation task.



* During an upgrade of VMware Tools, the virtual machines must be powered on.
Component Previous Current Description 

 Containerd v1.4.3 v1.4.4 See the [containerd release notes](https://github.com/containerd/containerd/releases/tag/v1.4.4). The update resolves CVE-2021-21334 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6433475)). 
 Ubuntu 18.04 packages N/A N/A Updated worker node image with package updates for [CVE-2021-21300](https://nvd.nist.gov/vuln/detail/CVE-2021-21300), [CVE-2021-24031](https://nvd.nist.gov/vuln/detail/CVE-2021-24031), [CVE-2021-24032](https://nvd.nist.gov/vuln/detail/CVE-2021-24032), [CVE-2021-27218](https://nvd.nist.gov/vuln/detail/CVE-2021-27218), and [CVE-2021-27219](https://nvd.nist.gov/vuln/detail/CVE-2021-27219). 
 Ubuntu 16.04 packages N/A N/A Updated worker node image with package updates for{: external}, [CVE-2021-21300](https://nvd.nist.gov/vuln/detail/CVE-2021-21300), [CVE-2021-27218](https://nvd.nist.gov/vuln/detail/CVE-2021-27218), [CVE-2021-27219](https://nvd.nist.gov/vuln/detail/CVE-2021-27219), and [CVE-2021-3177](https://nvd.nist.gov/vuln/detail/CVE-2021-3177). 







 Change log for worker node fix pack 1.20.4_1531, released 1 March 2021
Follow the recommendations of SAP Note 90835, which describes the SAP Incident Escalation Procedure. This SAP Note (and others) is found at [https://support.sap.com/en/index.html](https://support.sap.com/en/index.html)





 Before you begin 

Before you deploy SAP S/4HANA High Availability on Single Zone:



* The automation for this deployment requires IBM Cloud File Storage for VPC to complete successfully. IBM Cloud File Storage for VPC is available for customers with special approval to preview this service in the Frankfurt, London, Dallas, Toronto, Washington, Sao Paulo, Sydney, Osaka, and Tokyo regions. Contact your IBM Sales representative to get access. For more information, see [IBM Cloud File Storage for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-about).
* Set up your account to access the VPC. Make sure that your account is [upgraded to a paid account](https://cloud.ibm.com/docs/account?topic=account-accountfaqschangeacct).
* If you have not already, create a bastion server to store the SAP kits. For more information, see [Automate SAP bastion server - SAP media storage repository](https://cloud.ibm.com/docs/sap?topic=sap-sap-bastion-server). You need the floating IP from your bastion server for deployment.
* Download the SAP kits from the SAP Portal to your Deployment Server. Make note of the download locations. Ansible decompresses the files. For more information, see the README file, in the respective GitHub repository for [Schematics](https://github.com/IBM-Cloud/sap-s4hana-sz-ha/tree/main/schematics) and [Terraform](https://github.com/IBM-Cloud/sap-s4hana-sz-ha) and on the About page for the catalog tile.
Red Hat OpenShift on IBM Cloud. 4.11.9 4.11.12 For more information, see the [change log](https://docs.openshift.com/container-platform/4.11/release_notes/ocp-4-11-release-notes.htmlocp-4-11-12). 
 HAProxy b034b2 3a1392 [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434), [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434), [CVE-2020-35525](https://nvd.nist.gov/vuln/detail/CVE-2020-35525), [CVE-2020-35527](https://nvd.nist.gov/vuln/detail/CVE-2020-35527), [CVE-2022-3515](https://nvd.nist.gov/vuln/detail/CVE-2022-3515), [CVE-2022-2509](https://nvd.nist.gov/vuln/detail/CVE-2022-2509). 







 Change log for master fix pack 4.11.8_1528_openshift, released 27 October 2022 

The following table shows the changes that are in the master fix pack 4.11.8_1528_openshift. Master patch updates are applied automatically.



Changes since version 4.11.41523openshift

 Component Previous Current Description 

 Cluster health image v1.3.11 v1.3.12 Updated Go dependencies, golangci-lint, and to Go version 1.19.2. Updated base image version to 109. Excluded ingress status from cluster status calculation. 
 IBM Cloud Controller Manager v1.24.5-1 v1.24.7-1 Updated to support the Kubernetes 1.24.7 release.