Skip to content
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.

Scaling a cluster after a kubernetes upgrade #3478

Closed
BrendanThompson opened this issue Jul 16, 2018 · 0 comments · Fixed by #3482
Closed

Scaling a cluster after a kubernetes upgrade #3478

BrendanThompson opened this issue Jul 16, 2018 · 0 comments · Fixed by #3482
Assignees

Comments

@BrendanThompson
Copy link

BrendanThompson commented Jul 16, 2018

Is this a request for help?:


Is this an ISSUE or FEATURE REQUEST? (choose one):

FEATURE REQUEST

What version of acs-engine?:

v0.19.1

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes v1.9.x -> v1.11.x

What happened:

When attempting to scale the cluster after performing an upgrade from v1.9.x to v.1.11.x I get the following error:
image

And the cluster won't scale properly. For all intents and purposes the agent pool scales, but it gets that error. Obviously not something useable unfortunately.

If however, I scale the cluster prior to an upgrade it works fine. Although it means that once an upgrade has occurred it cannot be scaled again.

What you expected to happen:
Expect to be able to scale a cluster after an upgrade has occurred.

How to reproduce it (as minimally and precisely as possible):

  1. Create cluster with "orchestratorRelease": "1.9",
  2. Upgrade cluster to 1.11.0-rc.3 using the acs-engine upgrade command
  3. Scale cluster using acs-engine scale command

Anything else we need to know:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants