Add configuration options to CRD Upgrade Safety preflight check for error/warn modes and failing open/closed. #668
Labels
epic/crd-upgrade-safety
Marks an issue as part of the CRD Upgrade Safety epic
This builds on top of #661 and #667, focusing on adding configuration options to the crd upgrade safety preflight check.
The configuration options are as follows:
error
mode, this check will fail if any problems are found with upgrading a CRD and prevent the changes from being applied to the cluster. When run inwarn
mode, this check will always succeed, but log warnings for any problems found. Thewarn
mode allows users to be aware of potential problems but proceed with applying the changes to the cluster if all other enabled preflight checks pass.error
is the default.mode=error
. When running in theopen
mode, if a change to an existing field is not validated by an existing check the preflight check will pass. When running in theclosed
mode, all changes to an existing field must be validated by an existing check. If it has not, the preflight check will fail with a message along the lines of "unable to determine if change to existing field is safe ...".closed
is the default.If the proposal for adding this functionality to carvel-dev/kapp has been accepted prior to starting this work, all changes should be made against carvel-dev/kapp, otherwise the changes should be made against https://github.com/everettraven/kapp/tree/feature/crd-upgrade-safety-preflight
The text was updated successfully, but these errors were encountered: