Server resource validation #14194
Description
What problem are you trying to solve?
Server resources lack comprehensive validation, which can lead to invalid Servers being created and accepted. See #14176 for an example of an invalid podSelector in a Server.
How should the problem be solved?
This can be solved at multiple levels simultaneously:
- Updating the static validation (either using schema validation or an admission controller) to reject the creation of invalid Servers
- Adding a Status subresource to Server which indicates the current validity of the Server
Any alternatives you've considered?
N/A
How would users interact with this feature?
No response
Would you like to work on this feature?
None