Fix/Ingress on gcp doesnt work by default.

[8ball030]

High level description of the change.

When deployed to GCP I hit this issue;

k8s.io/client-go@v0.25.3/tools/cache/reflector.go:169: Failed to watch *v1.EndpointSlice: failed to list *v1.EndpointSlice: endpointslices.discovery.k8s.io is forbidden: User "system:serviceaccount:ingress:default" cannot list resource "endpointslices" in API group "discovery.k8s.io" at the cluster scope

I added the extra cluster rbacs to the ingress class and all seems to now work.

Testing

I deployed on GCP and was able to route ingress traffic to a contianer in the cluster.

[dghubble]

Thanks

Closes #1350

I'd be curious to hear about your usage because I've been weighing removing the addon examples Kubernetes manifests, or maybe replacing them with Terraform modules.

[8ball030]

Oh that was convenient.
Wasn't aware I'd fixed an issue.
I am a pretty heavy user of this to be candid.
It is kind of my go to.

In terms of improvements, I always end up having to basically do a couple of things;

A) setup the ingress controller.
(An option in the initial tf module I.e. ingress_enabled: bool) would save me time.

B) normally I end up having to setup a wildcard dns entry into the cluster

C) I normally have to deploy certmanager

D) I almost always have to setup persistent storage. For example an efs mount to the workers such that I can use a nfs controller to manage volumes.

Thanks again for merging my pr, it's quite cool to be a contributor to this repo, I've been using it for years.