Skip to content

Conversation

jaehanbyun
Copy link
Member

@jaehanbyun jaehanbyun commented Oct 9, 2024

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Toolchain Guide
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

What I have done:

  • Enable ignoreResourceUpdate by default

@jaehanbyun jaehanbyun requested a review from a team as a code owner October 9, 2024 05:19
Copy link

bunnyshell bot commented Oct 9, 2024

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

  • 🚀 /bns:deploy to deploy the environment

Copy link

codecov bot commented Oct 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.99%. Comparing base (82484ce) to head (3bb5034).
Report is 395 commits behind head on master.

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.
📢 Have feedback on the report? Share it here.

Copy link
Member

@nitishfy nitishfy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@crenshaw-dev
Copy link
Member

Please also update documentation

@jaehanbyun jaehanbyun requested a review from a team as a code owner October 9, 2024 15:50
@jaehanbyun
Copy link
Member Author

jaehanbyun commented Oct 9, 2024

@crenshaw-dev I updated documentation. Thanks!

Comment on lines +110 to +111
# to resources are applied to the cluster cache. Default is true.
resource.ignoreResourceUpdatesEnabled: "true"
Copy link
Member

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?

@jaehanbyun
Copy link
Member Author

@crenshaw-dev I'm not sure if the option has been well explained, PTAL!

Signed-off-by: jaehanbyun <awbrg789@naver.com>
Copy link
Member

@christianh814 christianh814 left a 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

Copy link
Member

@agaudreault agaudreault left a 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.

@jaehanbyun
Copy link
Member Author

@agaudreault Understood. Please let me know if there are any additional details related to this PR after the meeting. Thanks!

@agaudreault agaudreault enabled auto-merge (squash) October 10, 2024 16:38
@agaudreault agaudreault merged commit 8ebf4a8 into argoproj:master Oct 10, 2024
28 checks passed
austin5219 pushed a commit to austin5219/argo-cd that referenced this pull request Oct 16, 2024
…#20303)

Signed-off-by: jaehanbyun <awbrg789@naver.com>
Signed-off-by: austin5219 <3936059+austin5219@users.noreply.github.com>
adriananeci pushed a commit to adriananeci/argo-cd that referenced this pull request Dec 4, 2024
…#20303)

Signed-off-by: jaehanbyun <awbrg789@naver.com>
Signed-off-by: Adrian Aneci <aneci@adobe.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants