-
Notifications
You must be signed in to change notification settings - Fork 762
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: Add flag to enable/disable referential constraints #3701
base: master
Are you sure you want to change the base?
fix: Add flag to enable/disable referential constraints #3701
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3701 +/- ##
==========================================
- Coverage 54.49% 47.56% -6.93%
==========================================
Files 134 236 +102
Lines 12329 19923 +7594
==========================================
+ Hits 6719 9477 +2758
- Misses 5116 9553 +4437
- Partials 494 893 +399
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
bfe0234
to
7008f88
Compare
… by default. Signed-off-by: David-Jaeyoon-Lee <[email protected]>
Signed-off-by: David-Jaeyoon-Lee <[email protected]>
7008f88
to
9de4ad9
Compare
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.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no suggestions.
Comments skipped due to low confidence (1)
main.go:119
- [nitpick] The description for the flag 'enable-referential-rules' is too long and may be confusing. Consider simplifying it to: 'Enable referential rules. Note: Referential constraints may not always be perfectly enforced due to Kubernetes controller consistency.'
enableReferential = flag.Bool("enable-referential-rules", true, "Enable referential rules. Only use this flag if you know what you're doing; referential rules have edge cases where referential constraints may not be perfectly enforced due to the eventual consistency inherent in Kubernetes controllers")
Signed-off-by: David-Jaeyoon-Lee <[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
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.
What this PR does / why we need it:
This allows gatekeeper to set if referential constraints are enabled to disabled via a flag
Which issue(s) this PR fixes (optional, using
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when the PR gets merged):Fixes #
Special notes for your reviewer: