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 have 2 ingress for the same domain and apparently after PR #517 nginx generate a wrong whitelist-source-range.
apiVersion: v1 items: - apiVersion: extensions/v1beta1 kind: Ingress metadata: annotations: ingress.kubernetes.io/whitelist-source-range: 23.135.13.124/32 kubernetes.io/ingress.class: extern name: acl namespace: xxx spec: rules: - host: my.staging.eu http: paths: - backend: serviceName: default-http-backend servicePort: 80 path: /health-check - apiVersion: extensions/v1beta1 kind: Ingress metadata: annotations: ingress.kubernetes.io/whitelist-source-range: 23.135.13.124/32 kubernetes.io/ingress.class: extern kubernetes.io/tls-acme: "false" name: xxx-extern namespace: xxx spec: rules: - host: my.staging.eu http: paths: - backend: serviceName: my_service servicePort: 80 path: / - apiVersion: extensions/v1beta1 kind: Ingress metadata: annotations: ingress.kubernetes.io/whitelist-source-range: 0.0.0.0/0 kubernetes.io/ingress.class: extern kubernetes.io/tls-acme-challenge-endpoints: "true" generation: 1 name: kube-lego-extern namespace: kube-system spec: rules: - host: my.staging.eu http: paths: - backend: serviceName: kube-lego-extern servicePort: 8080 path: /.well-known/acme-challenge
server_name my.staging.eu; .... location /health-check { set $proxy_upstream_name "staging-default-http-backend-80"; allow 23.135.13.124/32; deny all; ... ... location / { set $proxy_upstream_name "staging-xxx-80"; allow 0.0.0.0/0; < ====== It's wrong deny all; ....
The text was updated successfully, but these errors were encountered:
Is 0.0.0.0/0 the default whitelist range from your config map?
0.0.0.0/0
Sorry, something went wrong.
No, I don't have this option in the configmap just in ingress
Successfully merging a pull request may close this issue.
I have 2 ingress for the same domain and apparently after PR #517 nginx generate a wrong whitelist-source-range.
Generated nginx.conf
The text was updated successfully, but these errors were encountered: