New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ingress: Add Ingress to v1 API and update backend to defaultBackend #89778
Conversation
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
/assign @liggitt |
/retest |
1 similar comment
/retest |
/assign @robscott |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for all the work on this! Will be great to get this in early in the release cycle.
kubernetes/kubernetes#91420 kubernetes/kubernetes#90672 kubernetes/kubernetes#90671 kubernetes/kubernetes#89778 kubernetes/kubernetes#90463 can only be tacked later when the GRM vendors the 1.19 libraries and is capable of understanding autoscaling/v2beta2 (as it has some incompatible changes compared to autoscaling/v2beta1)
kubernetes/kubernetes#91420 kubernetes/kubernetes#90672 kubernetes/kubernetes#90671 kubernetes/kubernetes#89778 kubernetes/kubernetes#90463 can only be tacked later when the GRM vendors the 1.19 libraries and is capable of understanding autoscaling/v2beta2 (as it has some incompatible changes compared to autoscaling/v2beta1)
kubernetes/kubernetes#91420 kubernetes/kubernetes#90672 kubernetes/kubernetes#90671 kubernetes/kubernetes#89778 kubernetes/kubernetes#90463 can only be tacked later when the GRM vendors the 1.19 libraries and is capable of understanding autoscaling/v2beta2 (as it has some incompatible changes compared to autoscaling/v2beta1)
kubernetes/kubernetes#91420 kubernetes/kubernetes#90672 kubernetes/kubernetes#90671 kubernetes/kubernetes#89778 kubernetes/kubernetes#90463 can only be tacked later when the GRM vendors the 1.19 libraries and is capable of understanding autoscaling/v2beta2 (as it has some incompatible changes compared to autoscaling/v2beta1)
kubernetes/kubernetes#91420 kubernetes/kubernetes#90672 kubernetes/kubernetes#90671 kubernetes/kubernetes#89778 kubernetes/kubernetes#90463 can only be tacked later when the GRM vendors the 1.19 libraries and is capable of understanding autoscaling/v2beta2 (as it has some incompatible changes compared to autoscaling/v2beta1)
kubernetes/kubernetes#91420 kubernetes/kubernetes#90672 kubernetes/kubernetes#90671 kubernetes/kubernetes#89778 kubernetes/kubernetes#90463 can only be tacked later when the GRM vendors the 1.19 libraries and is capable of understanding autoscaling/v2beta2 (as it has some incompatible changes compared to autoscaling/v2beta1)
In addition to `extensions/v1beta1`, `networking.k8s.io/v1beta1` was also deprecated in 1.19 and is also targeted for removal in 1.22. Deprecation PR: kubernetes/kubernetes#89778 Removal mention in deprecation guide: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#ingress-v122
This commit implements the changes introduces in [1] and documented in [2] Mainly, this concerns the definiton of a `backend` and the necessity to declare a `pathType`[3]. I choose `ImplementationSpecific` here, as this was the default previously and passes the decision how the path should be matched to our `nignx-ingress`. [1] kubernetes/kubernetes#89778 [2] https://kubernetes.io/blog/2020/04/02/improvements-to-the-ingress-api-in-kubernetes-1.18/ [3] https://kubernetes.io/blog/2020/04/02/improvements-to-the-ingress-api-in-kubernetes-1.18/#better-path-matching-with-path-types
Signed-off-by: Christopher M. Luciano cmluciano@us.ibm.com
What type of PR is this?
/kind api-change
What this PR does / why we need it:
This PR adds Ingress to the networking v1 APIs. The planned rename of backend to defaultBackend is also implemented.
Which issue(s) this PR fixes:
xref:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
Ingress KEP
kubernetes/enhancements#1453