vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Key Management Service provider 136 166 Updated image for [CVE-2018-16890](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16890), [CVE-2019-3822](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3822), and [CVE-2019-3823](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3823). 
 Trusted compute agent 5f3d092 a02f765 Updated image for [CVE-2018-10779](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10779), [CVE-2018-12900](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12900), [CVE-2018-17000](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17000), [CVE-2018-19210](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19210), [CVE-2019-6128](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6128), and [CVE-2019-7663](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7663). 







 Change log for 1.13.4_1510, released 4 March 2019 

The following table shows the changes that are in the patch 1.13.4_1510.



Table 1. Changes since version 1.13.2_1509

 Component Previous Current Description
Version 1.1.1_1949_iks is now the default version for all ALBs that run the Kubernetes Ingress image. If you have Ingress auto update enabled, your ALBs automatically update to use this image.



* [CVE-2021-44716](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44716)
* [CVE-2021-44717](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44717)









 Version 1.0.0 

For the community changes for this version of the Kubernetes Ingress image, see the [community Kubernetes change log for ingress-nginx](https://github.com/kubernetes/ingress-nginx/blob/main/Changelog.md100). Refer to the following table for a summary of changes for each build of version 1.0.0 of the Kubernetes Ingress image that IBM Cloud Kubernetes Service releases.



 Version 1.0.3_1995_iks, released on 24 February 2022 



* [CVE-2022-23772](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23772)
* [CVE-2022-23773](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23773)
* [CVE-2022-23806](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23806)







 Version 1.0.3_1933_iks, released on 25 January 2022
* Updates the storage-secret-sidecar image to v1.1.2.
* Improves error messaging if iks_token_exchange_endpoint_private_url is invalid or unreachable.
* Adds [new storage classes for OpenShift Data Foundation](https://cloud.ibm.com/docs/containers?topic=containers-vpc-blockvpc-block-reference).
* Updates to improve the volume attach/detach performance by avoiding unnecessary retries.
* Fixes an issue where mounting failed with already mounted error.
* Improves logging when the device path for a volume is not present on worker node.
* Adds the image label compliance.owner="ibm-armada-storage".







 Change log for version 4.0.0_769, released 16 September 2021 

Review the changes in version 4.0.0_769 of the Block Storage for VPC add-on.



* Image tags: v4.0.0
* Resolves the following CVEs:



* [CVE-2021-27218](https://nvd.nist.gov/vuln/detail/CVE-2021-27218)
* [CVE-2021-3520](https://nvd.nist.gov/vuln/detail/CVE-2021-3520)
* [CVE-2021-20271](https://nvd.nist.gov/vuln/detail/CVE-2021-20271)
* [CVE-2021-3516](https://nvd.nist.gov/vuln/detail/CVE-2021-3516)
* [CVE-2021-3517](https://nvd.nist.gov/vuln/detail/CVE-2021-3517)
* [CVE-2021-3518](https://nvd.nist.gov/vuln/detail/CVE-2021-3518)
* [CVE-2021-3537](https://nvd.nist.gov/vuln/detail/CVE-2021-3537)
* Resolves the following CVEs: [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361), [CVE-2023-24536](https://nvd.nist.gov/vuln/detail/CVE-2023-24536), [CVE-2023-24537](https://nvd.nist.gov/vuln/detail/CVE-2023-24537), [CVE-2023-24538](https://nvd.nist.gov/vuln/detail/CVE-2023-24538).







 Version 4.9.5, release 20 May 2022 



* Support update and scaling on Satellite.
* Golang update.
* Updates the UBI.







 Version 4.9.4, released 13 April 2022 

UBI update.





 Version 4.9.3, released 23 March 2022 



* Updates Golang.
* Updates the UBI.







 Version 4.9.2, released 24 February 2022 

Use PVC for mon on VPC.





 Version 4.9.1, released 23 February 2022 

Updates the UBI.





 Version 4.9.0, released 11 February 2022 

Initial release.







 Version 4.8 



 Version 4.8.31, release 05 May 2023 



* Golang updated to 1.19.8.
Version 1.4 (unsupported) 

Version 1.4 of the managed Istio add-on is unsupported. (: deprecated)





 Change log for 1.4.9, released 18 May 2020 

Review the changes that are in version 1.4.9 of the managed Istio add-on.

Previous version
: 1.4.8

Current version
: 1.4.9

Updates in this version
: See the Istio release notes for [Istio 1.4.9](https://istio.io/latest/news/releases/1.4.x/announcing-1.4.9/).
: Resolves the following CVEs



* [CVE-2019-18348](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18348)
* [CVE-2020-3810](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-3810)
* [CVE-2020-8492](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8492)
* [usn-4359-1](https://ubuntu.com/security/notices/USN-4359-1/)
* [usn-4333-1](https://ubuntu.com/security/notices/USN-4333-1/)



: For more information, see the [Istio security bulletin](https://istio.io/latest/news/security/istio-security-2020-005/)





 Change log for 1.4.8, released 30 April 2020 

Review the changes that are in version 1.4.8 of the managed Istio add-on.

Previous version
: 1.4.7

Current version
: 1.4.8

Updates in this version
* [CVE-2019-3844](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3844)
* [CVE-2019-20386](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20386)
* [CVE-2016-9843](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9843)
* [CVE-2016-9841](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9841)
* [CVE-2016-9842](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9842)
* [usn-4263-1](https://ubuntu.com/security/notices/USN-4263-1/)
* [usn-4249-1](https://ubuntu.com/security/notices/USN-4249-1/)
* [usn-4269-1](https://ubuntu.com/security/notices/USN-4269-1/)
* [usn-4246-1](https://ubuntu.com/security/notices/USN-4246-1/)







 Change log for 1.4.4, released 14 February 2020 

Review the changes that are in version 1.4.4 of the managed Istio add-on.

Previous version
: 1.4.3

Current version
: 1.4.4

Updates in this version
: See the Istio release notes for [Istio 1.4.4](https://istio.io/latest/news/releases/1.4.x/announcing-1.4.4/).
Your vCenter Server instance might be different, and the step-by-step instructions can accommodate different instances.
* A gateway cluster that hosts vSRX firewall appliances.



* The Veeam service is already deployed and uses the bare metal option. However, the VSI instance is similar from a network perspective with two IP addresses; one on the primary subnet and one on the instance management subnet. The VM option has a single IP address only on the instance management subnet.







 High-level steps 

Use the same steps as described in [Cyber-recovery immutable backup high-level steps](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam-cr-sag-overviewveeam-cr-sag-overview-immutbckup-highlvlsteps). In addition, review the following information:



* [Creating the airgap by using Juniper vSRX](https://cloud.ibm.com/docs/vmwaresolutions/?topic=vmwaresolutions-veeam-cr-sag-vsrx) topic describes an approach to create the airgap.
* [Configuring the production environment](https://cloud.ibm.com/docs/vmwaresolutions/?topic=vmwaresolutions-veeam-cr-sag-ireprod) topic describes the tasks on the production environment to enable cyber-recovery access.









 Related links 



* [Cyber recovery with Veeam architecture overview](https://cloud.ibm.com/docs/vmwaresolutions/?topic=vmwaresolutions-veeam-cr-sa-overview)
For more information, see [Procedure to view the virtual data center summary](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_viewing-vdc-summaryshared_viewing-vdc-summary-procedure) or [Procedure to view virtual data center details](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_viewing-vdc-detailsshared_viewing-vdc-details-procedure).



 Procedure to access the Veeam self-service portal from the virtual data center 



1. Under Recommended services on the virtual data center details page, click Veeam backups.
2. Use a user with the Organization Administrator role to log in to the Veeam self-service portal. A newly provisioned virtual data center's admin user has the role by default.



For more information about generating the VMware Cloud Director console credentials, see [Procedure to access the VMware Cloud Director Management console](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_accessing-vcd-consoleshared_accessing-vcd-console-procedure).

Alternatively, click the More menu in the VMware Cloud Director tenant portal and select Data Protection with Veeam.

If you do not see the Data Protection with Veeam option, open an IBM Support ticket by following the steps in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support). In the subject for your issue, include Request Veeam Self Service Portal for my Organization and include your Organization ID and virtual data center name in your issue description.





 Limitations for Veeam Availability Suite 



* For the Veeam application aware image processing and guest file system indexing options to work for Windows® VMs, the most recent VMware® Tools must be installed on the VMs. Linux® VMs do not support application awareness or guest file system indexing.
Install the IBM Hardware Security Module (HSM) client software 

In this step, you'll install Citrix Netscaler VPX with the software and utilities required to interact with the Hardware Security Monitor (HSM).

Steps one and two in this procedure are optional and needed only if the safenet directory and the files or sub-folders in it are missing in the /var path. These resources are necessary to install VPX with the client software and allow it to run the utilities associated with the HSM software.

Find the credentials to access the NetScaler CLI listed in the Control Portal under Devices > Device List > Expand VPX name.

You'll need them for this section and the remainder of the guide.

All VPX commands and outputs in this document will list either netscalername (indicating a shell execution), or > (for the VPX CLI itself).



1. (OPTIONAL) Obtain the safenet_dirs.tar file and transfer it to the VPX in the /var directory. Download the safenet_dirs.tar file in the following locations:



* [Commercial users](http://downloads.service.softlayer.com/citrix/netscaler/Safenet-HSM/)
* [Federal government users](http://downloads.service.usgov.softlayer.com/citrix/netscaler/Safenet-HSM/)



You must be logged into your IBM Cloud account to access the links.

This image shows the WinSCP software transferring the safenet_dir.tar file into the Citrix VPX.
2. (OPTIONAL) Extract the tar file:

root@IBMADC690867-wnzs tar -xvpf safenet_dirs.tar
x safenet/
x safenet/config/
x safenet/gateway/
x safenet/SAClient_600.tgz
x safenet/SAClient_622.tgz
x safenet/install_client.sh
x safenet/gateway/start_safenet_gw
x safenet/gateway/gw_delay
x safenet/config/safenet_config
Version 0.47.0_1614_iks, released on 09 September 2021 

This image is no longer available.



* [CVE-2021-3711](https://nvd.nist.gov/vuln/detail/CVE-2021-3711)
* [CVE-2021-3712](https://nvd.nist.gov/vuln/detail/CVE-2021-3712)







 Version 0.47.0_1578_iks, released on 01 September 2021 

Updates to support arbitrary controller values in the Ingress classes.





 Version 0.47.0_1540_iks, released on 23 August 2021 



* [CVE-2021-36221](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36221)
* [CVE-2021-3121](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3121)







 Version 0.47.0_1480_iks, released on 10 August 2021 



* [CVE-2021-34558](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34558)







 Version 0.47.0_1434_iks, released on 02 August 2021 



* [CVE-2021-3541](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3541)
* [CVE-2021-22925](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22925)
* [CVE-2021-22924](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22924)







 Version 0.47.0_1376_iks, released on 06 July 2021
./ManualRegisterConnector.ps1 -APIClientID {APIClientID} -APIClientSecret {APIClientSecret} -ADDomainName {ADDomainName} -ADServerName {ADServerName} -ActiveDirectoryUserName {ActiveDirectoryUserName} -ActiveDirectoryPassword {ActiveDirectoryPassword} -PreferredDnsServer {PreferredDnsServer}

Replace the contents of the {} with the values for your system.











 Step 3: Access the Active Directory, Cloud Connectors (Optional) 

You can access the Active Directory and Cloud Connectors through a Remote Desktop session. VSI naming conventions are:



* Active Directory: cvad-ad (ex. cvad-vjbxd-ad)
* Cloud Connector: cc- (ex. cc-vjbxd-1, cc-vjbxd-2)
* Custom Image: cstm-img- (ex. cstm-img-vjbxd)



For VSI, make sure that security group that is associated with the instance allows inbound and outbound Remote Desktop Protocol traffic (TCP port 3389). You can remove this rule when you are finished accessing the VSI.

You must create and assign a floating IP to the instance to connect on the public network. For more information, see [About networking](https://cloud.ibm.com/docs/vpc?topic=vpc-about-networking-for-vpc).

For more information about connecting to instances, see [Connecting to Windows instances](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_windows).





 Step 4: Create custom image of virtual machine 

If you do not have an existing custom image, you can create a custom image now.



1. Upload your SSH key from your local machine to the IBM Cloud.
2. Using the UI or Terraform with schematics order your VPC and select add a Custom Image Virtual Machine. Select your SSH key.
3.
Click Import licenses from a previous version.
3. Select the version that contains the licenses that you want to import.
4. Click Import.









 Reviewing your readme file 

When users install the software, they can view product information by clicking the Readme file link. This information is generated from the readme file that you uploaded to your source repository.



1. From the Edit readme tab, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/edit-tagging.svg).
2. Preview how the information in the readme file will be displayed to users when they are installing the software.
3. To make updates, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/edit-tagging.svg) next to the Readme section title.
4. Click Save.
5. Click Next.



If you are importing a virtual server image for VPC, the readme file is not automatically generated. Copy and paste the contents of the [readme file template](https://cloud.ibm.com/media/docs/downloads/software/sw-readme-tab-template.md) and make updates as needed.





 Validating the product 

The steps to validate your product can vary based on the type of software that you're onboarding.



1. From the Validate product tab, configure your validation target, and click Next. This step applies only to Helm charts and Operators.
2. Configure your workspace, and click Next. This step applies only to Helm charts, Operators, Terraform templates, and virtual server images with Terraform.
3. Click Validate.



To monitor the progress of the validation process, click View logs.
1. Leave the default Account for in
2. Leave All resource types for Resource type and click Viewer for Platform Access.
3. Click Add > Assign. The VPC Infrastructure Service policy is assigned to your Service ID.







 Creating an API Key for the Service ID. 

Use the following steps to create an API Key for the new Service ID.



1. Select Service IDs and your newly created Service ID
2. Click the tab Access Policy and verify that the VPC Infrastructure Service is listed as an Access Policy. If not repeat steps 4-9.
3. Click the next tab API keys > Create.
4. Enter a Name and Description for the key and click Create.
5. Click Copy or Download your API key to save it.



Now is the only opportunity to access the API Key data. You cannot view this API key again, so you cannot retrieve it later.







 Installing the IBM Metrics Collector for SAP on Windows 

The IMCS is a service that automatically starts after the installation is and requires an API key. It collects metrics from the metadata of the virtual server, IBM Cloud infrastructure services, runtime data about resources, such as CPU, memory, network, and disk. The metrics are aggregated and displayed through the web server for SAP customers. SAPOSCOL uses the XML output of this web server.

The IMCS uses port 18181 to show the metrics. Make sure that port 18181 is not used by any other application. For more information on how to check port availability, see [Troubleshooting](https://cloud.ibm.com/docs/sap?topic=sap-ibm-metrics-collector-for-sap-windowstroubleshooting-win).

The commands that are listed in this section were run in Windows PowerShell 5.1.

Use the following steps to download the IMCS.



1. [Download the IMCS](ftp://public.dhe.ibm.com/cloud/bluemix/sap/windows).
2. Select the appropriate .zip. In most cases, use the current version. Connect as guest.
[Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 VAPP_VM_METADATA_TO_VCENTER ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Catalog: CLSP Publish Subscribe ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 Catalog: VCSP Publish Subscribe Caching ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 vApp Template: Checkout ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 







 Related links 



* [Setting up user access](https://cloud.ibm.com/docs/account?topic=account-access-getstarted)
* [Inviting users to an account](https://cloud.ibm.com/docs/account?topic=account-iamuserinv)
* [Locating an IAM account administrator](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-iam_verify_permissions)
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.
* [Create or retrieve an IBM Cloud API key](https://cloud.ibm.com/docs/account?topic=account-userapikey&interface=uicreate_user_key). The API key is used to authenticate with the IBM Cloud platform and to determine your permissions for IBM Cloud services.
* [Create or retrieve your SSH key ID](https://cloud.ibm.com/docs/ssh-keys?topic=ssh-keys-getting-started-tutorial). You need the 40-digit UUID for the SSH key, not the SSH key name.
* (Optional - catalog tile) create secrets for your credentials and passwords by using the [Secrets Manager](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-arbitrary-secrets&interface=ui).







 Deploying SAP HA S/4HANA by using Terraform with the bastion server CLI 

Use these steps to configure the IBM Cloud Provider plug-in and use Terraform to install SAP HA S/4HANA on your existing VPC. The scripts can take 1 - 2 hours to complete.



1. Access the bastion server CLI.
2. Clone the solution repository from https://github.com/IBM-Cloud/sap-s4hana-sz-ha and cd to the sap-s4hana-sz-ha/cli/terraform folder.

git clone https://github.com/IBM-Cloud/sap-s4hana-sz-ha.git

cd sap-s4hana-sz-ha/cli/terraform
3. Specify your VPC.
A project is similar to a Kubernetes cluster namespace, and the list is populated from your Red Hat OpenShift environment.
5. Click Next.
6. Configure your IBM Cloud Schematics workspace.
7. Click Next.
8. If applicable, review the license agreements, and select I have read and agree to the following license agreements:.
9. Click Validate.







 OVA image 



1. From the Validate product tab, review the license agreements, and select I have read and agree to the following license agreements:.
2. Click Validate.







 Virtual server image with Terraform 



1. From the Validate product tab, configure your IBM Cloud Schematics workspace.
2. Click Next.
3. If applicable, review the license agreements, and select I have read and agree to the following license agreements:.
4. Click Validate.







 Virtual server image for VPC 



1. From the validate version tab, configure the validation target, and click Next.
2. Optionally, configure your Schematics workspace, and click Next.
3. If applicable, review the license agreements, and select I have read and agree to the following license agreements:.
4. Click Validate.









 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).



1. Click Add controls.
2. Choose a profile.
3. Select the controls that you want to add to your version.
4. Click Add.
5. In the Code Risk Analyzer scan section, click Run scan.
6. Wait for the scan to finish.
7.
* If your IBM Cloud account is running an Activity Tracker Event Routing V2 configuration and you have a CLI V2 plugin installed in your local system, the CLI plugin is set by default in your local system to use the API V2.
* If you have a CLI V2 plugin installed in your local system and you migrate your account from an Activity Tracker Event Routing V1 configuration to an Activity Tracker Event Routing V2 configuration, you must set the API version that the CLI plugin targets in your local system to V2 by running the ibmcloud atracker init version command.







 IAM permissions 

To run the ibmcloud atracker init command, you must have the following [IAM roles](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources):



Table 1. Required IAM roles

 Role Minimum required roles Action 

 atracker.setting.get Administrator <br>Editor <br>Viewer <br>Operator Initialize the API version that the CLI plugin uses. 







 Scenario 1: Before you migrate the Activity Tracker Event Routing configuration 

If you have routes and targets already configured in your IBM Cloud account when the V2 CLI is deployed to your local system, you must run the ibmcloud atracker init version command to revert your local system to use the V1 API until you have [migrated your routes and targets to a V2 configuration.](https://cloud.ibm.com/docs/atracker?topic=atracker-migrate-resources)

Complete the following steps to set the CLI version to V1 so that you can manage an Activity Tracker Event Routing V1 configuration with a CLI V2 plugin:



1. [Install IBM Cloud Activity Tracker Event Routing CLI V2](https://cloud.ibm.com/docs/atracker?topic=atracker-atracker-cli-configatracker-cli-config-install).
2. Check the version of the plugin is set to a V2 version such as 0.2.x.

ibmcloud plugin show --repo atracker
3.