-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validate that require-kubeconfig is not passed after 1.10 #5621
Conversation
This should alert users that are manually specifying old flags - I suspect that a few of the upgrade failures are due to users that are running with clusters captured from `kops get cluster --full`, and this will detect that. Issue kubernetes#5459
7af88e3
to
e10124e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
is the beginning of a more centralized effort to better handle deprecated flags?
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: geojaz, justinsb The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@geojaz that's a good idea! Having a few verifications in each release to warn people. If we do I think we'd want some helper functions though! |
Cherry pick of #5621 onto release-1.10
* Starting support of kubernetes v1.10 * Starting support for kops-v1.10 * Remove missplaced comment * ClusterSpec : Remove 'requireKubeconfig' (removed since kops-1.10 of kubernetes/kops#5621)
This should alert users that are manually specifying old flags - I
suspect that a few of the upgrade failures are due to users that are
running with clusters captured from
kops get cluster --full
, andthis will detect that.
Issue #5459