Repository navigation
Fix Swarm secret references for managed risk workers - #323
Merged
Merged
Conversation
Signed-off-by: zerodrift <zerodrift@users.noreply.github.com>
zerodrift
enabled auto-merge
November 19, 2026 03:35
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
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.
Docker Engine rejected the service rendered after #320 because the three secret references were missing their registered Swarm names. The renderer now binds each secret by both name and ID. Existing installation profiles need the three names before rendering. The installation guide also specifies Engine API v1.47 for recording the approved service specification.
Verification
All three VMs shared one physical host. Target-host capacity and large-portfolio performance remain deployment checks.