OSDOCS-19410-4 back porting most recent zero-trust docs to 4.18 PR#4#110952
Open
wgabor0427 wants to merge 1 commit intoopenshift:enterprise-4.18from
Open
OSDOCS-19410-4 back porting most recent zero-trust docs to 4.18 PR#4#110952wgabor0427 wants to merge 1 commit intoopenshift:enterprise-4.18from
wgabor0427 wants to merge 1 commit intoopenshift:enterprise-4.18from
Conversation
openshift-ci
Bot
added
the
size/L
wgabor0427
force-pushed
the
OSDOCS-19410-4
branch
3 times, most recently
from
31d41a5 to
e783c42
Compare
| $ oc get SpireServer cluster -o yaml | ||
| ---- | ||
| + | ||
| .Example output |
Collaborator
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.BlockTitle: Block titles can only be assigned to examples, figures, and tables in DITA.
| $ oc get SpireServer cluster -o yaml | ||
| ---- | ||
| + | ||
| .Example output |
Collaborator
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.BlockTitle: Block titles can only be assigned to examples, figures, and tables in DITA.
| toc::[] | ||
|
|
||
| [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. |
Collaborator
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.
|
|
||
| The following scenarios are examples of when the `create-only` mode might be of use: | ||
|
|
||
| **Manual Customization Required**: You need to customize operator-managed resources (ConfigMaps, Deployments, DaemonSets, etc.) with specific configurations that differ from the operator's defaults |
Collaborator
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.
|
|
||
| The following scenarios are examples of when the `create-only` mode might be of use: | ||
|
|
||
| **Manual Customization Required**: You need to customize operator-managed resources (ConfigMaps, Deployments, DaemonSets, etc.) with specific configurations that differ from the operator's defaults |
Collaborator
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.
|
|
||
| **Manual Customization Required**: You need to customize operator-managed resources (ConfigMaps, Deployments, DaemonSets, etc.) with specific configurations that differ from the operator's defaults | ||
|
|
||
| **Day 2 Operations**: After initial deployment, you want to prevent the operator from overwriting their manual changes during subsequent reconciliation cycles |
Collaborator
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.
|
|
||
| **Day 2 Operations**: After initial deployment, you want to prevent the operator from overwriting their manual changes during subsequent reconciliation cycles | ||
|
|
||
| **Configuration Drift Prevention**: You want to maintain control over certain resource configurations while still benefiting from the operator's lifecycle management |
Collaborator
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.
wgabor0427
force-pushed
the
OSDOCS-19410-4
branch
2 times, most recently
from
396c7b0 to
85cfef1
Compare
|
|
||
| The following scenarios are examples of when the `create-only` mode might be of use: | ||
|
|
||
| **Manual Customization Required**: You need to customize operator-managed resources (ConfigMaps, Deployments, DaemonSets, etc.) with specific configurations that differ from the Operator's defaults |
Collaborator
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.
wgabor0427
force-pushed
the
OSDOCS-19410-4
branch
from
85cfef1 to
e547a3f
Compare
wgabor0427
changed the title
|
@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. |
This was referenced Apr 29, 2026
wgabor0427
changed the title
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version(s):
4.18
Issue:
https://redhat.atlassian.net/browse/OSDOCS-19410
Link to docs preview:
https://110952--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/zero_trust_workload_identity_manager/zero-trust-manager-proxy.html
https://110952--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/zero_trust_workload_identity_manager/zero-trust-manager-reconciliation.html
QE review:
Additional information:
The 4.18 documentation in this PR is a copy and paste from the most recent zero-trust documentation.
This PR contains the following assemblies:
This is PR #4. This is related to the following PRs:
The PRs were put into smaller PRs instead of having one large PR. This makes it easier for the merge reviewers.