Repository navigation
Isolate operator startup and preserve Unix services during updates - #162
Merged
Merged
Conversation
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.
Administrative commands need a fixed credential and configuration boundary while preserving caller-relative files and stdin.
sudo guard-operatorrequires root ownership and mode0700, authenticates from the protected token file while preserving command stdin, and rejects an incompatible Guard binary before connecting.The Unix installer validates the coordinated package and offers read-only checks plus explicit binary updates that preserve compatible existing service units, drop-ins, identities, configuration and state. The deployment guide covers separate service activation and matching-snapshot rollback.