Yerken

@Raffo you are welcome to contribute ;)

@linki was this issue already addressed ? if not, please include some examples

I suggest this delayed until this PR is merged https://github.com/kubernetes/kubernetes/pull/39173 Currently `k8s.io/kubernetes/...` packages have internal conflicts with official Go CLI. Upon the merge I expect much easier integration of leaderelection...

IMHO we should not try to support custom solutions, which do not write back the ingress status. Having multiple sources of truth will not only be difficult to manage, but...

@onzo-operry please specify the version of mate you are running - nevermind, I see you are running 0.5.1, please try master branch. First thing I would suggest you to run...

you should be getting two RRS created: 1. annotated-nginx.prod.onzo.cloud - as specified in your service 2. a1.prodb.onzo.cloud - as specified in your ingress rule hosts So to double confirm none...

@onzo-operry `annotated-nginx.prod.onzo.cloud` this one will be created if you have `prod.onzo.cloud` (note missing **b** in `prod`) hosted zone as well. I will create and deploy a new release which should...

I reckon the reason is ELB address is not reported on the ingress resource. Could you please try: ``` kubectl get -o json ingress ingress ``` and paste the output...

** "ip": "10.55.53.140" ** Yes, it is a compatibility issue with nginx-ingress-controller. Unfortunately this information is not enough to set up an Alias A record on Route53 :( ____ There...

@onzo-operry this is more related to the way nginx-controller works, because the address is reported from the nginx-controller. Unfortunately since in Route53 we only create Alias records, public/private IP cannot...