Run in standalone mode #553
Open
Conversation
This file contains 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.
Desired Outcome
The Conjur secret provider component can run as a standalone Kubernetes (K8s) deployment and periodically trigger the provisioning of Conjur secrets. Meanwhile, it reacts to every new or modified K8s secret and triggers provisioning only for that specific secret.
It would be good to introduce this feature along with #550
Implemented Changes
A new 'standalone' run mode is provided. The component periodically runs provisioning and updates target secrets. Additionally, a new HTTP server is exposed to handle registered Kubernetes (K8s) mutation webhooks. While provisioning runs automatically within the defined time period, the webhook ensures that every new or modified K8s secret is provisioned immediately.
Connected Issue/Story
DRAFT for:
#549