weiguoqiang/cert-manager
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Add section on Migration

Browse Source 
Signed-off-by: joshvanl <vleeuwenjoshua@gmail.com>
This commit is contained in:
joshvanl 2022-01-19 10:48:48 +00:00
parent b64dcfff99
commit cfa63f47fb
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
design/20220118.server-side-apply.md
View File

@ -195,3 +195,16 @@ gaining confidence that it is a safe change is to solicit feedback from end
users who have the feature enabled. Graduation should ideally be done over no
more than one or two releases, however the project shouldn't proceed with
removing the gate until the authors are confident.
## Migration
For an exiting cluster with cert-manager and resources installed, a user should
be able to safely enable the feature or upgrade cert-manager with the feature
enabled by default without any down time or loss of data.
Although testing is needed, it _should_ be the case that an upgrade/feature
enable that all controllers on the next reconcile that applies, will take
ownership of that component's fields and set the correct values. Fields will not
be deleted that should be however (i.e. Annotation or Label from a previous
SecretTemplate) as the field manager has changed (though this is the same
behaviour as today).