The ingress resource was moved to a new API group, with a full cutover starting in 1.22. Moved from networking.k8s.io/v1beta1 to networking.k8s.io/v1.
Changes proposed in this pull request
Based on this comment the new API group is only applied when the cluster version is >=1.20, which is when k8s starts reading from the stable api group instead of the beta api group for the ingress controller.
Contributor Checklist
[ ] ~Variables are documented in the README.md~
[x] Which branch are you merging into?
master is for changes related to the current release of the concourse/concourse:latest image and should be good to publish immediately
dev is for changes related to the next release of Concourse (aka unpublished code on master in concourse/concourse)
Reviewer Checklist
This section is intended for the core maintainers only, to track review progress. Please do not
fill out this section.
[ ] Code reviewed
[ ] Topgun tests run
[ ] Back-port if needed
[ ] Is the correct branch targeted? (master or dev)
Existing Issue
Fixes #204
Why do we need this PR?
The ingress resource was moved to a new API group, with a full cutover starting in 1.22. Moved from
networking.k8s.io/v1beta1tonetworking.k8s.io/v1.Changes proposed in this pull request
Based on this comment the new API group is only applied when the cluster version is >=1.20, which is when k8s starts reading from the stable api group instead of the beta api group for the ingress controller.
Contributor Checklist
README.md~masteris for changes related to the current release of theconcourse/concourse:latestimage and should be good to publish immediatelydevis for changes related to the next release of Concourse (aka unpublished code onmasterin concourse/concourse)Reviewer Checklist