ingress

Hia all!

Please update the documentation examples in the section of actions and the conditions.
I want to define a default HTTP 403 response for those loadbalancer rule paths which are not defined.

Environment

• AWS Load Balancer controller version: v2.2.1
• Kubernetes version: 1.19
• Using EKS (yes/no), if so version? EKS 1.19

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.

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.

Kubernetes v1.18 introduced a dedicated resource + field for defining IngressClass. See the documentation here: https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-class

It would make sense for the ingress-controller to support ingress class in this way going forward.

Related issue for skipper: zalando/skipper#1478

Timeout for waiting for the components/custom resources to launch or set up now is hardcoded. It's not reasonable since the GitHub Action is slow sometimes.

We may tidy up the timeout settings around the codebase and unify them with a configurable one, also, for the sake of easy to change, we may export an environment variable to control it.

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