Skip to content

Conversation

@tmalove
Copy link
Contributor

@tmalove tmalove commented Oct 17, 2025

Version(s):
4.20

Issue:
OSDOCS-13616

Link to docs preview:
[etcd cluster latency requirements

QE review:

  • QE has approved this change.

Additional information:
This PR replaces the original one. The content is the same.

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 17, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Oct 17, 2025

🤖 Fri Oct 17 16:47:55 - Prow CI generated the docs preview:

https://100706--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-20-release-notes.html

@dusk125
Copy link

dusk125 commented Oct 17, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2025
@tmalove tmalove force-pushed the osdocs-16319-rn-new branch from 0c17134 to c1052c4 Compare October 17, 2025 13:31
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2025
@tmalove tmalove force-pushed the osdocs-16319-rn-new branch 2 times, most recently from 2943b24 to 81ecaa8 Compare October 17, 2025 15:06
@dusk125
Copy link

dusk125 commented Oct 17, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2025
[id="ocp-release-notes-additional-cluster-requirements-for-etcd_{context}"]
==== Additional cluster latency requirements for etcd

With this update, the etcd product documentation is updated to include additional requirements for reducing {product-title} cluster latency. This update clarifies the prerequisites and setup procedures for using etcd, resulting in an improved user experience. As a result, this feature introduces support for Transport Layer Security (TLS) 1.3 in etcd, which enhances security and performance for data transmission, and enables etcd to comply with the latest security standards, reducing potential vulnerabilities. The improved encryption ensures more secure communication between etcd and its clients. For more information, see link:https://github.com/openshift/openshift-docs/pull/100647[Document cluster latency requirements for etcd]
Copy link
Contributor

@dfitzmau dfitzmau Oct 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
With this update, the etcd product documentation is updated to include additional requirements for reducing {product-title} cluster latency. This update clarifies the prerequisites and setup procedures for using etcd, resulting in an improved user experience. As a result, this feature introduces support for Transport Layer Security (TLS) 1.3 in etcd, which enhances security and performance for data transmission, and enables etcd to comply with the latest security standards, reducing potential vulnerabilities. The improved encryption ensures more secure communication between etcd and its clients. For more information, see link:https://github.com/openshift/openshift-docs/pull/100647[Document cluster latency requirements for etcd]
With this update, the etcd product documentation is updated to include additional requirements for reducing {product-title} cluster latency. This update clarifies the prerequisites and setup procedures for using etcd, resulting in an improved user experience. As a result, this feature introduces support for Transport Layer Security (TLS) 1.3 in etcd, which enhances security and performance for data transmission, and enables etcd to comply with the latest security standards, reducing potential vulnerabilities. The improved encryption ensures more secure communication between etcd and its clients. For more information, see xref:../etcd/etcd-practices.adoc#recommended-cluster-latency-etcd_etcd-practices[Cluster latency requirements for etcd].

@tmalove tmalove force-pushed the osdocs-16319-rn-new branch from 81ecaa8 to 8083187 Compare October 17, 2025 15:41
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2025
@tmalove tmalove force-pushed the osdocs-16319-rn-new branch 2 times, most recently from 6bb0f4b to c5dd248 Compare October 17, 2025 16:14
@tmalove tmalove force-pushed the osdocs-16319-rn-new branch from c5dd248 to 0025623 Compare October 17, 2025 16:17
@dfitzmau
Copy link
Contributor

LGTM as soon as the build passes!

@openshift-ci
Copy link

openshift-ci bot commented Oct 17, 2025

@tmalove: all tests passed!

Full PR test history. Your PR dashboard.

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

@dusk125
Copy link

dusk125 commented Oct 17, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2025
@tmalove
Copy link
Contributor Author

tmalove commented Oct 17, 2025

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Oct 17, 2025
@skopacz1 skopacz1 added the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Oct 17, 2025
Copy link
Contributor

@skopacz1 skopacz1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@skopacz1 skopacz1 merged commit 29063ac into openshift:enterprise-4.20 Oct 17, 2025
2 checks passed
@skopacz1 skopacz1 removed merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR labels Oct 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.20 lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants