You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please review these deprecations and important changes for Pomerium Enterprise before upgrading.
280
+
:::info
282
281
283
-
:::caution
282
+
Your Pomerium Enterprise version should always match the same **minor version number** as your Pomerium Core version. For example:
283
+
✅ Core **v0.27.0** with Enterprise **v0.27.3** is a supported configuration.
284
+
❌ Core **v0.27.0** with Enterprise **v0.28.0** is not supported.
284
285
285
-
<UpgradeNotice />
286
286
:::
287
287
288
+
To **upgrade** a Pomerium Enterprise deployment, we recommend that you:
289
+
290
+
1. Reach out to your account manager to let us know you are planning an upgrade, especially if upgrading across multiple minor versions at once.
291
+
1. First review the version-specific upgrade notes on this page for **both** Pomerium Core and Pomerium Enterprise for any changes that might pertain to your deployment. (If you're not sure, please don't hesitate to reach out and ask for clarification.)
292
+
1. Take a database backup of the Pomerium Enterprise database.
293
+
1. Upgrade Pomerium Core to the new version. For a replicated deployment, instances can be updated one at a time to avoid downtime.
294
+
1. Upgrade Pomerium Enterprise to the new version.
295
+
1. Verify that your deployment continues to behave as expected.
296
+
297
+
In case of trouble during the upgrade process, follow these steps to **roll back** to the previous version:
298
+
299
+
1. Stop Pomerium Enterprise.
300
+
1. Restore the Pomerium Enterprise database from a backup taken before the upgrade.
301
+
1. Downgrade Pomerium Core to the previous version.
302
+
1. Start the previous version of Pomerium Enterprise.
0 commit comments