Skip to content

[Automated] Draft docs (kagent): fix: include image pull secrets in substrate worker pool service account #664

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
github-actions wants to merge 1 commit into from
Closed

[Automated] Draft docs (kagent): fix: include image pull secrets in substrate worker pool service account #664

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: 2 additions & 0 deletions docs-site/content/kagent/1.x/operations/tune-agent-substrate.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,6 +157,8 @@ substrateWorkerPool:

The chart writes `serviceAccountName` into the pool's pod template. A `serviceAccountName` that you set under `substrateWorkerPool.template` is overwritten rather than merged. Set the account through `substrateWorkerPool.serviceAccount.name`.

If the chart creates the Worker ServiceAccount, the account receives the chart's image pull secrets. Use `imagePullSecrets` for secrets that apply only to this chart, or `global.imagePullSecrets` for secrets that apply to every pod. The chart merges the two lists by Secret name. If you set `substrateWorkerPool.serviceAccount.create` to `false`, add the image pull secrets to your external ServiceAccount. The chart does not update an account that it does not create.

### Keep placement scoped to the pool's namespace {#workerpool-placement-labels}

kagent selects a WorkerPool by name and namespace when it compiles an ActorTemplate, and the generated ActorTemplate matches Workers on the `kagent.dev/worker-pool-name` and `kagent.dev/worker-pool-namespace` labels. Agent Substrate matches those labels across every pool rather than checking the WorkerPool's namespace. A pool that sets only the name label can therefore be selected from another namespace.
Expand Down