Skip to content

OCPBUGS #34373: Added a note in creating the externally managed certificate section #92978

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

OCPBUGS #34373: Added a note in creating the externally managed certificate section #92978

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions modules/nw-ingress-route-secret-load-external-cert.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,14 @@ This feature applies to both edge routes and re-encrypt routes.
* You must have a secret containing a valid certificate/key pair in PEM-encoded format of type `kubernetes.io/tls`, which includes both `tls.key` and `tls.crt` keys.
* You must place the referenced secret in the same namespace as the route you want to secure.

[NOTE]
====
To configure the `spec.tls.externalCertificate` field on a route:

* You must have the `create` permission on the `routes/custom-host` sub-resource to set this field during route creation.
* You must have either the `create` or `update` permission on the `routes/custom-host` sub-resource to modify this field on an existing route.
====

.Procedure

. Create a `role` in the same namespace as the secret to allow the router service account read access by running the following command:
Expand Down