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

docs: Improve Documentation for Scaledown on Aborted Rollout #3835

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

bishalthapa-t
Copy link
Contributor

@bishalthapa-t bishalthapa-t commented Sep 17, 2024

Improves understanding of how scaling down behaves depending on different configurations:

• Canary with traffic routing + setCanaryScale does not scales down immediately when abortScaleDownDelaySeconds = 0

• Canary with traffic routing + setCanaryScale scales down after some delay of N second abortScaleDownDelaySeconds = N

Addresses the following issue: #1841

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
  • The title of the PR is (a) conventional with a list of types and scopes found here, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
  • I've signed my commits with DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My builds are green. Try syncing with master if they are not.
  • My organization is added to USERS.md.

@bishalthapa-t bishalthapa-t changed the title Improve Documentation for Scaledown on Aborted Rollout docs: Improve Documentation for Scaledown on Aborted Rollout Sep 17, 2024
@bishalthapa-t bishalthapa-t force-pushed the bishalthapa-t/improve-doc-scaledown-on-aborted branch from c223de8 to bcfd6af Compare September 17, 2024 09:40
Copy link

codecov bot commented Sep 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.89%. Comparing base (b8a9bf5) to head (e5e5cbd).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3835      +/-   ##
==========================================
+ Coverage   83.88%   83.89%   +0.01%     
==========================================
  Files         163      163              
  Lines       18560    18560              
==========================================
+ Hits        15569    15571       +2     
+ Misses       2119     2118       -1     
+ Partials      872      871       -1     

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

Copy link
Contributor

github-actions bot commented Sep 17, 2024

Published E2E Test Results

  4 files    4 suites   3h 15m 1s ⏱️
113 tests 102 ✅  7 💤 4 ❌
458 runs  424 ✅ 28 💤 6 ❌

For more details on these failures, see this check.

Results for commit 7665aa8.

♻️ This comment has been updated with latest results.

Copy link
Contributor

github-actions bot commented Sep 17, 2024

Published Unit Test Results

2 275 tests   2 275 ✅  2m 59s ⏱️
  128 suites      0 💤
    1 files        0 ❌

Results for commit 7665aa8.

♻️ This comment has been updated with latest results.

Improves understanding of how scaling down behaves depending on different configurations.
 • Canary with traffic routing + setCanaryScale does not scales down immediately when `abortScaleDownDelaySeconds = 0`.
 • Canary with traffic routing + setCanaryScale scales down after some delay of N second `abortScaleDownDelaySeconds = N`.

Signed-off-by: Bishal Thapa <bishal.thapa@trustly.com>
@bishalthapa-t bishalthapa-t force-pushed the bishalthapa-t/improve-doc-scaledown-on-aborted branch from 999db8a to e5e5cbd Compare September 17, 2024 16:16
@zachaller zachaller self-assigned this Sep 18, 2024
Copy link

sonarcloud bot commented Sep 18, 2024

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.

2 participants