Skip to content

📖 docs: fix ServiceAccount name inconsistency in ManifestWork executor example #532

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

Merged
openshift-merge-bot merged 1 commit into from
Nov 28, 2025
Merged

📖 docs: fix ServiceAccount name inconsistency in ManifestWork executor example #532

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 content/en/docs/concepts/work-distribution/manifestwork.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -840,7 +840,7 @@ The executor subject feature(introduced in release `0.9.0`) provides a way to cl
takes effect so that we can explicitly check whether the executor has sufficient permission in the managed cluster.

The following example clarifies the owner "executor1" of the `ManifestWork`, so before the work-agent applies the
"default/test" `ConfigMap` to the managed cluster, it will first check whether the `ServiceAccount` "default/executor"
"default/test" `ConfigMap` to the managed cluster, it will first check whether the `ServiceAccount` "default/executor1"
has the permission to apply this `ConfigMap`

```yaml
Expand Down