ingress-controller

If I wanted to enable compression for another content type, how should I proceed?

Originally posted by @bourquep in projectcontour/contour#731 (comment)

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When I schedule new pods I see equally the same behaviour each time - pod fails to start and does 'restarts', kubectl reports minimum 2 restarts before pod is marked as 'running'. in events I see next:

Events:
  Type     Reason     Age                    From               Message
  -

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