ingress

A few weeks ago it was announced that NLBs could now use and Application Load Balancer-type Target Group (docs).

We are currently using the [previously docum

A Kong SNI can only point to a single certificate. Per Kong/kubernetes-ingress-controller#1268 (comment), misconfigured Kubernetes resources can attempt to point an SNI to multiple certificates.

While we do avoid adding attached SNIs to new certificates, we do

Service LBs populate the description field with helpful information. I see GCE ingress does not do that for things like forwarding rules. Would be helpful in UIs.

Use heptio/workgroup to improve handling of the multiple goroutines that are spawned in each of the discoverers. This will also help us to bubble up errors to main, and handle them appropriately.

An example of this is #224. We wanted to handle the case where re-auth failed 3 times, but there was no good way of bubbling up the error to main.go. We could make reconciler.Run return an error to bub

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

Test cases are failing for status pages which reflect that there is some API change from the service providers. We should update our implementation for handling status pages and fix those test cases.

Issue description

Hi, when I create a new Issue or PR, it's too complex for me to fulfill the contents :)

I find a better example here https://github.com/facebook/docusaurus/issues/new/choose, could we have some ideas from it?

![image](https://user-images.githubuserconten

Please, add some brief instructions, dependencies and requirements to compile kubemci (golang, GOPATH, GOBIN. etc).

That would be very helpful for those who not familiar with golang. Thanks in advance.

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

We can see ornaments on the map, but it would be useful to see extended info in portal info section.