Update ingress to suit networking.k8s.io/v1

[SharkofMirkwood]

I believe the latest versions of the chart are broken (1.1.0 and 1.0.1 both seem affected) due to backend in the ingress not matching the networking.k8s.io/v1 API spec; I've been receiving the following error on creating a release:

Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: [ValidationError(Ingress.spec.rules[0].http.paths[0].backend): unknown field "serviceName" in io.k8s.api.networking.v1.IngressBackend, ValidationError(Ingress.spec.rules[0].http.paths[0].backend): unknown field "servicePort" in io.k8s.api.networking.v1.IngressBackend]

See https://kubernetes.io/docs/concepts/services-networking/ingress/#the-ingress-resource and https://blog.hycorve.com/migrating-from-ingress-networking-k8s-io-v1beta1-to-v1/

I can't tell how you handle chart versioning here since the Chart.yaml hasn't been updated in 2 years, so I assume this is automated.

[sstarcher]

@SharkofMirkwood thanks and you were able to test this fix in your cluster?

[dirien]

May I add the point, to keep the chart a little bit downwards compatibel with using the template functions? I could help to add this, if its wanted ofc.

[sstarcher]

@dirien Since networking.k8s.io/v1beta1 is being removed in 1.22 and networking.k8s.io/v1 has been around for a while I don't know if we want to support clusters older than 1.19 as I don't believe they are supported by Kubernetes itself.

[sstarcher]

If someone can verify for me that this PR fixes the problem as listed and was tested I'll merge this and release a version.

[dirien]

@sstarcher,

works fine, here some screenshots:

Hope it helps

Deployed via local clone of the local repo

[sstarcher]

This should now be available as 1.1.1. The entire release is automated except for the docker image build... since docker hub stopped doing that for open source projects