ingress-controller

External auth example does not work on m1 macs, the image used for testing electroma/ingress-demo-authsvc-amd64:0.1 is only built for linux/amd64
https://github.com/kubernetes/ingress-nginx/tree/main/docs/examples/customization/external-auth-headers

docker run electroma/ingress-demo-authsvc-amd64:0.1
WARNING: The requested image's platform (linux/amd64) does not match the detected hos

See release notes for Envoy 1.20.0: https://www.envoyproxy.io/docs/envoy/v1.20.0/version_history/current

http: the HeaderMatcher fields exact_match, safe_regex_match, prefix_match, suffix_match and contains_match are deprecated by string_match.

The wrinkle here is that string_match was added in Envoy 1.20.0 and does not exist in 1.19.x so we cannot use this field as soon as we

NOTE: GitHub issues are reserved for bug reports only.
For anything else, please join the conversation
in Kong Nation https://discuss.konghq.com/c/kubernetes.

https://medium.com/free-code-camp/how-to-set-up-a-serious-kubernetes-terminal-dd07cab51cd4

Is there an updated ARM template that uses VMSS for nodePool creations, add them to app gateway backend pool and I would like to know how we can egress the traffic through APP Gateway as it would be the only public IP for the cluster and I still get a random IP address when I try to access a web page from a pod.

https://raw.githubusercontent.com/Azure/application-gateway-kubernetes-ingress/ma

We run the controller with limited AWS STS credentials (issued by Vault). These credentials are not allowed to perform any operation in iam:*, which causes startup to fail. To get around this we've custom built the controller to comment out the IAM lookup, as all our certs are in ACM. It'd be nice if we could disable this in the official build via command line flag, or have it warn and move o