-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix existing client secret check #676
Fix existing client secret check #676
Conversation
Welcome @orange-llajeanne! It looks like this is your first PR to falcosecurity/charts 🎉 |
Hi @orange-llajeanne, thanks for the PR. Could you please rebase on main? |
Signed-off-by: Loïc Lajeanne <[email protected]>
Signed-off-by: Loïc Lajeanne <[email protected]>
2ff8a22
to
41c3254
Compare
@alacuku Hi, I've rebased my branch and updated the version number |
@orange-llajeanne, it would help if you run a |
Signed-off-by: Loïc Lajeanne <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alacuku, orange-llajeanne The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
LGTM label has been added. Git tree hash: f1a67d6f4487f65d658fe3cac7509629a1b6cc99
|
What type of PR is this?
/kind bug
/kind chart-release
Any specific area of the project related to this PR?
/area falco-chart
What this PR does / why we need it:
This PR fixes a check in the falco pod template, which uses the
existingSecret
variable instead ofexistingClientSecret
when deciding if client secrets are enabled.The consequence was that the chart would not work correctly when defining
existingSecret
but notexistingClientSecret
: it would try to attach an unexisting configmap to falco podsChecklist