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

Don't downscale the current stack even if it has no traffic #71

Merged
merged 1 commit into from Oct 17, 2018

Conversation

aermakov-zalando
Copy link
Contributor

This allows the deployment to proceed even if the users set a short TTL. A downside is that they'll have a deployment which doesn't do anything if they decide to go back to a previous version, but it looks like an acceptable trade-off.

Signed-off-by: Alexey Ermakov <alexey.ermakov@zalando.de>
@coveralls
Copy link

Pull Request Test Coverage Report for Build 251

  • 0 of 16 (0.0%) changed or added relevant lines in 2 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.2%) to 30.144%

Changes Missing Coverage Covered Lines Changed/Added Lines %
controller/stack.go 0 4 0.0%
controller/stackset.go 0 12 0.0%
Totals Coverage Status
Change from base Build 249: -0.2%
Covered Lines: 441
Relevant Lines: 1463

💛 - Coveralls

@mikkeloscar
Copy link
Contributor

Seems like a reasonable trade-off to me.

@mikkeloscar
Copy link
Contributor

👍

1 similar comment
@aermakov-zalando
Copy link
Contributor Author

👍

@aermakov-zalando aermakov-zalando merged commit 54ccc78 into master Oct 17, 2018
@aermakov-zalando aermakov-zalando deleted the avoid-downscaling-current-stack branch October 17, 2018 14:32
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.

None yet

3 participants