LinkedIn
Twitter
I am working on switching our GKE fleet from using Multi Cluster Ingress to Multi Cluster Gateways. So far I've followed this tech docs to set it up:
https://cloud.google.com/kubernetes-engine/docs/how-to/enabling-multi-cluster-gateways
https://cloud.google.com/kubernetes-engine/docs/how-to/multi-cluster-services#enable_mcs_project
https://cloud.google.com/kubernetes-engine/docs/how-to/deploying-multi-cluster-gateways#deploy-gatew...
I got no errors and was able to execute the required steps (enable missing APIs and Gateway API at config cluster. Most of the other stuff like permissions was already set when MCI was first configured). However, Gatewayclasses are only showing Cluster Gateway resources:
There's no multi cluster gateway classes whatsoever. I took a deep dive into documentation and the closest match I found was this:
- There is a known issue with the multi-cluster Gateway controller where it may fail to start. To avoid this issue, enable the Gateway API on the config cluster and include the CRDs before the Fleet ingress feature is enabled.
Such workaround is impossible for me since this is a production environment, with a whole fleet already created and working.
