They all use TLS. In my case I just wanted to drop the Operator into my basic cluster and quickly look at the Operator Console. I'm running RKE2 v1.28.2+rke2r1 with the built-in RKE2 Nginx add-on disabled and community ingress-nginx helm chart version 4.6.1, app version 1.7.1 installed instead with no special configs. I'm deploying the Minio operator helm chart with values:
Is it possible that the Nginx behavior referenced by all the tickets is only supported for HTTPS?
P.S. I've also tried omitting the nginx.ingress.kubernetes.io/use-regex: "true" annotation and setting pathType: Prefix and other things but - no luck.
Thanks.
UPDATED I just re-tried this workflow with cert-manager and a self-cigned cert on the ingress and experienced the same thing:
There are several issues/PRs in the repo talking about accessing the console behind Nginx:
They all use TLS. In my case I just wanted to drop the Operator into my basic cluster and quickly look at the Operator Console. I'm running RKE2 v1.28.2+rke2r1 with the built-in RKE2 Nginx add-on disabled and community ingress-nginx helm chart version 4.6.1, app version 1.7.1 installed instead with no special configs. I'm deploying the Minio operator helm chart with values:
... based on the various tickets and other guidance I've been able to find.
Trying to access http://ip-10-104-22-233.myco.org/minio results in the redirects all looking for "root" urls. E.g.: http://ip-10-104-22-233.mycorp.org/styles/root-styles.css which the Ingress ignores. If I hand-modify that as a test for example to http://ip-10-104-22-233.mycorp.org/minio/styles/root-styles.css then:
P.S.: If
kubectl -n minio-operator port-forward svc/console 9090
then in the browser http://localhost:9090 redirects to http://localhost:9090/login and the page properly displays.Is it possible that the Nginx behavior referenced by all the tickets is only supported for HTTPS?
P.S. I've also tried omitting the
nginx.ingress.kubernetes.io/use-regex: "true"
annotation and settingpathType: Prefix
and other things but - no luck.Thanks.
UPDATED I just re-tried this workflow with cert-manager and a self-cigned cert on the ingress and experienced the same thing: