ingress-controller

The Helm chart provides the flag controller.nodeSelector for the controller pod which allows to assign it to nodes with a specific label.
It would be nice to have a nodeSelector flag for the admission jobs (create/patch) too, e.g.:
controller.admissionWebhooks.patch.nodeSelector.

Right now we have some basic information about how to get involved under https://projectcontour.io/community/. I think we could drive more attention to the community efforts if we had a more prevalent "Get involved" section on the front page, similar to what https://inclusivenaming.org/ does.

I see this as multiple parts:

• Update/modify the current /community page to look a bit better and hav

Most of our table driven unit tests goes in this format:

	for idx, tt := range cases {
		t.Run("case-name", func(t *testing.T) {
			// do something on tt
		})
	}

The loop iteration variable tt is used in the inner function, while t.Run runs the function in param in a separated goroutine. If we use t.Parallel() to run test cases in parallel, the variable inside may not be the

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

The impression from the values.yaml description regarding Redis Sentinel use, is to provide three config options, but does not make clear that the address also needs to be updated to reflect the Sentinel port (typically 26379). This is the relevant extract:

redis:
  # The addrs value will allow you to set your Redis addresses. If you are
  # using a redis cluster, you can l