Updating ingress-controller, default-backend and fixing permission for ClusterRole

[BradErz]

Upgrading nginx-ingress-controller to 0.9.0-beta.10 and default backend server to 1.3.

Fixing the ClusterRole to allow permission to create/update config map as it complains.

Fixes: #2895

[k8s-ci-robot]

Hi @BradErz. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[chrislovecnm]

/assign @aledbf

[chrislovecnm]

@aledbf do you mind reviewing?

[chrislovecnm]

/ok-to-test

[aledbf]

@chrislovecnm sure

[aledbf]

This permissions are too open. Please check https://github.com/kubernetes/ingress/tree/master/examples/rbac/nginx
We only need to update one configmap used to store the leader election.

[chrislovecnm]

/retest

[BradErz]

@aledbf Heya, sorry for getting back to you so late. Had a busy week!

I refactored it to match the nginx rbac recommendations, now it's using a role and cluster role. I tested on my test cluster and seems just fine.

[justinsb]

Closing & reopening to trigger CI

[justinsb]

LGTM