default-backend | A default backend for nginx-ingress in Kubernetes | Runtime Evironment library

We performed our kubernetes cluster upgrade from v1.21 to v1.22. After this operation we discovered that our nginx-ingress-controller deployment’s pods are failing to start with the following error message: pkg/mod/k8s.io/client-go@v0.18.5/tools/cache/reflector.go:125: Failed to list *v1beta1.Ingress: the server could not find the requested resource

We have found out that this issue is tracked over here: https://github.com/bitnami/charts/issues/7264

Because azure doesn't let to downgrade the cluster back to the 1.21 could you please help us fixing the nginx-ingress-controller deployment? Could you please be specific with what should be done and from where (local machine or azure cli, etc) as we are not very familiar with helm.

This is our deployment current yaml:

I'm trying to add an NGINX Ingress controller on a GKE cluster, with existing HAProxy Ingress controller (which has some problem with rewriting rules)

First I tried to expose the controller's Service to LoadBalancer type. The traffic can reach ingress and backends, but it didn't work with Managed Certificates.

So I tried to use L7 Load Balancer (URL Map) to forward traffic to GKE cluster IP, and create an Ingress object for my ingress controller itself.

The problem is, this Ingress object seems not bound to external IP. And routing to the domain yields "default backend - 404" response.

I have created a kubernetes cluster using Vagrant. I created a Nginx pod and a Cluster IP service for it. I can curl both the pod and the service getting a successful result. I have now installed an Nginx Ingress Controller from: https://kubernetes.github.io/ingress-nginx/deploy/#bare-metal-clusters and ran the following command: kubectl create ingress nginxingress --rule="/nginx=nginx-service:80" --annotation nginx.ingress.kubernetes.io/rewrite-target=/ --default-backend=nginx-service:80 and they both have been setup correctly as far as I see as there are no errors. But whenever I try to curl the path then it fails, the controller keeps throwing a 404 Not found. Some more information that might help:
services:
ingresses:

any help will be greatly appreciated

I'm trying to apply a terraform resource (helm_release) to k8s and the apply command is failed half way through.

I checked the pod issue now I need to update some values in the local chart.

Now I'm in a dilemma, where I can't apply the helm_release as the names are in use, and I can't destroy the helm_release since it is not created.

Seems to me the only option is to manually delete the k8s resources that were created by the helm_release chart?

Here is the terraform for helm_release:

I try to test Kubernetes Ingress on Minikube. My OS is Windows 10. Minikube is installed successfully as well as Nginx ingress controller.

I created an .exe file using pyinstaller. When I run it on Pycharm, it works perfectly. But when I try to run the executable an error occurs.

Here's the full error:

I have an ongoing requirement to patch my nginx-ingress daemonset each time I wish to expose new TCP ports. I have reviewed the documentation and I cannot understand the correct kubectl patch syntax to perform the patch. An excerpt from the yaml follows:

I have created an ingress controller using Helm with default configuration

I am trying to setup Horizontal Pod Autoscaler to automatically scale up and down my api server pods based on CPU usage.

I currently have 12 pods running for my API but they are using ~0% CPU.