Please add support for connecting to Anthos clusters hosted outside GCP via the connect gateway #257
Labels
enhancement
New feature or request
Comments
sethvargo
added a commit
that referenced
this issue
Dec 9, 2022
This PR changes the Connect Gateway builder to always lookup the given membership and determine if the resulting cluster is a GKE cluster. If it is a GKE cluster, it uses the /gkeMemberships collection endpoint. Otherwise, it uses the standard /memberships collection endpiont. It also drops the e2e test in favor of just using kubectl directly. - Closes #256 - Closes #245 - Closes #253 - Gets us closer to supporting #257
|
Just voicing that this would be very useful for myself as well. Thank you! |
|
We are not planning to implement this feature. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TL;DR
Hi, we have an Anthos cluster hosted on-prem that we can connect to using the connect gateway. It seems this action does not work in this scenario as it requires a cluster location to be specified. We have tried 'global' and 'registered' (which is what the location is listed as in GCP, see attached) but the action produces an error 'location does not exist'.
Detailed design
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: