vela config-template migrate
Adopt a legacy config template and its configs into ConfigTemplate and Config CRs.
Synopsis
Adopt a legacy config template (a config-template-<name> ConfigMap) and every legacy config made from it, in any namespace, into ConfigTemplate and Config CRs. Nothing is deleted: each config Secret becomes owned by its Config, the template ConfigMap is annotated with the ConfigTemplate that replaced it, and a second run skips both. --all does this for every legacy template in the namespace, then for the legacy configs left there. Objects a GitOps tool applies are adopted too and the report lists them: commit their new ConfigTemplate and Config CRs to the repository the GitOps tool applies them from, next to the legacy objects, or the tool reverts them.
vela config-template migrate [flags]
Examples
vela config-template migrate my-template -n vela-system
vela config-template migrate my-template -n vela-system --dry-run
vela config-template migrate --all -n vela-system
Options
--all migrate every legacy template in the namespace
--dry-run print the CRs that would be created and the objects that would be adopted, and change nothing
-h, --help help for migrate
-n, --namespace string specify the namespace of the template (default "vela-system")
Options inherited from parent commands
-V, --verbosity Level number for the log level verbosity
-y, --yes Assume yes for all user prompts
SEE ALSO
- vela config-template - Manage the template of config.