Open chasinglogic opened 2 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I guess bump to stop the stale bot?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I'd be willing to put a PR up for this if there was acknowledgement that it would get accepted as a valid change. Just don't wanna go through the trouble to find out that this is something the project doesn't want to support.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
hi @chasinglogic sry for not answering this earlier,
this is definitely something that is useful and if you are wiling to do a PR that would be appreciated. (we can also back-port it to previous versions)
When using Google Kubernetes Engine auto upgrade feature GKE will monitor your cluster for use of deprecated APIs and warn you if you are. It will also prevent the upgrade until you remove the usage of those APIs.
We recently went through this process and updated all of our Ingresses to
networking.k8s.io/v1
from thev1beta1
and now HAProxy's ingress controller is still pollingv1beta1
and causing GKE to believe we are relying on deprecated APIs:It would be ideal if we could turn off this backwards compatibility or somehow set which APIs to poll so that we can use the GKE auto upgrade feature.