vania-janet/multiturn-rag-retrieval-data huggingface dataset:
RoleID: core.StringPtr("crn:v1:bluemix:public:iam::::role:Viewer"),
}
accountIDResourceAttribute := &iampolicymanagementv1.ResourceAttribute{
Name: core.StringPtr("accountId"),
Value: core.StringPtr("ACCOUNT_ID"),
Operator: core.StringPtr("stringEquals"),
}
serviceNameResourceAttribute := &iampolicymanagementv1.ResourceAttribute{
Name: core.StringPtr("serviceName"),
Value: core.StringPtr("is"),
Operator: core.StringPtr("stringEquals"),
}
policyResources := &iampolicymanagementv1.PolicyResource{
Attributes: []iampolicymanagementv1.ResourceAttribute{
accountIDResourceAttribute, serviceNameResourceAttribute}
}

options := iamPolicyManagementService.NewCreatePolicyOptions(
"access",
[]iampolicymanagementv1.PolicySubject{policySubjects},
[]iampolicymanagementv1.PolicyRole{policyRoles},
[]iampolicymanagementv1.PolicyResource{policyResources},
)

policy, response, err := iamPolicyManagementService.CreatePolicy(options)
if err != nil {
panic(err)
}
b, _ := json.MarshalIndent(policy, "", " ")
fmt.Println(string(b))

