Discovery of ConfigMaps and Label Selectors#761
Uh oh!
There was an error while loading. Please reload this page.
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.
ConfigMaps Discovery & Label Selectors
Business Value
These enhancements provide users with greater control and flexibility over Kubernetes resource discovery:
Changes
Feature 1: ConfigMap Discovery
Added ConfigMap resource type to the dynamic data gatherer:
configmapsinto the informer-based collection pipelineFeature 2: Label Selectors
Implemented label selectors for all resource types:
conjur.org/name=conjur-connect-configmapis set for ConfigMap resources.How to test locally
go run . agent --one-shot --machine-hub -v 6 --agent-config-file ./examples/machinehub.yaml