vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Updated Liberty buildpack v3.56-20210412-1223
: The alternate Liberty runtime GA version is changed to the 21.0.0.4 release.



* The alternate Liberty runtime version 21.0.0.4 includes a fix for the [CVE-2021-26296](https://www.ibm.com/support/pages/node/6441433) security vulnerability.
* To specify the monthly runtime set the following two variables:

ibmcloud cf set-env <yourappname> JBP_CONFIG_LIBERTY "version: +"
ibmcloud cf set-env <yourappname> IBM_LIBERTY_MONTHLY true
* For more information see [Use the monthly runtime](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-using_monthly_runtime)
* The default Liberty runtime GA version is the [21.0.0.3](https://openliberty.io/blog/2021/03/19/microprofile-4-21003.html) release.
* The AdoptOpenJDK OpenJ9 alternate JRE (11.0.10_9_openj9-0.24.0) and IBM JRE Version (8 SR6 FP26) remains unchanged.







 19 March 2021 

Updated the ASP.NET Core buildpack v2.10-20210312-1113
: This release includes version 2.3.25 of the dotnet-core Cloud Foundry buildpack.



* Add support for .NET ASP.NET Core 2.1.25
* Add support for .NET ASP.NET Core 2.1.26
* Add support for .NET ASP.NET Core 3.1.12
* Add support for .NET ASP.NET Core 3.1.13
* Add support for .NET ASP.NET Core 5.0.3
* Add support for .NET ASP.NET Core 5.0.4
* Add support for .NET Runtime 2.1.25
* Add support for .NET Runtime 2.1.26
* The IBM JRE version was updated to 8 SR6 FP10.







 4 May 2020 

Updated Liberty buildpack v.3.44-20200430-1451
: The default Liberty runtime version is the [20.0.0.3](https://openliberty.io/blog/2020/03/13/access-specific-kafka-properties-samesite-20003.html) release.



* The alternate Liberty runtime version was changed to 20.0.0.5 release
* The AdoptOpenJDK OpenJ9 alternate JRE was updated to version 11.0.7_10_openj9-0.20.0
* The default Liberty runtime version 20.0.0.3 includes a fix for the [CVE-2020-4303 security vulnerability](https://www.ibm.com/support/pages/node/6147195).







 1 May 2020 

Updated the ASP.NET Core buildpack v2.6-20200424-1047
: This release includes version 2.3.9 of the dotnet-core Cloud Foundry buildpack.



* Add support for .NET ASP.NET Core 2.1.16
* Add support for .NET ASP.NET Core 2.1.17
* Add support for .NET ASP.NET Core 3.1.2
* Add support for .NET ASP.NET Core 3.1.3
* Add support for .NET Runtime 2.1.16
* Add support for .NET Runtime 2.1.17
* Add support for .NET Runtime 3.1.3
* Add support for .NET SDK 2.1.403
* Add support for .NET SDK 2.1.508
* Add support for .NET SDK 2.1.509
* Add support for .NET SDK 2.1.605
* Add support for .NET SDK 2.1.606
* Add support for .NET SDK 2.1.804
* Add support for .NET SDK 2.1.805
* Add support for .NET SDK 3.1.200
System and Services Acquisition (SA) [SA-3 System Development Life Cycle](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-3) <br>[SA-8 Security Engineering Principles](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-8) <br>[SA-10 Developer Configuration Management](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-10) <br>[SA-10 (1) Developer Configuration Management | Software and Firmware Integrity Verification](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-10.1) <br>[SA-11 Developer Security Testing and Evaluation](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-11) <br>[SA-15 Development Process, Standards, and Tools](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-15) <br>[SA-15 (9) Development Process, Standards, and Tools | Use of Live Data](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-sa-15.9) 
 Risk Assessment (RA) [RA-5 Vulnerability Scanning](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ra-5) 







 Next steps 



* [Responsibilities for operating services in your deployment](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-responsibilities)
* The alternate Liberty runtime GA version is the [20.0.0.10](https://openliberty.io/blog/2020/09/25/signed-certificate-with-acme-200010.html) release.
* This buildpack contains a DB2 service fixing:



* Liberty incompatibility issue with updated DB2 paid plans. It will allow users to create the paid plan of the service and bind the application with new VCAP service format.









 2 October 2020 

Updated Liberty buildpack v3.49-20200918-0244
: The default Liberty runtime GA version is the [20.0.0.9](https://openliberty.io/blog/2020/08/28/graphql-apis-open-liberty-20009.html) release.



* The default Liberty runtime version 20.0.0.9 includes a fix for the [CVE-2020-4590 security vulnerability](https://www.ibm.com/support/pages/node/6333623).
* The alternate Liberty runtime GA version is changed to the [20.0.0.10](https://openliberty.io/blog/2020/09/25/signed-certificate-with-acme-200010.html) release.
* AdoptOpenJDK and the IBM JRE Version (8 SR 6 FP15) is unchanged.







 17 September 2020 

Updated the ASP.NET Core buildpack v2.8-20200908-1929
: This release includes version 2.3.13 of the dotnet-core Cloud Foundry buildpack.



* Add support for .NET ASP.NET Core 3.1.8
* Add support for .NET ASP.NET Core 3.1.7
* Add support for .NET ASP.NET Core 2.1.22
* Add support for .NET Runtime 3.1.8
* Add support for .NET Runtime 2.1.22
* Add support for .NET SDK 3.1.402
* Add support for .NET SDK 2.1.810
* Remove support for .NET ASP.NET Core 3.1.4
ibmcloud cf set-env <yourappname> JBP_CONFIG_LIBERTY "version: +"
ibmcloud cf set-env <yourappname> IBM_LIBERTY_MONTHLY true



* The IBM JRE version is changed to 8 SR8 and contains the fixes for the following security vulnerabilities:



* [CVE-2023-35116]
* [CVE-2022-21426](https://www.ibm.com/support/pages/node/6967221)
* All applicable Java SE CVEs published by Oracle in the [January 2023 Critical Patch Update](https://www.oracle.com/security-alerts/cpujan2023.html)



* The IBM Semeru Open J9 alternate JRE remains unchanged ibm-semeru-open-jre_x64_linux_11.0.18_10_openj9-0.36.1



* To specify the alternate JRE set the following variable:

ibmcloud cf set-env myapp JBP_CONFIG_IBMJDK "version: 11.+"









 2 May 2023 

Updated Liberty buildpack v4.0-20230421-1536
: The alternate runtime version is changed to the [23.0.0.4](https://openliberty.io/blog/2023/05/02/23.0.0.4.html) release. The default Liberty runtime is unchanged [23.0.0.3](https://openliberty.io/blog/2023/04/04/23.0.0.3.html).



* This buildpack adds support for the Cloud Foundry stack cflinuxfs4.
* The default and monthly Liberty runtime contain the fix for the following security vulnerability:



* [CVE-2023-24998](https://www.ibm.com/support/pages/node/6982047)



* To specify the monthly runtime set the following two variables and restage your application:
AT&T Vyatta 5600 vRouter software patches (archived) 



* Patch received: January 17, 2020
* Published in documentation: January 27, 2020



This document lists the patches for previously supported versions of the Vyatta Network OS 5600. With versions 5.2 and older, patches are named using an S number.

When multiple CVE numbers are addressed in a single update, the highest CVSS score is listed.

For current patch information for the Vyatta 5600 OS newer than 17.2, refer to [this topic](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-at-t-vyatta-5600-vrouter-software-patches).



 5.2R6S12 

Released June 21, 2018.



 Issues Resolved 



Issues resolved in 5.2R6S12

 Issue Number Priority Summary 

 VRVDR-42084 Blocker Vfp interface marked as “non-dataplane interface” in “show dataplane route” when nat/ipsec config is re-applied 







 Security Vulnerabilities Resolved 



Security vulnerabilities resolved in 5.2R6S12

 Issue Number CVSS score Advisory Summary 

 VRVDR-42317 5.4 DSA-4226-1 CVE-2018-12015: Debian DSA-4226-1: perl – security update 
 VRVDR-42284 7.5 DSA-4222-1 CVE-2018-12020: Debian DSA-4222-1: gnupg2 – security update 
 VRVDR-41797 8 DSA-4196-1 CVE-2018-1087, CVE-2018-8897: Debian DSA-4196-1: linux – security update 
 VRVDR-41680 7.8 DSA-4188-1 Debian DSA-4188-1: linux – security update (Spectre) 









 5.2R6S11 

Released June 11, 2018



 Issues Resolved 



Issues resolved in 5.2R6S11

 Issue Number Priority Summary
* [Security Bulletin: Vulnerability in Apache Log4j may affect IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data (CVE-2021-4428)](https://www.ibm.com/support/pages/node/6536732)







 20 December 2021 (Version 1.2.x) 

Important: You can no longer install Speech to Text version 1.2.x on IBM Cloud Pak for Data version 3.5
: Important: You can no longer perform new installations of Speech to Text version 1.2.x on IBM Cloud Pak for Data version 3.5. You can install only Speech to Text version 4.0.x on IBM Cloud Pak for Data version 4.x. For more information, see [Installing Watson Speech to Text](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=text-installing-watson-speech).

The Speech services for IBM Cloud Pak for Data version 3.5 reach their End of Support date on 30 April 2022. You are encouraged to upgrade to the latest version 4.0.x release of the services at your earliest convenience. For more information, see [Upgrading Watson Speech to Text](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=text-upgrading-watson-speech).





 30 November 2021 (Version 4.0.3) 

Version 4.0.3 is now available
: Speech to Text for IBM Cloud Pak for Data version 4.0.3 is now available. This version supports IBM Cloud Pak for Data version 4.x and Red Hat OpenShift versions 4.6 and 4.8. For more information about installing and managing the service, see [Installing Watson Speech to Text](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=text-installing-watson-speech).

License Server now a mandatory prerequisite
: You must now install the License Server from the IBM Cloud Pak for Data foundational services.
The default Liberty runtime is unchanged [23.0.0.3](https://openliberty.io/blog/2023/04/04/23.0.0.3.html).



* This buildpack adds support for the Cloud Foundry stack cflinuxfs4.
* The default and monthly Liberty runtime contain the fix for the following security vulnerability:



* [CVE-2023-24998](https://www.ibm.com/support/pages/node/6982047)



* To specify the monthly runtime set the following two variables and restage your application:



ibmcloud cf set-env <yourappname> JBP_CONFIG_LIBERTY "version: +"
ibmcloud cf set-env <yourappname> IBM_LIBERTY_MONTHLY true



* The IBM JRE version remains unchanged 8 SR7 FP20.
* The IBM Semeru Open J9 alternate JRE remains unchanged ibm-semeru-open-jre_x64_linux_11.0.18_10_openj9-0.36.1



* To specify the alternate JRE set the following variable:

ibmcloud cf set-env myapp JBP_CONFIG_IBMJDK "version: 11.+"









 4 April 2023 

Updated Liberty buildpack v3.80-20230321-1018
: The alternate and default Liberty runtime version is changed to the 23.0.0.3 release.



* The IBM JRE version remains unchanged 8 SR7 FP20.
* The IBM Semeru Open J9 alternate JRE remains unchanged ibm-semeru-open-jre_x64_linux_11.0.18_10_openj9-0.36.1



* To specify the alternate JRE set the following variable:

ibmcloud cf set-env myapp JBP_CONFIG_IBMJDK "version: 11.+"









 7 March 2023 

Updated Liberty buildpack v3.79-20230223-2310
* Remove support for .NET ASP.NET Core 2.1.16
* Remove support for .NET Runtime 2.1.16
* Remove support for .NET SDK 2.1.804
* Remove support for .NET SDK 3.1.200
* Update Node.js version to 10.21.0







 8 June 2020 

Updated Node.js buildpack v4.3-20200606-1928
: The SDK for Node.js buildpack v4.3 provides Node.js community runtime versions v10.20.1, v10.21.0, v12.17.0, v12.18.0. The default is latest 10.x, so it is currently 10.21.0. This buildpack is based on the community node.js buildpack [v1.7.20](https://github.com/cloudfoundry/nodejs-buildpack/tree/v1.7.20).

This release also includes CVE-2020-8172, CVE-2020-11080, CVE-2020-8174 and CVE-2020-10531: [June 2020 Security Releases](https://nodejs.org/en/blog/vulnerability/june-2020-security-releases/)





 5 June 2020 

Updated Liberty buildpack v3.45-20200601-1056
: The default Liberty runtime GA version is the [20.0.0.6](https://openliberty.io/blog/2020/06/05/graphql-open-liberty-20006.html) release.



* The alternate Liberty runtime GA version was changed to 20.0.0.6 release
* The IBM JRE version was updated to 8 SR6 FP10.







 4 May 2020 

Updated Liberty buildpack v.3.44-20200430-1451
: The default Liberty runtime version is the [20.0.0.3](https://openliberty.io/blog/2020/03/13/access-specific-kafka-properties-samesite-20003.html) release.
The release removes support for older runtime versions as announced in [IBM Cloud Node.js Buildpack v3.3 – FIPS mode and more](https://www.ibm.com/blogs/cloud-archive/2016/05/node-buildpack-update-fips-mode/). The buildpack now supports 0.10.44, 0.10.45, 0.12.13, 0.12.14, 4.4.4, 4.4.5, 6.1.0, and 6.2.0.

This release includes bug fixes from the [Cloud Foundry’s Node.js buildpack 1.5.14](https://github.com/cloudfoundry/nodejs-buildpack/tree/v1.5.14).





 17 June 2016 

Updated Liberty buildpack v3.0-20160608-1450
: The buildpack now contains two versions of WebSphere Liberty, the latest stable release and the latest monthly release. Specifically, it provides [16.0.0.2](https://www.ibm.com/support/pages/node/281685) stable release and [2016.6.0.0](https://developer.ibm.com/wasdev/blog/2016/06/03/beta-websphere-liberty-and-tools-june-2016/) monthly release. The stable release will be used by default. See [Liberty versions](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-buildpack_defautsliberty_versions) for additional details.



* The buildpack also contains security fixes for the [Apache Standard Taglibs vulnerability](https://www.ibm.com/support/pages/node/282471).







 10 June 2016 

Updated ASP.NET Core buildpack v0.8.1-20160526-0957
: This version of the buildpack includes the following changes:



* The runtime's name is changed from ASP.NET 5 to ASP.NET Core.
* The buildpack version number is included in detect script output.
IBM Cloud Foundry [end-of-marketing is 30 November 2022](https://ibm.biz/ibmcf-announce). On 30 November 2022 all new IBM Cloud users are blocked from deploying Cloud Foundry applications. Existing users that already have Cloud Foundry applications deployed can continue to deploy new applications and use their applications until the [end-of-support date.](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_timeline)





 25 October 2022 

Updated Liberty buildpack v3.75-20221012-1015
: The alternate Liberty runtime version is changed to the 22.0.0.11 release. The default runtime remains the same [22.0.0.9](https://openliberty.io/blog/2022/08/30/password-utilities-22009.html)){: external}.



* The default and monthly Liberty runtime contain the fix for the following security vulnerability:



* [CVE-2022-24839](https://www.ibm.com/support/pages/node/6824871)



* To specify the monthly runtime set the following two variables and restage your application:

ibmcloud cf set-env <yourappname> JBP_CONFIG_LIBERTY "version: +"
ibmcloud cf set-env <yourappname> IBM_LIBERTY_MONTHLY true
* The IBM Semeru Open J9 alternate JRE remains unchanged ibm-semeru-open-jre_x64_linux_11.0.16.1_1_openj9-0.33.1



* To specify the alternate JRE set the following variable:

ibmcloud cf set-env myapp JBP_CONFIG_IBMJDK "version: 11.+"



* The IBM JRE version is changed to 8 SR7 FP16.







 27 September 2022 

Updated Liberty buildpack v3.74-20220913-1224
: The alternate Liberty runtime version is changed to the 22.0.0.10 release.
* The IBM Semeru Open J9 alternate JRE remains unchanged ibm-semeru-open-jre_x64_linux_11.0.18_10_openj9-0.36.1



* To specify the alternate JRE set the following variable:

ibmcloud cf set-env myapp JBP_CONFIG_IBMJDK "version: 11.+"









 7 March 2023 

Updated Liberty buildpack v3.79-20230223-2310
: The alternate Liberty runtime version is changed to [23.0.0.2](https://openliberty.io/blog/2023/03/07/23.0.0.2.html). The default Liberty runtime is unchanged [22.0.0.12](https://openliberty.io/blog/2022/11/22/22.0.0.12.html).



* The alternate Liberty runtime contains the fix for the following security vulnerability:



* [CVE-2022-46364](https://www.ibm.com/support/pages/node/6953767)



* To specify the monthly runtime set the following two variables and restage your application:

ibmcloud cf set-env <yourappname> JBP_CONFIG_LIBERTY "version: +"
ibmcloud cf set-env <yourappname> IBM_LIBERTY_MONTHLY true
* The IBM JRE version remains unchanged 8 SR7 FP20.
* The IBM Semeru Open J9 alternate JRE is changed to ibm-semeru-open-jre_x64_linux_11.0.18_10_openj9-0.36.1



* To specify the alternate JRE set the following variable:

ibmcloud cf set-env myapp JBP_CONFIG_IBMJDK "version: 11.+"









 7 February 2023 

Updated Liberty buildpack v3.78-20230124-2119
: The alternate Liberty runtime version is changed to 23.0.0.1.
![Continuous integration pipeline success](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/ds_kub_explore_ci_pipeline_success.png)

Figure 11. Continuous integration pipeline success



 Shift left practice 

In the secure app development world, shift left is a practice that prevents and finds issues such as defects and security vulnerabilities and runs compliance checks early in the software delivery process. Shift left includes the following practices:



* Run checks that can be run on the code or the repo itself and do not need the built image, as early as possible. These checks prevent noncompliant code from being merged into the master branch of the repo. Because evidence is not collected from the pull request pipeline, its goal is to shift compliance checks as far left as possible.
* All checks are run in every pipeline run. If a previous check fails, the pipeline progresses to the next check. To evaluate if you have any failures in your run, check the final step of your pipeline that has a pipeline evaluator.



Results from unit tests and vulnerability scans are published to the DevOps Insights instance within the toolchain. To review these results, click the DevOps Insights tile within the toolchain and go to the Quality Dashboard page.

Zoom

![Toolchain continuous integration results](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/ds_kub_explore_ci_test_results_DOI.png)

Figure 12. Toolchain continuous integration results

To evaluate if you have any failures in your pipeline run, check the final step of your pipeline, which has a pipeline evaluator.







 Explore the continuous delivery pipeline 

The pull request and continuous integration pipelines are common across all of the deployment strategies.
These checks prevent noncompliant code from being merged into the master branch of the repo. Because evidence is not collected from the pull request pipeline, its goal is to shift compliance checks as far left as possible.
* All checks are run in every pipeline run. If a previous check fails, the pipeline progresses to the next check. To evaluate if you have any failures in your run, check the final step of your pipeline that has a pipeline evaluator.



Results from unit tests and vulnerability scans are published to the DevOps Insights instance within the toolchain. To review these results, click the DevOps Insights tile within the toolchain and go to the Quality Dashboard page.

To evaluate if you have any failures in your pipeline run, check the final step of your pipeline, which has a pipeline evaluator.







 Explore the continuous delivery pipeline 

The pull request and continuous integration pipelines are common across all of the deployment strategies. The continuous delivery pipeline design and implementation changes are based on the deployment strategy that you previously selected in this tutorial.

You can start a continuous delivery pipeline in either of the following ways:



* Trigger the continuous delivery pipeline manually.
* Automatically trigger the continuous delivery pipeline after each Merge action in the Inventory repo. After the merge, you must manually trigger the continuous deliver pipeline run.



A Git Repos and Issue Tracking trigger is set up to trigger an automatic continuous delivery pipeline, but it is disabled by default. You can enable this trigger after the first time that you promote a change.

Zoom

![Continuous delivery pipeline triggers for rolling deployment](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/sat_cd_pipeline_triggers_rolling.png)

Figure 11. Triggers in continuous delivery pipeline for rolling deployment







 Next steps 

If you want to remove the sample app that is running on Kubernetes, you must clean the Kubernetes cluster:



1.
Build and push the image again:



1. Build the image again by running the following command:

docker build -t us.icr.io/<my_namespace>/hello-world:2 -f Dockerfile-vulnerable .
2. Push the image again by running the following command:

docker push us.icr.io/<my_namespace>/hello-world:2



3. Wait for the scan to complete and then run the following command to ensure that no issues are present in the image:

ibmcloud cr images --va
4. To patch the deployment, run the following command:

kubectl apply -f hello-world.yaml
5. Wait for the deployment to complete. To check whether the deployment is complete, run the following command:

kubectl rollout status deployment hello-world

This deployment succeeds, and you can access your service and see "Hello, world!" displayed.
6. Delete the deployment and the service before proceeding:

kubectl delete -f hello-world.yaml









 Step 3: Deploying to nondefault Kubernetes namespaces 

An IBM Cloud Kubernetes Service cluster can automatically pull images from IBM Cloud Container Registry to the default Kubernetes namespace. However, if you want to deploy to namespaces other than default, you must take extra steps.

Kubernetes and IBM Cloud Container Registry namespaces are different. For more information about IBM Cloud Container Registry namespaces, see [Registry namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_namespace). For more information about Kubernetes namespaces, see [Namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/).



1. In your cluster, create a Kubernetes namespace called test:

kubectl create namespace test
2.