Closed alexgervais closed 3 years ago
/assign @bowei
We can do this, although extensions v1beta1 has been removed and the feature will go GA soon.
Probably only need: networking.v1beta1 and networking.v1 when it comes? Solution would likely be to vendor the version conversion utilities to make it easy to interoperate?
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
This is already being returned by kubectl.
/close
@aledbf: Closing this issue.
Although our aim is to provide conformance tests for
networking.k8s.io/v1
, ingress-controller implementors would benefit from having the ability to test against different versions of the spec:networking.k8s.io/v1beta1
andextensions/v1beta1
.Consider using annotation on Scenarios for each of the supported version of the spec:
@networking.k8s.io/v1
,@networking.k8s.io/v1beta1
,@extensions/v1beta1