Move replication controller validation into rcstrategy #4973
Labels
area/api
Indicates an issue on api area.
area/apiserver
area/usability
priority/backlog
Higher priority than priority/awaiting-more-evidence.
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
Milestone
Currently the replication controller update routine validates each update as it would a create. Before we can add subresources to a replication controller (#4909), we need a way to validate updates as incremental changes, by comparing the current and proposed versions of an object. We can achieve this by moving the update validation into a strategy and directly calling
BeforeUpdate
. This will also bring rc validation inline with the implementation in generic/etcd, making it easier to merge the two.The text was updated successfully, but these errors were encountered: