We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I installed rancher desktop, enabled kubernetes, installed ingress as following:
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update helm upgrade --install nginx-ingress ingress-nginx/ingress-nginx --namespace ingress-nginx --create-namespace --values ./values.yaml
and the config of values.yaml is as following:
values.yaml
controller: extraArgs: enable-ssl-passthrough: true # config: # use-proxy-protocol: 'true' # use-forwarded-headers: 'true' # use-forward-headers: 'true' # compute-full-forward-for: 'true' # hostNetwork: true service: # type: "NodePort" externalTrafficPolicy: Local # externalTrafficPolicy: Cluster replicaCount: 1
No matter how much I tried or played with this, I cannot get any workaround to pass client real ip.
Please provide either documentation or way to help with this.
No response
The text was updated successfully, but these errors were encountered:
It is not clear to me what you are trying to achieve here. Ports are automatically forwarded to the host already.
Are you trying to replace the Traefik ingress controller? If yes, did you disable Traefik before you install nginx?
Anyways, please describe in more details what exactly you are trying to make happen!
Sorry, something went wrong.
No branches or pull requests
Problem Description
I installed rancher desktop, enabled kubernetes, installed ingress as following:
and the config of
values.yaml
is as following:No matter how much I tried or played with this, I cannot get any workaround to pass client real ip.
Proposed Solution
Please provide either documentation or way to help with this.
Additional Information
No response
The text was updated successfully, but these errors were encountered: