feat(operator): add karmor.yaml into kubearmor configmap #1949
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
tesla59
force-pushed
the
tesla/config-watcher
branch
from
cb142be to
2e58b43
Compare
Aryan-sharma11
force-pushed
the
tesla/config-watcher
branch
from
2e58b43 to
bf21d83
Compare
Signed-off-by: tesla59 <[email protected]>
tesla59
force-pushed
the
tesla/config-watcher
branch
from
bf21d83 to
dd6ae7c
Compare
Signed-off-by: tesla59 <[email protected]>
Signed-off-by: tesla59 <[email protected]>
…gmap data Signed-off-by: tesla59 <[email protected]>
tesla59
force-pushed
the
tesla/config-watcher
branch
from
7238b26 to
4cc9231
Compare
Rudra-Sankha-Sinhamahapatra
suggested changes
Mar 16, 2025
tesla59
force-pushed
the
tesla/config-watcher
branch
from
7b6c3ae to
4cc9231
Compare
|
@Rudra-Sankha-Sinhamahapatra hey. the checks are now passing |
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.
Purpose of PR?:
Introduces a new field
karmor.yamlin the ConfigMapkubearmor-configcreated by KubeArmor Operator. This field can be mounted into KubeArmor Pods so that the configuration can be done by Viper, deprecating Config Watcher in KubeArmorFixes #1920
Does this PR introduce a breaking change?
Configuration using
karmor.yamlwill eventually replace the other fields in the config mapIf the changes in this PR are manually verified, list down the scenarios covered::
Verified both fields in config map are having same values
Additional information for reviewer? :
Continuation of #1862
Checklist:
<type>(<scope>): <subject>