X-Controller | simple Node.js remote access tool | Runtime Evironment library

In this situation, For me, this method always works. At first go to your container and then use these commands:

As @Brian de Alwis pointed out in the comments section, this PR #11189 should resolve the above issue.

You can try the v1.20.0-beta.0 release with this fix. Additionally, a stable v1.20.0 version is now available.

We tried with another Ingress Controller i.e. https://github.com/nginxinc/kubernetes-ingress and were able to make it work .

Below were the steps done .

Ref: Expecting apiVersion - networking.k8s.io/v1 instead of extensions/v1beta1

TL;DR

kubectl explain predated a lot of the generic resource parsing logic, so it has a dedicated --api-version flag. This should do what you want.

From the image you posted of the nginx-port-forward, I see you went on localhost:9443 directly, which means the Nginx server you are trying to access serve its content under /

But in the ingress definition, you define that the service will be served with path: /my-nginx. This could be the problem, as you are requesting https://example.com/my-nginx which will basically go to my-nginx:9443/my-nginx and, depending on the Pod behind this service, it could return a 404 if there's nothing at that path.

To test if the problem is what I specified above, you have a few options:

• easiest one, remove path: /my-nginx an, instead, go with path: /. You could also specify pathType: Prefix which means that everything matching the subPath specified will be served by the service.
• Add a rewrite target, which is necessary if you want to serve a service at a different path from the one expected by the application.

Add an annotation similar to the following:

As indicated in the question comments and in the question itself, very well documented by @vladzam, two are the reasons of the problem.

On one hand, the nginx ingress controller available through the Helm stable channel seems to be deprecated in favor of the new ingress-nginx controller - please, see the Github repo and the official documentation.

On the other, it seems to be a problem related to the definition of the Rewrite target annotation. According to the docs:

Starting in Version 0.22.0, ingress definitions using the annotation nginx.ingress.kubernetes.io/rewrite-target are not backwards compatible with previous versions. In Version 0.22.0 and beyond, any substrings within the request URI that need to be passed to the rewritten path must explicitly be defined in a capture group.

As a consequence, it is necessary to modify the definition of the ingress resource to take into account this change. For instance:

You should be able to do this with the correct rewrite-rule and path pattern:

From within cluster this link should work - http://.:port in your case it will be - http://cheese-svc.default:80

To access it from outside, the service is accessible on nodePort 30635 http://10.106.203.73:30635

This issue was solved recently. Here is more information: https://github.com/prometheus-community/helm-charts/issues/467 and here: https://github.com/prometheus-community/helm-charts/pull/757

Here is the solution (https://github.com/prometheus-community/helm-charts/issues/467#issuecomment-802642666):

[you need to] opt-out the rootfs host mount (preventing the crash). In order to do that you need to specify the following value in values.yaml file: