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

feat: rolling update one pod at a time, adjust k8s resources #48

Merged
merged 1 commit into from
Aug 26, 2024

Conversation

hasakura12
Copy link
Contributor

@hasakura12 hasakura12 commented Aug 21, 2024

Deployed

TEST

Deployed one at a time

pod/reflux-solver-6db4c868d6-cfmk5   1/1
  Running     0          3m29s
pod/reflux-solver-6db4c868d6-xkjk4   1/1
  Running     0          2m49s

pod metrics after deployment
Prod reflux-solver metrics AFTER

Describe your changes

  • rolling update one pod at a time to make sure maxUnavailable=0
  • lower CPU & memory requests & limit

Usage at peak in last 30 days:
Reflux-solver:

  • Memory: 50m
  • CPU: 0.01

Reflux-indexer usage:

  • memory: 20m
  • CPU: 0.001

Issue ticket number and link

Checklist before requesting a review

  • I have performed a self-review of my code
  • If it is a core feature, I have added thorough tests.
  • Do we need to implement analytics?
  • Will this be part of a product update? If yes, please write one phrase about this update.

@ankurdubey521 ankurdubey521 merged commit 0f1da54 into main Aug 26, 2024
9 checks passed
@hasakura12 hasakura12 deleted the hasakura12/feat-rolling-upgrade-max-surge-1 branch August 27, 2024 06:12
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.

3 participants