User: Jdruker/PE Upgrade
Contents
Upgrade strategies[ | edit source]
[or are we calling them modes?]
<service> supports the following upgrade mode[templatizable plural and display]:
Discussion about upgrade strategies, but basically should be able to just link back to the suite-level doc.
Timing[ | edit source]
A regular upgrade schedule is necessary (link to info about the s/w versioning policy) but fixes might warrant an earlier upgrade.
Scheduling considerations[ | edit source]
When is the best/least disruptive time for actually performing the upgrade, and how long it’ll take. Are there any service dependencies?
Preparatory steps[ | edit source]
There’s probably some templatizable general prep like:
- Any recommended backups (optional service-specific content).
- Any permissions-related changes (ditto).
Upgrade <service>[ | edit source]
- Review the RN to identify changes.
- Ensure your previously customized values.yaml is available and update it as required to implement changes.
- Download the new package.
- Execute the following command to upgrade <service>:
helm upgrade --install <service> <service-helm-artifact> -f <service>values.yaml -n <service>Verify the upgrade[ | edit source]
Rollback[ | edit source]
May need subheads for different upgrade strategies.
Validate the rollback[ | edit source]
Uninstall[ | edit source]
In addition to the instructions, are there any preparatory steps (e.g., processes to stop, data to save) and/or service dependencies?
|structuredtext=Execute the following command to uninstall <service>:
helm uninstall <service> -n <service>