Skip to content

Fix for autoscale on k8s-1.9+ without breaking manual scaling - #106

Merged
Cryptophobia merged 18 commits into
teamhephy:masterfrom
Cryptophobia:ess-fix-autoscale-take-2
Aug 8, 2019
Merged

Cryptophobia merged 18 commits into
teamhephy:masterfrom
Cryptophobia:ess-fix-autoscale-take-2

Conversation

@Cryptophobia

Copy link
Copy Markdown
Member

This takes care of scheduler init and scaling RBAC permissions temporary fix started by #104. Thank you @ess!

Tested on AWS and GKE.

@kingdonb kingdonb left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks for fixing this up! LGTM

ess and others added 4 commits August 5, 2019 17:58
This functionality now lives in KubeHTTPClient, so
it is unnecessary to mutate the reported k8s API
version in the deployment resource.
Refactoring for new KubeHTTPClient.version() behavior
Kingdon Barrett added 2 commits August 8, 2019 10:45
Upgrading to apps/v1 requires changes to the way that Scale action is
called, and as we haven't understood this change yet, we will depend on
the older version of Deployment api to remain available until we do.

includes these squashed commits:
* WIP: this commit is probably wrong
* WIP: this seems more likely to work
* WIP: hardcode extensions/v1beta1 here for now

There is no "App.api_version" attribute and I'm not sure where this
information should come from

* fixup: line was too long for the style guide
@Cryptophobia Cryptophobia changed the title Fix for autoscale on k8s-1.9+ Fix for autoscale on k8s-1.9+ without breaking manual scaling Aug 8, 2019
@Cryptophobia
Cryptophobia merged commit 273a5f8 into teamhephy:master Aug 8, 2019
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