Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Deprecated apiVersion on generated Ingress resources

See original GitHub issue

Bug

I’m unable to start any services with ingress specified. Garden will receive the trying to run deploy the project in minikube. The same project was working on older garden versions.

Current Behavior

garden dev

Command "/home/aloise/.garden/tools/kubectl/11ac0bbd21058c50/kubectl --context=minikube --namespace=easyrentals-default apply --prune --selector service=gateway --output=json -f -" failed with code 1:

Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": an error on the server ("") has prevented the request from succeeding

Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": an error on the server ("") has prevented the request from succeeding

Expected behavior

It was running on older garden + k8s versions.

Reproducible example

Any project which has ingress is failing.

Workaround

Your environment

OS: Arch Linux, 5.12.1
minikube v1.19.1 + k8s v1.20.2
garden v0.12.21

Issue Analytics

State:
Created 2 years ago
Comments:7

Top GitHub Comments

1reaction

Cpcrookcommented, Dec 3, 2021

With the latest (4.3.0) release of Docker Desktop on 2021/12/02 (which includes Kubernetes 1.22.x) this issue appears to be rearing it’s head.

1reaction

eysi09commented, May 13, 2021

Ok happy to hear that. But the point stands that we should update the ingress api version on our end. It should be a quick fix.

Top Results From Across the Web

Deprecated API Migration Guide - Kubernetes

Migrate manifests and API clients to use the networking.k8s.io/v1 API version, available since v1.19. All existing persisted objects are ...

Kubernetes 1.22 deprecated APIs - Google Cloud

This page provides information on the deprecated APIs in the Kubernetes 1.22 release. For more detailed information, see the Kubernetes deprecated API ...

Keeping Track of Kubernetes Deprecated Resources - SUSE

Check for Kubernetes resource deprecations and removals with this new Kubewarden deprecated-api-versions policy.

Will the existing service(using deprecated Ingress api) affects ...

Hi All,. We are currently running AKS v1.21.2 and some of our services are exposed via Ingress(using networking.k8s.io/v1beta1), as per the ...

kubernetes - disable deprecated resource automatic conversion

This is the created resource on cluster, as you can see, the apiVersion is not the same… apiVersion: networking.k8s.io/v1 kind: Ingress metadata ...