serving
serving copied to clipboard
Move DomainMapping from Beta to GA
DomainMapping became Beta since Knative v0.24 and now it should be enough to move GA.
To make it GA:
- [x] Drop
v1alpha1
DomainMapping API - [ ] Add
v1
DomainMapping API - [ ] Remove
betaTests
configuration from e2e in serving and networking repos.
Follow up tasks after GA:
- [ ] Merge DomainMapping's controller and webhook into serving controller and webhook.
- [ ] Drop
v1beta1
DomainMapping API.
/area API /area networking /kind good-first-issue
/cc @dprotaso @evankanderson @psschwei @ReToCode @skonto
If there is any objection to make DomainMapping GA or miss some process, please leave a comment.
Just in case. As per the attached feature track in https://github.com/knative/serving/issues/7748 , the requirement of the GA is:
Four releases have been cut since the Alpha milestone, no roadblocks have been discovered in any backend implementation that argue against long-term support.
It has already done more than 4 releases and no roadblocks have been discovered in any backend implementation that argue against long-term support.
There's a project tracking this here - https://github.com/knative/serving/projects/47
It seems like folks have added some issues to the GA column since I last looked.
A big one for me is the fact that certain protocols don't seem to work out of the box - https://github.com/knative/serving/issues/13083
Ah, okay. Then, the issues in GA column should be solved.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen
. Mark the issue as
fresh by adding the comment /remove-lifecycle stale
.
/assign
/remove-lifecycle stale
/assign
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen
. Mark the issue as
fresh by adding the comment /remove-lifecycle stale
.
/unassign @Priyansurout /lifecycle frozen