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.
Any suggestion on how to identify VMs to upgrade without relying on tags? Should it rely on VM names instead?
CecileRobertMichon
changed the title
Missing VM tags results in failed kubernetes upgrade
Missing VM tags results in failed kubernetes upgrade and scale
Sep 4, 2018
@serbrech I think for now even a simple check to make sure those tags exist before dereferencing them would help so that we can return a meaningful error ("expected tags "..." and "..." on VM "..." but no tags were found" or something like that) instead of panicking would be better.
Upgrade and scale should not rely on VM tags to determine k8s version during upgrade as those could easily be removed or modified.
https://github.com/Azure/acs-engine/blob/master/pkg/operations/kubernetesupgrade/upgradecluster.go#L200
https://github.com/Azure/acs-engine/blob/master/cmd/scale.go#L225
The text was updated successfully, but these errors were encountered: