WikiSysop: Created page with "==Upgrade strategies== supports the following upgrade strategies [templatizable plural and display]: Rolling Update {{FULLPAGENAME}..."

2022-03-30T14:55:26Z

Created page with "==Upgrade strategies== <service> supports the following upgrade strategies [templatizable plural and display]: *[[{{FULLPAGENAME}}#Rolling|Rolling Update]] *{{FULLPAGENAME}..."

New page

==Upgrade strategies==
<service> supports the following upgrade strategies [templatizable plural and display]:

*[[{{FULLPAGENAME}}#Rolling|Rolling Update]]
*[[{{FULLPAGENAME}}#BlueGreen|Blue/Green]]
*[[{{FULLPAGENAME}}#Canary|Canary]]

You must upgrade Designer and DAS in tandem. The way you upgrade or rollback Designer and DAS depends on the way you initially deployed the service.

For more information about the upgrade strategies, see {{Link-SomewhereInThisVersion|manual=PEGuide|topic=UpgradStrats}}.

==Timing==
A regular upgrade schedule is necessary (link to info about the s/w versioning policy) but fixes might warrant an earlier upgrade.

===Scheduling considerations===
''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==
# Review the release note to identify what's changed.
# Download the new package from the JFrog repository (https://pureengageuse1.jfrog.io/ui/login/).
# If necessary to accommodate new features or modifications, update your environment or your customized '''values.yaml''' file as required.
''Additional service-specific steps -- e.g., back up a db.''

{{AnchorDiv|Rolling}}
==Rolling Update==
===Upgrade===
# ''Service-/Strategy-specific steps.''
# Execute the following command to upgrade the service:
#: <source lang="text">helm upgrade --install <service> -f <service>-values.yaml -n <service package></source>
#: where <tt><service>-values.yaml</tt> is your customized '''values.yaml''' file.
#: '''Tip:'''If the only update you need to make to your existing '''<service>-values.yaml''' is to update the image version, you can pass the image tag as an argument by using the <tt>--set</tt> flag in the command:
#: <source lang="text"><nowiki>helm upgrade --install <service> -f <service>-values.yaml <service package> --set <service>.image.tag=<new service version></source>

Follow the same instructions to upgrade Designer and DAS. For example, the respective commands are:
* Designer: <source lang="text">helm upgrade --install designer -f designer-values.yaml designer-100.0.112+xxxx.tgz --set designer.image.tag=100.0.112.xx</source>
* DAS: <source lang="text">helm upgrade --install designer-das -f designer-das-values.yaml designer-das-100.0.112+xxxx.tgz --set das.image.tag=9.0.1xx.xx.xx</source>

===Rollback Designer===
To perform a rollback, the image version in the '''designer-values.yaml''' file can be downgraded. Or you can use the <code>--set</code> flag through the command given below. Once the '''designer-values.yaml''' file is updated, use this Helm command to perform the rollback:

*<code>helm upgrade --install designer -f designer-values.yaml designer-100.0.112+xxxx.tgz --set designer.image.tag=9.0.1xx.xx.xx</code>

The values.yaml overrides passed as an argument to the above Helm upgrade command:

*<code>designer.image.tag=9.0.1xx.xx.xx</code> - This is the Designer version to be rolled back to, for example, <code>9.0.111.05.5</code>.

===Upgrade DAS===
To perform an upgrade, the image version has to be upgraded in the '''designer-das-values.yaml''' file or can be set using the <code>--set</code> flag through the command given below. Once the '''designer-das-values.yaml''' file is updated, use this Helm command to perform the upgrade:

*<code>helm upgrade --install designer-das -f designer-das-values.yaml designer-das-100.0.112+xxxx.tgz --set das.image.tag=9.0.1xx.xx.xx</code>

The values.yaml overrides passed as an argument to the above Helm upgrade command:

*<code>das.image.tag=9.0.1xx.xx.xx</code> - This is the new DAS version to be installed, for example, <code>9.0.111.05.5</code>.

===Rollback DAS===
To perform a rollback, the image version in the '''designer-das-values.yaml''' file can be downgraded. Or you can use the <code>--set</code> flag through the command given below. Once the '''designer-das-values.yaml''' file is updated, use this Helm command to perform the rollback:

*<code>helm upgrade --install designer-das -f designer-das-values.yaml designer-das-100.0.112+xxxx.tgz --set das.image.tag=9.0.1xx.xx.xx</code>

The values.yaml overrides passed as an argument to the above Helm upgrade command:

*<code>das.image.tag=9.0.1xx.xx.xx</code> - This is the DAS version to be rolled back to, for example, <code>9.0.111.05.5</code>.

===Verify the upgrade===

==Rollback==
May need subheads for different upgrade strategies.

===Validate the rollback===

==Uninstall==
In addition to the instructions, are there any preparatory steps (e.g., processes to stop, data to save) and/or service dependencies?

Execute the following command to uninstall <service>:
<source lang="text">helm uninstall <service> -n <service></source>

User:Jdruker/PE Upgrade/Designer JD - Revision history

WikiSysop: Created page with "==Upgrade strategies== supports the following upgrade strategies [templatizable plural and display]: *Rolling Update *{{FULLPAGENAME}..."

WikiSysop: Created page with "==Upgrade strategies== supports the following upgrade strategies [templatizable plural and display]: Rolling Update {{FULLPAGENAME}..."