const policySubjects = [
{
attributes:
{
name: 'iam_id',
value: 'IBMid-123453user',
},
],
After the token is returned and you [decode](https://cloud.ibm.com/docs/appid?topic=appid-token-validation) it, you see a result similar to the following example:

{
"sub" : "1234567890",
"name" : "John Doe",
"exp" : 1564566,
"roles" : ["admin", "manager"],
"id": "<nameIDFromSaml>",
"attributes.uid": "<uidFromSaml>"
...
}
a string text STRING TEXT string a string text 
 {"firefox": { <br>"name": "Firefox", <br>"pref_url": "about:config" <br>}} STRING JSON org.json.JSONObject {"firefox":{"name":"Firefox","pref_url":"about:config"}} 
 men: <br>- John Smith <br>- Bill Jones <br>women: <br>- Mary Smith <br>- Susan Williams STRING YAML java.lang.String `"men:<br><br><br><br> * John Smith<br> * Bill Jones\women:<br> * Mary Smith<br> * Susan Williams"`<br><br><br> 





 Feature flag usage example 

const feature = client.getFeature('json-feature');
feature.getFeatureDataType(); // STRING
feature.getFeatureDataFormat(); // JSON

// Example (traversing the returned JSON)
let result = feature.getCurrentValue(entityId, entityAttributes);
console.log(result.key) // prints the value of the key

const feature = client.getFeature('yaml-feature');
feature.getFeatureDataType(); // STRING
feature.getFeatureDataFormat(); // YAML
feature.getCurrentValue(entityId, entityAttributes); // returns the stringified yaml (check above table)





 Property usage example 

const property = client.getProperty('json-property');
property.getPropertyDataType(); // STRING
property.getPropertyDataFormat(); // JSON

// Example (traversing the returned JSON)
let result = property.getCurrentValue(entityId, entityAttributes);
Discovery supports prefiltering only. To prefilter, Discovery replicates the document's source access control list (ACL) at crawl time into the index. The search engine must compare user credentials to the replicated document ACLs. Discovery is faster when documents are prefiltered and when you control which documents you add to the index. However, it is difficult to model all of the security policies of the various data sources in the index and implement comparison logic uniformly. Also, prefiltering is not as responsive to changes that occur in the source ACLs after the most recent crawl.

Document-level security is supported by the following data source types:



* Box
* FileNet P8
* HCL Notes
* Microsoft SharePoint Online
* Microsoft SharePoint On Prem
* Microsoft Windows File System



When you query collections where document-level security is enabled, no results are returned if the users associated with your Discovery instance are not present in the source system. For more information about querying these collections, see [Querying with document-level security enabled](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-conceptsquerydls).

To enable document-level security, you must complete the following steps:



1. [Create Discovery users that match the users available on the source system](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collection-typescreateusersdls).
2. Associate users with your Discovery instance. For more information, see [Giving users access to a Watson Discovery instance](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-discovery/discovery-admin-add-users.html).
3. Enable document-level security for the data source when you connect to it.





 Creating users for document-level security 

You must create users that match the users available on the source system that Discovery is connecting to so that they can query with document-level security enabled.



1. Log in to Discovery as an administrator.
2.
[recognize-audio](https://cloud.ibm.com/apidocs/speech-to-textrecognize-audio) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, audio, content_type, model, customization_id, acoustic_customization_id, base_model_version, customization_weight, inactivity_timeout, keywords, keywords_threshold, max_alternatives, word_alternatives_threshold, word_confidence, timestamps, profanity_filter, smart_formatting, speaker_labels Recognize audio. 
 [check-job](https://cloud.ibm.com/apidocs/speech-to-textcheck-a-job) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, id Check a job. 
 [check-jobs](https://cloud.ibm.com/apidocs/speech-to-textcheck-jobs) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url Check jobs. 
 [create-job](https://cloud.ibm.com/apidocs/speech-to-textcreate-job) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, audio, content_type, model, callback_url, events, user_token, results_ttl, customization_id, acoustic_customization_id, base_model_version, customization_weight, inactivity_timeout, keywords, keywords_threshold, max_alternatives, word_alternatives_threshold, word_confidence, timestamps, profanity_filter, smart_formatting, speaker_labels Create a job.
$ ibmcloud kp key show $KEY_ID --output json

 OR... CAPTURE THE PAYLOAD
$ PAYLOAD=$(ibmcloud kp key show $KEY_ID --output json | jq -r '.["payload"]')

{
"id": "8480e26f-3add-4fff-bca7-8cf908894b7c",
"name": "credentials-key",
"type": "application/vnd.ibm.kms.key+json",
"algorithmType": "AES",
"createdBy": "user id ...<redacted>...",
"creationDate": "2020-08-18T16:13:08Z",
"lastUpdateDate": "2020-08-18T16:13:08Z",
"extractable": true,
"payload": "ewoJImhvc3QiOiAibG9jYWxob3N0IiwKCSJkYXRhYmFzZSI6ICJkZXYtYmFja3VwIiwKCSJ1c2VybmFtZSI6ICJteS11c2VybmFtZSIsCgkicGFzc3dvcmQiOiAibXktcGFzc3dvcmQiCn0=",
"state": 1,
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:a192d603-0b8d-452f-aac3-f9e1f95e7411:key:8480e26f-3add-4fff-bca7-8cf908894b7c",
"deleted": false,
"dualAuthDelete": {
"enabled": false
}
}

 decode the payload to get the original string (credentials)
$ echo $PAYLOAD | base64 -d

{
"host": "localhost",
"database": "dev-backup",
"username": "my-username",
"password": "my-password"
}







 Required parameters 

KEY_NAME
: A unique, human-readable alias to assign to your key.
nginx.ingress.kubernetes.io/configuration-snippet: 
auth_request_set $_oauth2_<App_ID_service_instance_name>_upstream_1 $upstream_cookie__oauth2_<App_ID_service_instance_name>_1;
auth_request_set $access_token $upstream_http_x_auth_request_access_token;
access_by_lua_block {
if ngx.var._oauth2_<App_ID_service_instance_name>_upstream_1 = "" then
ngx.header["Set-Cookie"] = "_oauth2_<App_ID_service_instance_name>_1=" .. ngx.var._oauth2_<App_ID_service_instance_name>_upstream_1 .. ngx.var.auth_cookie:match("(; .)")
end
if ngx.var.access_token = "" then
ngx.req.set_header("Authorization", "Bearer " .. ngx.var.access_token)
end
}
...
Show more
* To send the Access Token and the ID Token, add the following information to the configuration-snippet annotation. (This extends the snippet from Step 5.2.)

...
annotations:
nginx.ingress.kubernetes.io/configuration-snippet: 
auth_request_set $_oauth2_<App_ID_service_instance_name>_upstream_1 $upstream_cookie__oauth2_<App_ID_service_instance_name>_1;
auth_request_set $access_token $upstream_http_x_auth_request_access_token;
auth_request_set $id_token $upstream_http_authorization;
access_by_lua_block {
The following table shows the changes that are in the worker node fix pack update 3.11.232_1555_openshift. Worker node patch updates can be applied by updating or reloading the worker node



Changes since version 3.11.232_1554_openshift

 Component Previous Current Description 

 Master Proxy 1.8.25-30b675 2.0.15-afe432 See the [HA proxy change logs](https://www.haproxy.org/download/2.0/src/CHANGELOG). 
 RHEL 7 Packages 3.10.0-1127.10.1.el7 3.10.0-1127.13.1.el7 Updated worker node images with kernel package updates for [CVE-2020-10749](https://nvd.nist.gov/vuln/detail/CVE-2020-10749), [CVE-2020-1702](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1702), [CVE-2016-8867](https://nvd.nist.gov/vuln/detail/CVE-2016-8867), [CVE-2020-14298](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14298), [CVE-2020-14300](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14300), [CVE-2020-12888](https://nvd.nist.gov/vuln/detail/CVE-2020-12888), [CVE-2020-11868](https://nvd.nist.gov/vuln/detail/CVE-2020-11868), and [CVE-2020-13817](https://nvd.nist.gov/vuln/detail/CVE-2020-13817).
resource "ibm_container_worker_pool_zone_attachment" "tfwp-dal13" {
cluster = ibm_container_cluster.tfcluster.id
worker_pool = element(split("/",ibm_container_worker_pool.workerpool.id),1)
zone = "dal13"
private_vlan_id = "<private_vlan_ID_dal13>"
public_vlan_id = "<public_vlan_ID_dal13>"
resource_group_id = data.ibm_resource_group.resource_group.id
}
Show more

For more information, about the description of ibm_container_worker_pool_zone_attachment argument reference such as public_vlan_id, private_vlan_id values, refer to [registry documentation of ibm_container_worker_pool_zone_attachment](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_worker_pool_zone_attachmentargument-reference).

For more information, about the description of ibm_container_worker_pool argument reference, refer to [registry documentation of ibm_container_worker_pool](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_worker_poolargument-reference).
2. Create an Terraform on IBM Cloud execution plan and review the actions that Terraform on IBM Cloud is about to perform.

terraform plan

Example output

...
Plan: 4 to add, 0 to change, 0 to destroy.
3. Create the worker pool in your cluster and spread worker nodes across the zones that you defined. Note that the creation of worker nodes might take a few minutes to complete.

terraform apply

Example output

...
ibm_container_worker_pool.workerpool: Creating...
ibm_container_worker_pool.workerpool: Creation complete after 6s [id=aaaaaaaaa1eaaaaaaaaa/aaaaaaaaa1eaaaaaaa-aa1aa11]
The documentation includes v2.4 [Fabric Gateway samples](https://github.com/hyperledger/fabric-gateway/tree/main/samples), [connection details](https://hyperledger-fabric.readthedocs.io/en/release-2.4/write_first_app.htmlfirst-establish-a-grpc-connection-to-the-gateway), and related client application development topics.





 Connecting to the Fabric Gateway peer service 

A client application that uses the v2.4 Fabric Gateway peer service needs to specify the connection details for the target peer. The recommended method for retrieving peer connection information is to download the connection profile for your organization, which contains the peer endpoint URL, and the TLS Root CA certificate in pem format, required for the client application to connect.

Attention: The peer endpoint URL in the downloaded connection profile starts with grpcs://, which is not recognized as part of the endpoint URL. The endpoint URL is therefore the url field in the peer connection profile, with the grpcs:// prefix removed. Peer node details in the organization connection profile will look similar to the following example:

"url": "grpcs://n257768-org1peer1.us-east.containers.appdomain.cloud:7051",
"tlsCACerts": {
"pem": "-----BEGIN CERTIFICATE-----nMIICCzCCAbKgAwIBAgIUYH1G2I60YOEZuiAQPsvSmWXABxUwCgYIKoZIzj0EAwIwnZDELMAkGA1UEBhMCVVMxFzAVBgNVBAg
< MATERIAL REMOVED FOR BREVITY AND SECURITY>
DAQH/MB0GA1UdDgQWBBRDV6AdNnpIEGO9n7mbUM5bk4U0/yTAKBggqhkjOPQQDAgNHADBEAiAxjAM3zkf4v0TXUlJZZgS4TFE5nY7eO7e16X1rETFryywIgHuSvyhPDUog0hD5VUUtZjroXYG4pO1aI1L/zue9lr48=n-----END CERTIFICATE-----n"
},
"grpcOptions": {
: Change log documentation is available for worker node versions [4.8.24_1540_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_484824_1540),[4.7.40_1545_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_474740_1545), [4.6.52_1568_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464652_1568), and [3.11.570_1617_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311570_1617).







 December 2021 

Review the release notes for December 2021.



 20 December 2021 

Worker node fix pack update
: Change log documentation is available for Red Hat OpenShift version [4.8.24_1539_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_484824_1539_openshift), [4.7.40_1544_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_474740_1544_openshift), [4.6.52_1567_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464652_1567_openshift), and [3.11.570_1616_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311570_1616_openshift).





 7 December 2021 

Master fix pack update
Change log for worker node fix pack 4.12.4_1528_openshift, released 27 February 2023 

The following table shows the changes that are in the worker node fix pack 4.12.4_1528_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.12.2_1526_openshift

 Component Previous Current Description 

 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).
Change log for worker node fix pack 4.10.26_1530_openshift, released 16 August 2022 

The following table shows the changes that are in the worker node fix pack 4.10.26_1530_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.10.24_1529_openshift

 Component Previous Current Description 

 RHEL 7 Packages 3.10.0-1160.71.1 3.10.0-1160.76.1 Worker node package updates for [CVE-2022-0005](https://nvd.nist.gov/vuln/detail/CVE-2022-0005), [CVE-2022-21123](https://nvd.nist.gov/vuln/detail/CVE-2022-21123), [CVE-2022-21125](https://nvd.nist.gov/vuln/detail/CVE-2022-21125), [CVE-2022-21127](https://nvd.nist.gov/vuln/detail/CVE-2022-21127), [CVE-2022-21131](https://nvd.nist.gov/vuln/detail/CVE-2022-21131), [CVE-2022-21136](https://nvd.nist.gov/vuln/detail/CVE-2022-21136), [CVE-2022-21151](https://nvd.nist.gov/vuln/detail/CVE-2022-21151), [CVE-2022-21166](https://nvd.nist.gov/vuln/detail/CVE-2022-21166). 
 Red Hat OpenShift on IBM Cloud.
* Worker node versions



* [14 January 2021](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jan1421)



* Cluster autoscaler



* [12 January 2021](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jan1221)



* Ingress resources
* Kubernetes benchmarks
* Removal of data center support



* [7 January 2021](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jan0721)



* Ingress ALB change log



* [6 January 2021](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-jan0621)



* Master versions





* [December 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-dec20)



* [21 December 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-dec2120)



* Gateway firewalls and Calico policies
* Worker node versions



* [18 December 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-dec1820)



* CLI change log
* IBM Cloud Object Storage plug-in



* [17 December 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-dec1720)



* Audit documentation
* Back up and restore
* Ingress ALB change log



* [16 December 2020](https://cloud.ibm.com/docs/containers?topic=containers-containers-relnotescontainers-dec1620)



* Istio add-on
* [Migrating your worker nodes to RHEL 8](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_versions_4949_rhel-migrate)



[Red Hat OpenShift version 4.9 change log](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49openshift_changelog_49)



* [Overview](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49openshift_changelog_overview_49)
* [Change logs](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_4949_changelog)



* [Change log for worker node fix pack 4.9.59_1595_openshift, released 03 July 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_494959_1595_openshift_W)
* [Change log for master fix pack 4.9.59_1594_openshift, released 27 June 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_494959_1594_openshift_M)
* [Change log for worker node fix pack 4.9.59_1593_openshift, released 19 June 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_494959_1593_openshift_W)
* [Change log for worker node fix pack 4.9.59_1592_openshift, released 5 June 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_494959_1592_openshift_W)
Change log for worker node fix pack 1.22.12_1566, released 16 August 2022 

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



Changes since version 1.22.12_1565

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-189 4.15.0-191 Worker node kernel & package updates for [CVE-2016-3709](https://nvd.nist.gov/vuln/detail/CVE-2016-3709), [CVE-2021-4209](https://nvd.nist.gov/vuln/detail/CVE-2021-4209), [CVE-2022-1652](https://nvd.nist.gov/vuln/detail/CVE-2022-1652), [CVE-2022-1679](https://nvd.nist.gov/vuln/detail/CVE-2022-1679), [CVE-2022-1734](https://nvd.nist.gov/vuln/detail/CVE-2022-1734), [CVE-2022-2509](https://nvd.nist.gov/vuln/detail/CVE-2022-2509), [CVE-2022-2586](https://nvd.nist.gov/vuln/detail/CVE-2022-2586), [CVE-2022-2588](https://nvd.nist.gov/vuln/detail/CVE-2022-2588), [CVE-2022-34918](https://nvd.nist.gov/vuln/detail/CVE-2022-34918). 
 Kubernetes N/A N/A N/A 







 Change log for worker node fix pack 1.22.12_1565, released 01 August 2022
Change log for worker node fix pack 4.6.60_1594_openshift, released 16 August 2022 

The following table shows the changes that are in the worker node fix pack 4.6.60_1594_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.6.60_1593_openshift

 Component Previous Current Description 

 RHEL 7 Packages 3.10.0-1160.71.1 3.10.0-1160.76.1 Worker node package updates for [CVE-2022-0005](https://nvd.nist.gov/vuln/detail/CVE-2022-0005), [CVE-2022-21123](https://nvd.nist.gov/vuln/detail/CVE-2022-21123), [CVE-2022-21125](https://nvd.nist.gov/vuln/detail/CVE-2022-21125), [CVE-2022-21127](https://nvd.nist.gov/vuln/detail/CVE-2022-21127), [CVE-2022-21131](https://nvd.nist.gov/vuln/detail/CVE-2022-21131), [CVE-2022-21136](https://nvd.nist.gov/vuln/detail/CVE-2022-21136), [CVE-2022-21151](https://nvd.nist.gov/vuln/detail/CVE-2022-21151), [CVE-2022-21166](https://nvd.nist.gov/vuln/detail/CVE-2022-21166). 
 Red Hat OpenShift on IBM Cloud. N/A N/A N/A 







 Change log for worker node fix pack 4.6.60_1593_openshift, released 01 August 2022
Change log for worker node fix pack 4.7.59_1588_openshift, released 07 November 2022 

The following table shows the changes that are in the worker node fix pack 4.7.59_1588_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.7.59_1585_openshift

 Component Previous Current Description 

 RHEL 7 Packages 3.10.0-1160.76.1 3.10.0-1160.80.1 Worker node kernel & package updates for [CVE-2022-21233](https://nvd.nist.gov/vuln/detail/CVE-2022-21233), [CVE-2022-23816](https://nvd.nist.gov/vuln/detail/CVE-2022-23816), [CVE-2022-23825](https://nvd.nist.gov/vuln/detail/CVE-2022-23825), [CVE-2022-2588](https://nvd.nist.gov/vuln/detail/CVE-2022-2588), [CVE-2022-26373](https://nvd.nist.gov/vuln/detail/CVE-2022-26373), [CVE-2022-29900](https://nvd.nist.gov/vuln/detail/CVE-2022-29900), [CVE-2022-29901](https://nvd.nist.gov/vuln/detail/CVE-2022-29901), [CVE-2022-41974](https://nvd.nist.gov/vuln/detail/CVE-2022-41974).
Ubuntu 18.04 packages 4.15.0-143 4.15.0-144 Updated worker node images with kernel package updates for [CVE-2021-25217](https://nvd.nist.gov/vuln/detail/CVE-2021-25217), [CVE-2021-31535](https://nvd.nist.gov/vuln/detail/CVE-2021-31535), [CVE-2021-32547](https://nvd.nist.gov/vuln/detail/CVE-2021-32547), [CVE-2021-32552](https://nvd.nist.gov/vuln/detail/CVE-2021-32552), [CVE-2021-32556](https://nvd.nist.gov/vuln/detail/CVE-2021-32556), [CVE-2021-32557](https://nvd.nist.gov/vuln/detail/CVE-2021-32557), [CVE-2021-3448](https://nvd.nist.gov/vuln/detail/CVE-2021-3448), and [CVE-2021-3520](https://nvd.nist.gov/vuln/detail/CVE-2021-3520). 







 Change log for worker node fix pack 1.17.17_1564, released 24 May 2021 

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



Changes since version 1.17.17_1562

 Component Previous Current Description
Change log for worker node fix pack 4.10.50_1554_openshift, released 30 January 2023 

The following table shows the changes that are in the worker node fix pack 4.10.50_1554_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.10.47_1551_openshift

 Component Previous Current Description 

 RHEL 7 Packages 3.10.0-1160.81 3.10.0-1160.83 Worker node kernel & package updates for [CVE-2017-5715](https://nvd.nist.gov/vuln/detail/CVE-2017-5715), [CVE-2021-25220](https://nvd.nist.gov/vuln/detail/CVE-2021-25220), [CVE-2021-26401](https://nvd.nist.gov/vuln/detail/CVE-2021-26401), [CVE-2022-2795](https://nvd.nist.gov/vuln/detail/CVE-2022-2795), [CVE-2022-2964](https://nvd.nist.gov/vuln/detail/CVE-2022-2964), [CVE-2023-22809](https://nvd.nist.gov/vuln/detail/CVE-2023-22809). 
 RHEL 8 Packages N/A N/A Worker node kernel & package updates for [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-2023-22809](https://nvd.nist.gov/vuln/detail/CVE-2023-22809).