-
Notifications
You must be signed in to change notification settings - Fork 38
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
feat: allow setting mutating webhook failurepolicy and objectSelector via helm #715
base: main
Are you sure you want to change the base?
Conversation
fixes open-feature#654 Signed-off-by: Marco Orovecchia <[email protected]>
651fd1c
to
92a5d3d
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #715 +/- ##
==========================================
- Coverage 86.51% 86.25% -0.26%
==========================================
Files 19 19
Lines 1587 1681 +94
==========================================
+ Hits 1373 1450 +77
- Misses 173 184 +11
- Partials 41 47 +6 see 3 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more. |
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.
Looks good, thanks.
Thanks @Oro for the PR 🙌 |
Signed-off-by: Marco Orovecchia <[email protected]>
e635000
to
0d59028
Compare
This PR
This makes it possible to configure new pods to wait until the webhook is available. Otherwise pods will start and not get mutated, i.e. will be missing the flagd sidecar.
The objectSelector is needed so that the webhook itself can still start up as otherwise it would fail while waiting on itself.
Related Issues
Fixes #654