vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Kubernetes v1.20.6 v1.20.7 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.20.7). 
 Ubuntu 18.04 packages 4.15.0-142 4.15.0-143 Updated worker node images with kernel package updates for [CVE-2021-28688](https://nvd.nist.gov/vuln/detail/CVE-2021-28688), [CVE-2021-20292](https://nvd.nist.gov/vuln/detail/CVE-2021-20292), [CVE-2021-29264](https://nvd.nist.gov/vuln/detail/CVE-2021-29264), [CVE-2021-29265](https://nvd.nist.gov/vuln/detail/CVE-2021-29265), and [CVE-2021-29650](https://nvd.nist.gov/vuln/detail/CVE-2021-29650). 
 Ubuntu 16.04 packages N/A N/A Updated worker node images with package updates for [CVE-2009-5155](https://nvd.nist.gov/vuln/detail/CVE-2009-5155) and [CVE-2020-6096](https://nvd.nist.gov/vuln/detail/CVE-2020-6096). 







 Change log for master fix pack 1.20.7_1540, released 24 May 2021 

The following table shows the changes that are in the master fix pack patch update 1.20.7_1540. Master patch updates are applied automatically.



Changes since version 1.20.6_1538

 Component Previous Current Description 

 Cluster health image v1.2.11 v1.2.12 Improved the add-on status information that is displayed when errors occur.
Operator Lifecycle Manager 0.12.0 0.13.0 See the [Operator Lifecycle Manager release notes](https://github.com/operator-framework/operator-lifecycle-manager/releases/tag/0.13.0). 







 Change log for worker node fix pack 1.16.3_1519, released 9 December 2019 

The following table shows the changes that are in the worker node fix pack 1.16.3_1519.



Changes since version 1.16.3_1518

 Component Previous Current Description 

 containerd v1.3.1 v1.3.2 See the [containerd release notes](https://github.com/containerd/containerd/releases/tag/v1.3.2). 
 Ubuntu 16.04 kernel and packages 4.4.0-169-generic 4.4.0-170-generic Updated worker node images with kernel and package updates for [CVE-2018-20784](https://nvd.nist.gov/vuln/detail/CVE-2018-20784), [CVE-2019-16168](https://nvd.nist.gov/vuln/detail/CVE-2019-16168), and [CVE-2019-5827](https://nvd.nist.gov/vuln/detail/CVE-2019-5827).
Kubernetes 1.23.15 1.23.16 For more information, see the [change log](https://github.com/kubernetes/kubernetes/releases/tag/v1.23.16). 
 HAPROXY 508bf6 8d6ea6 [CVE-2022-42010](https://nvd.nist.gov/vuln/detail/CVE-2022-42010), [CVE-2022-42011](https://nvd.nist.gov/vuln/detail/CVE-2022-42011), [CVE-2022-42012](https://nvd.nist.gov/vuln/detail/CVE-2022-42012), [CVE-2022-40303](https://nvd.nist.gov/vuln/detail/CVE-2022-40303), [CVE-2022-40304](https://nvd.nist.gov/vuln/detail/CVE-2022-40304), [CVE-2022-3821](https://nvd.nist.gov/vuln/detail/CVE-2022-3821), [CVE-2022-35737](https://nvd.nist.gov/vuln/detail/CVE-2022-35737), [CVE-2022-43680](https://nvd.nist.gov/vuln/detail/CVE-2022-43680), [CVE-2021-46848](https://nvd.nist.gov/vuln/detail/CVE-2021-46848). 







 Change log for worker node fix pack 1.23.15_1558, released 16 January 2023 

The following table shows the changes that are in the worker node fix pack 1.23.15_1558. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.
* Updates the UBI to version 8.7-1085.
* Updates Go to version 1.19.6.







 Revision 17, released 20 February 2023 



* Resolves the following CVEs: [CVE-2022-47629](https://nvd.nist.gov/vuln/detail/CVE-2022-47629)
* Updates the UBI to version 8.7-1049.1675784874.
* Updates Go to version 1.18.9.
* Updates the tridentctl pod as to run as non-root.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Project reclamation
: Updated project delete command to include information about project reclamation. See [Delete a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-projectdelete-project).





 4 March 2021 

Review the release notes for 4 March 2021.

Added Code Engine architecture and workload isolation documentation.
: See [Learning about Code Engine architecture and workload isolation](https://cloud.ibm.com/docs/codeengine?topic=codeengine-architecture).

Added HTTP headers and body information for subscriptions.
: See [HTTP headers and body information for IBM Cloud Object Storage events](https://cloud.ibm.com/docs/codeengine?topic=codeengine-eventing-cosevent-producersub-header-body-cos) and [HTTP headers and body information for Ping events](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronsub-header-body-cron).

System events
: Added information about viewing system events to troubleshooting information for apps and jobs. See [system event information for apps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-appsts-app-gettingevent) and [system event information for job runs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-jobts-job-gettingevent).

Updated versions for buildpacks.
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).





 2 March 2021 

Review the release notes for 2 March 2021.

CLI version 0.5.20 released.
Using the deprecated status can discourage use of the image before the status changes to obsolete.<br> * obsolete: The image is not available to use to provision an instance.<br> * Schedule complete lifecycle: You can schedule both the deprecated and obsolete status changes at the same time.<br><br><br><br>You can move back and forth between the three statuses. Only the statuses you can change to are displayed. You can schedule status changes by using calendar date and time or number of days. The obsolescence date must always be after the deprecation date. 







 Importing a custom image by using the CLI 

Make sure that your compatible custom image is available in IBM Cloud Object Storage. For more information, see [Creating a Linux custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-create-linux-custom-image), [Creating a Windows custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-create-windows-custom-image), [Bring your own license](https://cloud.ibm.com/docs/vpc?topic=vpc-byol-vpc-about) and [Uploading data](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-upload) to IBM Cloud Object Storage.

When you have an image available in IBM Cloud Object Storage, you can import it to IBM Cloud VPC infrastructure by using the command-line interface (CLI).

To import a custom image by using the CLI, use the ibmcloud is image-create command. Specify the name of the custom image to be created by using the IMAGE_NAME variable. You must also specify the source; for example, specify the --file option with the image file location. Specify the --os-name option with the name of the operating system for the image.

ibmcloud is image-create IMAGE_NAME [--file IMAGE_FILE_LOCATION] [--os-name OPERATING_SYSTEM_NAME]
ibmcloud is image-update IMAGE --name NEW_NAME [--deprecate-at DEPRECATE_AT | --reset-deprecate-at] [--obsolete-at OBSOLETE_AT | --reset-obsolete-at] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is image-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --name my-image
* ibmcloud is image-update my-image-from-volume-cli --name my-image-from-volume-cli-do-not-delete --obsolete-at "2023-03-02T04:20:00+05:30"
* ibmcloud is image-update my-image-from-volume-cli-do-not-delete --deprecate-at "2023-03-03T04:20:00+05:30"
* ibmcloud is image-update my-image-from-volume-cli-do-not-delete --reset-deprecate-at
* ibmcloud is image-update my-image-from-volume-cli-do-not-delete --reset-obsolete-at







 Command options 



* IMAGE: ID or name of the image.
* --name: New name of the image.
* --deprecate-at: The deprecation date and time to set for this image. The date and time must not be in the past, and must be earlier than "obsolete_at". Date and time must be in ISO 8601 format: 2024-03-05T15:31:50.701Z or 2024-03-05T15:31:50.701+8:00.
* --reset-deprecate-at: Specify this flag to remove an existing deprecation date and time. If the image status is "deprecated", it becomes "available".
* --obsolete-at: The obsolescence date and time to set for this image.
curl -X PATCH "$vpc_api_endpoint/v1/images/$image_id?version=2022-11-21&generation=2" -H "Authorization: Bearer $iam_token" -d '{ “obsolescence_at": null }'
* To change an image that has both the deprecation_at or obsolescence_at properties set back to available, you must update both the deprecation_at or obsolescence_at properties.

curl -X PATCH "$vpc_api_endpoint/v1/images/$image_id?version=2022-11-21&generation=2" -H "Authorization: Bearer $iam_token" -d '{ "deprecation_at": null, “obsolescence_at": null }'
curl -X PATCH "$vpc_api_endpoint/v1/images/$image_id?version=2022-11-21&generation=2" -H "Authorization: Bearer $iam_token" -d '{
“obsolescence_at": "2023-12-31T06:11:28+05:30" }'

If you want to change the deprecation_at and obsolescence_at date and time entries, you can run these commands again. The previous dates and times are replaced with the new dates and times.







 Remove previously scheduled custom image lifecycle status by using the API 

Make a PATCH /images request to remove any scheduled status change by updating deprecation_at or obsolescence_at to null. This property change removes the date and time from the image and the image is no longer scheduled for that status change.



* To change an image from deprecated to available, change the deprecation_at property to null.

curl -X PATCH "$vpc_api_endpoint/v1/images/$image_id?version=2022-11-21&generation=2" -H "Authorization: Bearer $iam_token" -d '{ "deprecation_at": null }'
* To change an image from obsolete to its previous state, change obsolescence_at to null. If the image previously contained a value other than null for deprecation_at, then this property change removes the obsolete state and changes it back to deprecated. If the previous state was available, meaning the image was moved from available directly to obsolete, then this property change moves from obsolete back to available.

curl -X PATCH "$vpc_api_endpoint/v1/images/$image_id?version=2022-11-21&generation=2" -H "Authorization: Bearer $iam_token" -d '{ “obsolescence_at": null }'
* To change an image that has both the deprecation_at or obsolescence_at properties set back to available, you must update both the deprecation_at or obsolescence_at properties.
If you use both the --reset-deprecate-at and --reset-obsolete-at options, the image status returns to available.





 Change the custom image lifecycle status by using the API 

You can change the lifecycle status of an IBM Cloud VPC custom image by using the application programming interface (API). You can make an immediate status change or schedule a status change to happen later.

To make an immediate status change, use one of the following examples. For the$image_id variable, specify the ID of the custom image for the status change.

You can make an immediate status change only if a future status change is not scheduled. To remove a scheduled status change, see [Remove a scheduled custom image lifecycle status change by using the API](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-custom-images&interface=uischedule-ilm-reset-status-change-API). After you remove the scheduled status change, you can make an immediate status change.



* Change image lifecycle status to deprecated.

curl -X POST "$vpc_api_endpoint/v1/images/$image_id/deprecate?version=2023-02-21&generation=2" -H “Authorization: Bearer $iam_token”
* Change the image lifecycle status to obsolete.

curl -X POST "$vpc_api_endpoint/v1/images/$image_id/obsolete?version=2023-12-21&generation=2" -H “Authorization: Bearer $iam_token”



To schedule a status change, use one of the following examples.

For the deprecation_at or obsolescence_at properties, specify a date in the ISO 8601 (YYYY-MM-DDThh:mm:ss+hh:mm) date and time format.



* YYYY is the four digit year
* MM is the two digit month
* DD is the two digit day
* T separates the date and time information
* hh is the two digit hours
* mm is the two digit minutes
If you define both the deprecation_at and obsolescence_at dates and times, the obsolescence_at date must be after the deprecation_at date and time.

The following example imports a custom image with the name of my-image, source location of cos://us-south/my-bucket/my-image.qcow2, and the operating system for the image is debian-9-amd64. The image is scheduled to be deprecated on 2023-03-01T06:11:28+05:30. The image is scheduled to be obsolete on 2023-12-31T06:11:28+05:30.

curl -X POST "$vpc_api_endpoint/v1/images?version=2023-02-21&generation=2" -H "Authorization: Bearer $iam_token" -d '{
"name": "my-image",
"file": {
"href": "cos://us-south/my-bucket/my-image.qcow2"
},
"operating_system": {
"name": "debian-9-amd64"
},
"deprecation_at": "2023-03-01T06:11:28+05:30",
"obsolescence_at": "2023-12-31T06:11:28+05:30"
}'







 Validating an imported custom image by using the UI 

After you import a custom image, you can view the checksum that was generated for the image when it is imported to IBM Cloud VPC.

If you generate a checksum locally for your image before you import it, you can compare the two checksums to make sure that they are identical. Matching checksums indicate that the image is unaltered.



1. In [IBM Cloud console](https://cloud.ibm.com/login), go to Menu icon !
Specify the name of the custom image to be created by using the IMAGE_NAME variable. You must also specify the source; for example, specify the --file option with the image file location. Specify the --os-name option with the name of the operating system for the image.

To schedule the deprecate-at or obsolete-at properties, specify a date in the ISO 8601 (YYYY-MM-DDThh:mm:ss+hh:mm) date and time format.



* YYYY is the four digit year
* MM is the two digit month
* DD is the two digit day
* T separates the date and time information
* hh is the two digit hours
* mm is the two digit minutes
* +hh:mm or -hh:mm is the UTC time zone



Thus, the date of 30 September 2023 at 8:00 p.m. in the North American Central Standard Time Zone (CST) would be 2023-09-30T20:00:00-06:00

When scheduling the date and time, you can't use your current date and time. For example, if it is 8 a.m. on June 12, then the scheduled date and time must be after 8 a.m. on June 12. If you define both the deprecate-at and obsolete-at dates and times, the deprecate-at date must be after the obsolete-at date and time.

ibmcloud is image-create IMAGE_NAME [--file IMAGE_FILE_LOCATION] [--os-name OPERATING_SYSTEM_NAME] [--deprecate-at YYYY-MM-DDThh:mm:ss+hh:mm] [--obsolete-at YYYY-MM-DDThh:mm:ss+hh:mm]

The following example creates a custom image with the name of my-ubuntu-16-amd64. The image source location is cos://us-south/custom-image-vpc-bucket/customImage-0.qcow2. The operating system is ubuntu-16-amd64.
If you use both the --reset-deprecate-at and --reset-obsolete-at options, the image status returns to available.





 Change the custom image lifecycle status by using the API 

You can change the lifecycle status of an IBM Cloud VPC custom image by using the application programming interface (API). You can make an immediate status change or schedule a status change to happen later.

To make an immediate status change, use one of the following examples. For the$image_id variable, specify the ID of the custom image for the status change.

You can make an immediate status change only if a future status change is not scheduled. To remove a scheduled status change, see [Remove a scheduled custom image lifecycle status change by using the API](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-custom-imagesschedule-ilm-reset-status-change-API). After you remove the scheduled status change, you can make an immediate status change.



* Change image lifecycle status to deprecated.

curl -X POST "$vpc_api_endpoint/v1/images/$image_id/deprecate?version=2023-02-21&generation=2" -H “Authorization: Bearer $iam_token”
* Change the image lifecycle status to obsolete.

curl -X POST "$vpc_api_endpoint/v1/images/$image_id/obsolete?version=2023-12-21&generation=2" -H “Authorization: Bearer $iam_token”



To schedule a status change, use one of the following examples.

For the deprecation_at or obsolescence_at properties, specify a date in the ISO 8601 (YYYY-MM-DDThh:mm:ss+hh:mm) date and time format.



* YYYY is the four digit year
* MM is the two digit month
* DD is the two digit day
* T separates the date and time information
* hh is the two digit hours
* mm is the two digit minutes
* +hh:mm or -hh:mm is the UTC time zone
Date and time must be in ISO 8601 format: 2024-03-05T15:31:50.701Z or 2024-03-05T15:31:50.701+8:00.
* --reset-deprecate-at: Specify this flag to remove an existing deprecation date and time. If the image status is "deprecated", it becomes "available".
* --obsolete-at: The obsolescence date and time to set for this image. The date and time must not be in the past, and must be later than "deprecate_at". Date and time must be in ISO 8601 format: 2024-03-05T15:31:50.701Z or 2024-03-05T15:31:50.701+8:00.
* --reset-obsolete-at: Specify this flag to remove an existing obsolescence date and time. If the image status is "obsolete", it becomes "deprecated" if "deprecate_at" is in the past. Otherwise, it becomes "available".
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is image-delete 

Delete one or more images.

ibmcloud is image-delete (IMAGE1 IMAGE2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command options 



* IMAGE1: ID or name of the image.
* IMAGE2: ID or name of the image.
* --output: Specify output format, only JSON is supported. One of: JSON.
* --force, -f: Force the operation without confirmation.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is image-export-job
For accounts that have been granted special approval to preview the image lifecycle management feature, the deprecated_at and obsoleted_at properties for [images](https://cloud.ibm.com/apidocs/vpc-betacreate-image) requests have been renamed deprecation_at and obsolescence_at, respectively. Original property names deprecated_at and obsoleted_at will continue to be supported until the feature becomes generally available. Requests that specify the original and revised property names simultaneously will be rejected.

This feature is now generally available. Support for property names deprecated_at and obsoleted_at has been removed. See the [VPC API change log](https://cloud.ibm.com/docs/vpc?topic=vpc-api-change-log11-july-2023).







 30 May 2023 



 For version 2023-05-30 or later 

This release introduces the following features for users with accounts that have access to file shares.

File shares property and request path name changes. When making API requests using a version query parameter of 2023-05-30 or later, the shares targets property has been changed to mount_targets. This change applies when [creating](https://cloud.ibm.com/apidocs/vpc-betacreate-share), [updating](https://cloud.ibm.com/apidocs/vpc-betaupdate-share), [listing](https://cloud.ibm.com/apidocs/vpc-betalist-shares), and [retrieving](https://cloud.ibm.com/apidocs/vpc-betaget-share) a file share, and when [listing all mount targets for a file share](https://cloud.ibm.com/apidocs/vpc-betalist-share-mount-targets).

The name change also applies to the method paths: Requests using a version query parameter of 2023-05-30 or later must use /shares/{share_id}/mount_targets (instead of /shares/{share_id}/targets) in the request URL.
Specify the source.volume subproperty to indicate the source of the image from volume.To schedule the deprecation_at or obsolescence_at properties, specify a date in the ISO 8601 (YYYY-MM-DDThh:mm:ss+hh:mm) date and time format.<-- <ul> --> * YYYY is the four digit year * MM is the two digit month * DD is the two digit day * T separates the date and time information * hh is the two digit hours * mm is the two digit minutes * +hh:mm or -hh:mm is the UTC time zone<-- </ul> -->Thus, the date of 30 September 2023 at 8:00 p.m. in the North American Central Standard Time Zone (CST) would be 2023-09-30T20:00:00-06:00When scheduling the date and time, you can't use your current date and time. For example, if it is 8 a.m. on June 12, then the scheduled date and time must be after 8 a.m. on June 12. If you define both the deprecation_at and obsolescence_at dates and times, the obsolescence_at date must be after the deprecation_at date and time. curl -X POST "$vpc_api_endpoint/v1/images?version=2023-02-21&generation=2" -H "Authorization: Bearer $iam_token" -d '{
"name": "test-ifv-boot-volume",
"source_volume": {
"id": "4fec84ef-baf9-405d-bf3b-9d5a60e068f7"
},
"deprecation_at": "2023-03-01T06:11:28+05:30",
"obsolescence_at": "2023-12-31T06:11:28+05:30"
}'
If you can't pull the most recent image by using the latest tag, see [Why can't I pull the newest image by using the latest tag?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-docker-latest) for assistance.
* If you are using Podman, run the following command.

podman pull <source_image>:<tag>

Example, where <source_image> is hello-world and <tag> is latest:

podman pull hello-world:latest









 Step 4: Tag the image 

To tag the image, replace <source_image> with the repository and <tag> with the tag of your local image that you pulled earlier. Replace <region> with the name of your [region](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions). Replace <my_namespace> with the namespace that you created in [Set up a namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-startedgs_registry_namespace_add). Define the repository and tag of the image that you want to use in your namespace by replacing <new_image_repo> and <new_tag>. For example, depending on the tool that you are using, run one of the following commands.

To find the name of your region, run the [ibmcloud cr region](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_region) command.



* If you are using Docker, run the following command.

docker tag <source_image>:<tag> <region>.icr.io/<my_namespace>/<new_image_repo>:<new_tag>

Example, where <source_image> is hello-world, <tag> is latest, <region> is uk, <my_namespace> is namespace1, <new_image_repo> is hw_repo, and <new_tag> is 1:
[More Actions icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/action-menu-icon.svg) for a specific image and select from the available options.
3. Select Schedule lifecycle.
4. Select Schedule complete lifecycle.



* If you selected By calendar date, enter the date and time for when you want the status change occur.
* If you selected By number of days, put in the number of days that you want to pass before the status is changed.



The date for obsolescence must be after the deprecation date.
5. Click Schedule.







 Changing an image from volume lifecycle status by using the CLI 

You can change the lifecycle status of an IBM Cloud VPC image from volume by using the command-line interface (CLI). You can make an immediate status change by using the ibmcloud is image-deprecate or ibmcloud is image-obsolete commands. You can also schedule these status changes for a future date and time by using the ibmcloud is image-update command. Specify the name or ID of the custom image with the IMAGE variable.

To make an immediate status change, use one of the following examples.

You can make an immediate status change only if a future status change is not scheduled. To remove a scheduled status change, see [Remove a scheduled custom image lifecycle status change by using the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-image-from-volume-vpc-manageschedule-reset-ilm-status-change-cli). After you remove the scheduled status change, you can make an immediate status change.



* Change the image lifecycle status to deprecate.

ibmcloud is image-deprecate IMAGE
* Change the image lifecycle status to obsolete.

ibmcloud is image-obsolete IMAGE



To schedule a status change, use the following example.