Proposal to change how kops performs validation during rolling-updates

[dskatz]

/kind feature

The kops validation checks that are performed during rolling-update procedures tend to timeout on kubernetes clusters that are dynamically sized frequently. The dynamic nature of the work causes kops validation to fail because those nodes entering or leaving will essentially be in a NotReady state.

This request is to start the conversation on potential changes to how kops performs validation checks or if there is a different approach managing dynamic clusters with kops.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale