ci: publish immutable Commander image for KiaB - #2332
Open
booker-keeper wants to merge 2 commits into
Open
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
1 participant
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
Add a GA-ready Docker/ECR publication workflow for Keeper Commander so it can be included as an optional Keeper-in-a-Box bundle artifact.
Changes
commanderECR repository.config.kiab.example.jsontemplate.KEEPER_SERVERinstead of baking an endpoint into the image.Runtime configuration
The image does not bake in cloud or KiaB endpoints. Operators provide a config file or
KEEPER_SERVERat runtime. KiaB can mount a config containinglocal.keepersecurity.com; cloud deployments can use the default or a normal Commander config.