-
Notifications
You must be signed in to change notification settings - Fork 1.9k
OSDOCS-18281 backporting 4-20 docs to 4-19 #106402
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.
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
base: enterprise-4.19
Are you sure you want to change the base?
Conversation
26e915b to
93e3362
Compare
93e3362 to
556b27c
Compare
| Install {zero-trust-full} to help ensure secure communication between your workloads. You can install the {zero-trust-full} by using either the web console or CLI. | ||
|
|
||
| include::snippets/technology-preview.adoc[] | ||
| If you install the Operator into a custom namespace (for example, `my-custom-namespace`), all managed operand resources are deployed within that same namespace. All secrets and ConfigMaps referenced by the Custom Resources (CRs) must also exist in that custom namespace. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖 [error] Vale.Terms: Use 'custom resources?' instead of 'Custom Resources'.
7770f86 to
45192ad
Compare
8cdce5f to
4357082
Compare
|
|
||
| By enabling the `create-only` mode, you can pause the Operator reconciliation, which allows you to perform manual configurations or debug without the controller overwriting your changes. This is done by annotating the API resources which are managed by the Operator. The following scenarios are examples of when the `create-only` mode might be of use: | ||
| [role="_abstract"] | ||
| To pause Operator reconciliation, enable `create-only` mode by setting an environment variable in the subscription object. By setting this value, you can perform manual configurations or debug the operator without the controller overwriting your changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.
4357082 to
2163c3d
Compare
2163c3d to
371cb11
Compare
|
|
||
| * The `tosAccepted` field accepts the Let's Encrypt Terms of Service. | ||
|
|
||
| * The `managedRoute` field enables an automatic route creation by the operator for the federation bundle endpoint. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.
| |string | ||
| |No | ||
| |`"true"` | ||
| |Enable or disable automatic OpenShift Route creation. Set to `"true"` for operator-managed routes or `"false"` for manual route management. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.
| Field validation rules:: | ||
|
|
||
|
|
||
| The following validation rules are enforced by the operator: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.
|
|
||
| . Install the cert-manager Operator on the cluster where you want to use externally managed certificates. | ||
| + | ||
| Create a namespace and install the operator: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.
371cb11 to
3bdbb43
Compare
3bdbb43 to
e8d86a5
Compare
|
@wgabor0427: 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. |
Version(s):
4.19
Issue:
https://issues.redhat.com/browse/OSDOCS-18281
Link to docs preview:
https://106402--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/zero_trust_workload_identity_manager/zero-trust-manager-components.html
https://106402--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/zero_trust_workload_identity_manager/zero-trust-manager-configuration.html
https://106402--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/zero_trust_workload_identity_manager/zero-trust-manager-install.html
https://106402--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/zero_trust_workload_identity_manager/zero-trust-manager-monitoring.html
https://106402--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/zero_trust_workload_identity_manager/zero-trust-manager-oidc-federation.html
https://106402--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/zero_trust_workload_identity_manager/zero-trust-manager-overview.html
https://106402--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/zero_trust_workload_identity_manager/zero-trust-manager-proxy.html
https://106402--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/zero_trust_workload_identity_manager/zero-trust-manager-reconciliation.html
https://106402--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/zero_trust_workload_identity_manager/zero-trust-manager-spire-federation.html
https://106402--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/zero_trust_workload_identity_manager/zero-trust-manager-uninstall.html
QE review:
Additional information:
The information in these files were copied from the 4.20 repo.