OSDOCS-17171-2:CQA 2.0-Security-Certificates-Attachment3

[tedaveryredhat]

Version(s):
4.20+

Issue:
https://redhat.atlassian.net/browse/OSDOCS-17171

Link to docs preview:
https://114797--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/certificates/api-server.html

[openshift-ci-robot]

@tedaveryredhat: This pull request references OSDOCS-17171 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.20+

Issue:
https://redhat.atlassian.net/browse/OSDOCS-17171

Link to docs preview:

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.

[ocpdocs-previewbot]

🤖 Tue Jul 07 18:52:16 - Prow CI generated the docs preview:

https://114797--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/certificates/api-server.html

[openshift-ci]

@tedaveryredhat: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

[tedaveryredhat]

/label merge-review-needed

[mburke5678]

Not a very strong short description. Would something like the be better/accurate?

[role="_abstract"]
To allow clients outside of the cluster to verify the API server's certificate, You can replace the default API server certificate with one that is issued by a CA that clients trust.

By default, the API server certificate is issued by an internal {product-title} cluster CA. As a result, clients outside of the cluster cannot verify the API server's certificate.