search

GoogleCloudPlatform / gke-networking-recipes

Apache License 2.0
307 stars 85 forks source link

networking.gke.io/v1 FrontendConfig availability #116

Closed ryan-jan closed 1 year ago

ryan-jan commented 1 year ago

Hi, I'm not sure if this is the right place to ask but hopefully you can at least point me in the right direction. I'm currently using the networking.gke.io/v1beta1.FrontendConfig annotation in an ingress and am receiving a deprecated API warning on my clusters. The clusters are running 1.21.14-gke.4300.

Following the guidance here I've upgraded the development cluster to v1.22.15-gke.1000 and have tested that I can still use networking.gke.io/v1beta1.FrontendConfig by destroying and recreating. This is working fine. However, I've now started looking at how to move to networking.gke.io/v1.FrontendConfig and cannot seem to find any information on this at all? I've tried simply changing the api version to v1 but the cluster throws an error telling me it is not available.

I can only think that the reason it has been published that the beta APIs will remain available for upgraded 1.22 clusters is because the FrontendConfig resource does not yet exist in networking.gke.io/v1, is this the case?

My main question is what is the best course of action for us to take in this situation to move to off of this v1beta1 api and ultimately unlock the 1.23 upgrade?

Thanks in advance and apologies again if this is not the right place to ask this.

boredabdel commented 1 year ago

Hi,

The FrontendConfig CRD is only available under networking.gke.io/v1beta1.

So even if you upgrade your cluster to a newer version. networking.gke.io/v1beta1.FrontendConfig will remain the annotation you use to associate a FrontendConfig object with an Ingress