Closed prashima closed 7 years ago
One more addition-
Some more commands made to this list:
For following commands no cloud provider is getting queried. So it's not possible to decide if a command is meant for vSphere. Additional parameters will have to be added to identify vSphere cloud provider.
https://github.com/vmware/kops/commit/ed42a932d175cd235a013a846735200a5ae0a7df fixes this issue, by supplying correct error message.
Commands discussed in comment above this one are yet to be fixed
Reduced priority, since the fix is available for common used commands. The remaining 4 commands don't get used very frequently. So a mention in doc will also do for now, in my opinion.
Filed https://github.com/kubernetes/kops/issues/2421 for 'import cluster' command.
For now, following commands will have to be documented as unsupported. I don't see any other way around to put a check for vSphere cloud provider, just for the duration for which they won't be supported.
Closing this issue. Will file a separate issue for documentation.
Fail gracefully for vsphere cloud provider, while executing following kops commands-
update cluster(filing a separate issue)'edit' and 'update' commands for federation are yet to be investigated. They might also make to this list.