Could you update your document about ingress-nginx install

[wss29]

hi,
Your document about installing ingress-nginx is a little out of date. Simply setting allow-snippet-annotations to true is no longer sufficient to enable the nginx.ingress.kubernetes.io/configuration-snippet annotation. I struggled for several days trying to understand why allow-snippet-annotations: "true" didn't work when installing my-theia-cloud component, until I finally found the answer on ingress-nginx issure

using follow commands can avoid configuration-snippet annotation error when install my-theia-cloud

helm upgrade --install ingress-nginx ingress-nginx \
 --repo https://kubernetes.github.io/ingress-nginx \
 --namespace ingress-nginx --create-namespace \
 --set controller.config.allow-snippet-annotations="true" \
 --set controller.config.annotations-risk-level="Critical"

This can be a headache for new users, especially when they follow the ingress-nginx Helm installation guide directly and then proceed to install my-theia-cloud. so if possible, could you update your document about the ingress-nginx install?

Aside from the previous issue, only one problem is left when installing the my-theia-cloud component. As shown in the image

I'm encountering the error: path /trynow(/|$)(.*) cannot be used with pathType Prefix. Is this related to the Kubernetes or ingress-nginx version? The issue originates from the landing-page-ingress-path-based.yaml file, but I don't know how to resolve it. I've already opened a discussion on GitHub #392. This is the final step to getting Theia-Cloud working, so any help would be greatly appreciated."
my current Kubernetes version is 1.31.0,

[jfaltermeier]

Hi, Thanks for reporting this. We haven’t updated to the latest 1.12 NGINX ingress controller in our demo/tests setups yet. The safest versions for Theia Cloud compatibility can be found in our Terraform configurations: https://github.com/eclipse-theia/theia-cloud/blob/main/terraform/modules/helm/main.tf#L107.
We typically update versions around the time of a new release, so this new NGINX ingress release is too recent for our current setup.

It seems the 1.12 release of the nginx ingress controller introduces some breaking changes, including the issue you reported and this one here: kubernetes/ingress-nginx#12637, which appears similar to your report.
This can be disabled for now: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#strict-validate-path-type

We will update our guides soon

[wss29]

hi @jfaltermeier
Thank you so much for your help with the pathType: Prefix issue. Could you provide me with a modified theia-cloud binary? I would like to test our product on theia.cloud. If it will take a long time for a new release, or if you cannot provide me with a temporary theia-cloud binary, would it be possible for me to directly change the pathType to ImplementationSpecific in the landing-page-ingress-path-based.yaml file and package it myself?