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
Currently we have a contract between kubeconfig and clusters managed by airshipctl, that cluster name MUST correspond to cluster name.
For easier management I propose that we allow users to specify kubeconfig context per cluster in ClusterMap object, and adding corresponding method to ClusterMap interface in pkg/cluster/clustermap
This would allow for easier merging of kubeconfig into document set, and easier to bring external kubeconfigs to airshipctl.
Default behavior would be still to use cluster name, if context is not specified
The text was updated successfully, but these errors were encountered:
Currently we have a contract between kubeconfig and clusters managed by airshipctl, that cluster name MUST correspond to cluster name.
For easier management I propose that we allow users to specify kubeconfig context per cluster in ClusterMap object, and adding corresponding method to ClusterMap interface in pkg/cluster/clustermap
This would allow for easier merging of kubeconfig into document set, and easier to bring external kubeconfigs to airshipctl.
Default behavior would be still to use cluster name, if context is not specified
The text was updated successfully, but these errors were encountered: