Skip to content
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

helm: Remove default cpu limit inside chart #4290

Merged
merged 2 commits into from
Oct 22, 2024

Conversation

RomainBelorgey
Copy link
Contributor

What type of PR is this?

  • fix: allow to have no cpu limit when chart used as dependency

What this PR does / why we need it:

  • Removing the default cpu limit as can't be removed if used as dependency
  • CPU limit should be removed on every deployment (not requests)
    #1
    #2
    #3
  • Other examples / writings can be found around that, still possible for someone to add back the cpu limit

Which issue(s) this PR fixes:

Fixes #

Copy link

codecov bot commented Sep 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.02%. Comparing base (544bd9c) to head (a6af418).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4290      +/-   ##
==========================================
+ Coverage   65.95%   66.02%   +0.07%     
==========================================
  Files         203      203              
  Lines       31154    31154              
==========================================
+ Hits        20547    20569      +22     
+ Misses       9420     9403      -17     
+ Partials     1187     1182       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@nezdolik
Copy link
Member

@arkodg currently is not possible to have cpu limit empty(unlimited), since value of 500m gets merged from parent chart. This is our values.yaml:

      resources:
        limits:
          memory: 1024Mi
        requests:
          cpu: 500m
          memory: 256Mi

This is the resulting config of a running pod:

    Limits:
      cpu:     500m
      memory:  1Gi
    Requests:
      cpu:      500m
      memory:   256Mi

@arkodg
Copy link
Contributor

arkodg commented Sep 23, 2024

hey @RomainBelorgey good to see you here :)
can you run make generate && make testdata && make manifests and commit those changes ?

@arkodg arkodg requested a review from a team September 23, 2024 22:02
@arkodg arkodg added the release-note Indicates a required release note label Sep 23, 2024
@RomainBelorgey
Copy link
Contributor Author

hey @RomainBelorgey good to see you here :) can you run make generate && make testdata && make manifests and commit those changes ?

Good to see you too :)

Thanks, I just run these commands and pushed the changes

@zirain zirain changed the title Fix: Remove default cpu limit inside chart helm: Remove default cpu limit inside chart Sep 24, 2024
arkodg
arkodg previously approved these changes Sep 25, 2024
@@ -9347,10 +9347,6 @@ spec:
partition: 0
serviceName: loki-headless
revisionHistoryLimit: 10

persistentVolumeClaimRetentionPolicy:
Copy link
Contributor

Choose a reason for hiding this comment

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

curious why this is deleted
this is why make gen-check is failing

@arkodg arkodg self-requested a review September 25, 2024 00:37
@zirain
Copy link
Contributor

zirain commented Sep 30, 2024

@RomainBelorgey can you address arko's comment?

@RomainBelorgey
Copy link
Contributor Author

Sorry got sidetracked to something else 😅
I readded manually persistentVolumeClaimRetentionPolicy on the 2 files where it was removed. Hope that it will fix the check

@arkodg
Copy link
Contributor

arkodg commented Oct 10, 2024

np @RomainBelorgey, I suggest rerunning 'make generate' and commiting those change or looking at the CI to see which test files you've missed and editing them

@arkodg arkodg added this to the v1.2.0-rc1 milestone Oct 15, 2024
@zirain
Copy link
Contributor

zirain commented Oct 22, 2024

@RomainBelorgey can you fix this, want to land this in v1.2.

Signed-off-by: Romain BELORGEY <romain.belorgey@docker.com>
@RomainBelorgey
Copy link
Contributor Author

@RomainBelorgey can you fix this, want to land this in v1.2.

Normally fixed 🤞

Copy link
Contributor

@arkodg arkodg left a comment

Choose a reason for hiding this comment

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

LGTM thanks !

@arkodg arkodg requested review from a team October 22, 2024 18:09
@zirain zirain merged commit e24ada6 into envoyproxy:main Oct 22, 2024
26 of 27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note Indicates a required release note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants