Add validation to `CRDUpgradeSafety` preflight check to prevent removal of existing fields
everettraven opened this issue · comments
Now that there is a base CRDUpgradeSafety
preflight check in place, we can continue adding validation logic based on the CRDUpgradeSafety
preflight check proposal.
This issue focuses on adding a validation to ensure that no existing fields are removed from a particular version of a CRD's schema during an upgrade operation.
As a potential source of inspiration, here is how a couple of the existing validations are implemented:
- Definitions:
kapp/pkg/kapp/crdupgradesafety/validator.go
Lines 71 to 93 in 82f2a30
- Consumption:
kapp/pkg/kapp/crdupgradesafety/preflight.go
Lines 36 to 39 in 82f2a30
I believe @rashmigottipati is interested in working on this