-
Story
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
True
-
5
-
None
-
NI&D Sprint 267, NI&D Sprint 268
What?
The purpose of this task is to block upgrades until a cluster admin explicitly provides consent for the platform to start taking over management of the Gateway API CRDs.
Why?
See the description of NE-1898.
How?
We will use an "admin gate" to inform the cluster admin of their responsibilities to ensure the safety of the cluster and block upgrades until the cluster admin accepts that responsibility.
The gate will include a description explaining the dangers of accepting the gate without understanding and accounting for its implications, as well as a link to more extensive documentation about this transfer (this is being created as a part of OSDOCS-13326).
The gate will be added only to 4.18.z clusters. From 4.19 onward, the transfer is complete, and the cluster ingress operator manages the gateway CRDs.
Prior Art
For an example of using admin gates in this manner, see here.