fix(operator): update relay env vars with initial config #1893
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
rksharma95
requested review from
daemon1024,
DelusionalOptimist and
rootxrishabh
Signed-off-by: rksharma95 <[email protected]>
rksharma95
force-pushed
the
fix-bug-1866
branch
from
2604066 to
e420327
Compare
DelusionalOptimist
approved these changes
Nov 26, 2024
daemon1024
approved these changes
Nov 28, 2024
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?:
PR fixes the bug in the operator that it was ignoring the initial configurations provided using kubearmorconfig for kubearmor-relay deployment.
Fixes #1866
Does this PR introduce a breaking change?
No
If the changes in this PR are manually verified, list down the scenarios covered::
verified that operator consider initial configuration provided during helm install and overridden values for
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>