Skip to content
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.

Sign up for GitHub

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

Jump to bottom

cluster verification #155

Closed
errordeveloper opened this issue Aug 9, 2018 · 3 comments
Closed

cluster verification #155

errordeveloper opened this issue Aug 9, 2018 · 3 comments
Labels
area/general-cli area/upgrades kind/feature New feature or request

Comments

@errordeveloper
Copy link
Contributor

It'd be neat to have some form of verification. This could come especially useful for troubleshooting in general, but also when user supplies any customisation (e.g. #69). This could also incorporate whatever we do in #151.
@errordeveloper
Copy link
Contributor Author

Kops has some kind of verification functionality, we should look into what it does.

@errordeveloper errordeveloper mentioned this issue Aug 9, 2018
Merged
11 tasks
@errordeveloper
Copy link
Contributor Author

I think comes helpful in the context of upgrades, and as more general form of some of the same concerns that #539 is meant to address.

@errordeveloper errordeveloper mentioned this issue May 1, 2019
Closed
@errordeveloper errordeveloper added the kind/feature New feature or request label May 1, 2019
@kalbir
Copy link

kalbir commented May 25, 2020

Closing as #587 better covers the problem IMO (and this is referenced there).

@kalbir kalbir closed this as completed May 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/general-cli area/upgrades kind/feature New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@errordeveloper @kalbir