can we execute on moving this to e.g. k8s.io/componentconfig in v1.12 please?
+1.
I think we all agree that we have to move the external types to a published repository. Both k8s.io/api and k8s.io/componentconfig sound fine to me, preferring the later.
@kubernetes/sig-api-machinery-api-reviews @deads2k @lavalamp @mtaufen opinions?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.![]()
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
Closed #58565.
This has been fixed in v1.12 already with KEP kubernetes/community#2354