Skip to content

OSDOCS#3437: Making update permission optional for creating routes #96060

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

OSDOCS#3437: Making update permission optional for creating routes #96060

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion modules/cert-manager-configuring-routes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ The following steps demonstrate the process of utilizing the {cert-manager-opera
.Prerequisites

* You have installed version 1.14.0 or later of the {cert-manager-operator}.
* You have the `create` and `update` permissions on the `routes/custom-host` sub-resource.
* You have `create` permission on the `routes/custom-host` sub-resource that helps create and update routes.
* You have a `Service` resource that you want to expose.

.Procedure
Expand Down
2 changes: 1 addition & 1 deletion 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 @@ -16,7 +16,7 @@ This feature applies to both edge routes and re-encrypt routes.
.Prerequisites

* You must enable the `RouteExternalCertificate` feature gate.
* You must have the `create` and `update` permissions on the `routes/custom-host`.
* You have `create` permission on the `routes/custom-host` sub-resource that helps create and update 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.
Expand Down