-
Notifications
You must be signed in to change notification settings - Fork 6.4k
feat: Enable ignoreResourceUpdate by default #19992 #20303
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
Conversation
❌ Preview Environment deleted from BunnyshellAvailable commands (reply to this comment):
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #20303 +/- ##
==========================================
+ Coverage 55.94% 55.99% +0.04%
==========================================
Files 322 322
Lines 44704 44704
==========================================
+ Hits 25011 25031 +20
+ Misses 17104 17077 -27
- Partials 2589 2596 +7 ☔ View full report in Codecov by Sentry. |
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!
Please also update documentation |
7ec5a37
to
daa992e
Compare
@crenshaw-dev I updated documentation. Thanks! |
# to resources are applied to the cluster cache. Default is true. | ||
resource.ignoreResourceUpdatesEnabled: "true" |
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.
Could you also update the docs in reconcile.md?
daa992e
to
04cb1f9
Compare
@crenshaw-dev I'm not sure if the option has been well explained, PTAL! |
04cb1f9
to
39a891b
Compare
Signed-off-by: jaehanbyun <awbrg789@naver.com>
39a891b
to
3bb5034
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.
Just needs to resolve feedback from Crenshaw but other than that 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. We discussed it a bit today in the SIG Scalability. I have been involved in monitoring the usage of this feature through slack and GitHub issues, i haven't seen any negative impact after enabling it with the default configurations.
Obviously, it still needs to be configured to improve the performance significantly. Perhaps 3.0 can include default configuration for known resources (#19992) so i don't think it fully closes the issue.
Let's bring it up at the next contributors meeting just in case, but it's safe to merge after that IMO.
@agaudreault Understood. Please let me know if there are any additional details related to this PR after the meeting. Thanks! |
…#20303) Signed-off-by: jaehanbyun <awbrg789@naver.com> Signed-off-by: austin5219 <3936059+austin5219@users.noreply.github.com>
…#20303) Signed-off-by: jaehanbyun <awbrg789@naver.com> Signed-off-by: Adrian Aneci <aneci@adobe.com>
Checklist:
What I have done: