OSDOCS-19235:Update the z-stream RNs for 4.19.29#110740
OSDOCS-19235:Update the z-stream RNs for 4.19.29#110740tedaveryredhat wants to merge 1 commit intoopenshift:enterprise-4.19from
Conversation
|
@tedaveryredhat: This pull request references OSDOCS-19235 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
added
the
jira/valid-reference
openshift-ci
Bot
added
the
size/M
|
🤖 Thu Apr 23 19:17:58 - Prow CI generated the docs preview: |
|
|
||
| * Before this update, the accumulation of unique session cookies across multi-pod deployments caused *Header Too Large* errors. With this release, the console proactively expires outdated pod-specific cookies whenever a new session is created. As a result, the cookie header remains within size limits during frequent re-authentications (especially with {azure-first} AD SSO) while maintaining a stable, single active session. (link:https://redhat.atlassian.net/browse/OCPBUGS-81574[OCPBUGS-81574]) | ||
|
|
||
| * Before this update, DNS name rules in the `EgressFirewall` custom resource (CR) were not working correctly when an error was encountered during DNS name resolution or a zero TTL value was returned by the DNS nameserver. For both scenarios, the next lookup occurred only after 30 minutes. However, these scenarios could be transient and might have gotten resolved well before the next lookup. With this update, the lookup occurs every five seconds when an error is encountered during DNS name resolution or a zero TTL value is returned by the DNS nameserver. When an error is encountered during the DNS lookup, the lookup occurs with an exponential backoff after 10 retries, with the maximum backoff time capped at two minutes. (link:https://redhat.atlassian.net/browse/OCPBUGS-82032[OCPBUGS-82032]) |
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'name server' rather than 'nameserver'. For more information, see RedHat.TermsErrors.
|
|
||
| * Before this update, the accumulation of unique session cookies across multi-pod deployments caused *Header Too Large* errors. With this release, the console proactively expires outdated pod-specific cookies whenever a new session is created. As a result, the cookie header remains within size limits during frequent re-authentications (especially with {azure-first} AD SSO) while maintaining a stable, single active session. (link:https://redhat.atlassian.net/browse/OCPBUGS-81574[OCPBUGS-81574]) | ||
|
|
||
| * Before this update, DNS name rules in the `EgressFirewall` custom resource (CR) were not working correctly when an error was encountered during DNS name resolution or a zero TTL value was returned by the DNS nameserver. For both scenarios, the next lookup occurred only after 30 minutes. However, these scenarios could be transient and might have gotten resolved well before the next lookup. With this update, the lookup occurs every five seconds when an error is encountered during DNS name resolution or a zero TTL value is returned by the DNS nameserver. When an error is encountered during the DNS lookup, the lookup occurs with an exponential backoff after 10 retries, with the maximum backoff time capped at two minutes. (link:https://redhat.atlassian.net/browse/OCPBUGS-82032[OCPBUGS-82032]) |
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'name server' rather than 'nameserver'. For more information, see RedHat.TermsErrors.
| [id="zstream-4-19-29-updating_{context}"] | ||
| == Updating | ||
|
|
||
| To update an {product-title} 4.19 cluster to this latest release, see xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster using the CLI]. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
tedaveryredhat
force-pushed
the
OSDOCS-19235
branch
from
196eeb7 to
dff439f
Compare
|
@tedaveryredhat: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
4 participants
Version(s):
4.19
Issue:
https://redhat.atlassian.net/browse/OSDOCS-19235
Link to docs preview:
Additional information:
4.19.29 MR: https://gitlab.cee.redhat.com/hybrid-platforms/art/ocp-shipment-data/-/merge_requests/479
ART Dashboard: https://art-dash.engineering.redhat.com/dashboard/release/openshift-4.19