You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
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:
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):
Create cluster with "orchestratorRelease": "1.9",
Upgrade cluster to 1.11.0-rc.3 using the acs-engine upgrade command
Scale cluster using acs-engine scale command
Anything else we need to know:
The text was updated successfully, but these errors were encountered:
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
tov.1.11.x
I get the following error: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):
"orchestratorRelease": "1.9",
1.11.0-rc.3
using theacs-engine upgrade
commandacs-engine scale
commandAnything else we need to know:
The text was updated successfully, but these errors were encountered: