Conversation
…count workloadServiceAccount.imagePullSecrets does not work for private nodes because workload pods run on dedicated private nodes and do not sync to the Control Plane Cluster namespace. Add a note pointing private node users to privateNodes.joinNode.containerd.registry instead. Closes DOC-1306 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
✅ Deploy Preview for vcluster-docs-site ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
teb510
approved these changes
Apr 16, 2026
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
2 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.
Summary
privateNodes="true"from theTenancySupportbanner on theworkloadServiceAccountpageprivate-nodesfromsidebar_class_nameprivateNodes.joinNode.containerd.registryfor image pull configurationworkloadServiceAccount.imagePullSecretsdoes not apply to private nodes because workload pods run on dedicated private nodes and never sync to the Control Plane Cluster namespace. The equivalent for private nodes is containerd-level registry configuration.Note:
controlPlane.advanced.serviceAccount(the control plane's own ServiceAccount) correctly remains marked as supported for private nodes — that pod always runs in the Control Plane Cluster.Test plan
workloadServiceAccountpage no longer shows Private Nodes in the supported configurations bannerprivateNodes.joinNode.containerd.registryCloses DOC-1306
🤖 Generated with Claude Code