This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
Upgrade should change the apimodel to reflect changes applied to the cluster #2273
Assignees
Labels
Comments
ghost
added
the
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a request for help?:
NO
Is this an ISSUE or FEATURE REQUEST? (choose one):
ISSUE
What version of acs-engine?:
v0.12.5
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes
What happened:
When upgrade is run on a cluster the resulting apimodel should have the changes applied by upgrade. For example, if a 1.7.9 cluster is upgraded to 1.8.6, the apimodel should show
"orchestratorVersion":"1.8.6"after the upgrade. Right now, the changes are not added to the apimodel which means a second upgrade won't work.The text was updated successfully, but these errors were encountered: