clusters apply fails if context name has underscore #61
GKE clusters typically have underscore in them (ie.
Workaround is to rename contexts - context - name in
The text was updated successfully, but these errors were encountered:
This made me recall that when I was setting up that GKE demo, I did indeed edit my
Another way to solve this is to do something like this in your
managementClusters: - name: my-management-cluster context: gke_ACCOUNT_ZONE_CLUSTERNAME_FOR_MANAGEMENT applicationClusters: - name: my-application-cluster context: gke_ACCOUNT_ZONE_CLUSTERNAME_FOR_WORKLOAD
This way Shipper will use
In terms of making this obvious going forward, I think the easiest thing would be for us to put that regex in
Does that sound sensible to you?
shipperctl's usage of the context name for the Cluster object fails if that context name is not an acceptable Kubernetes object name, as is the case in GKE clusters and their underscores. This helps people work around the issue in #61, but a better fix will be for shipperctl to give immediate feedback when it detects that issue.