pomerium/docs/enterprise/upgrading.md
backport-actions-token[bot] 5f61f7d663
Docs/batch link fixes (#2621) (#2622)
* add redirect for installation

* batch of link fixes

Co-authored-by: Alex Fornuto <afornuto@pomerium.com>
2021-09-21 17:16:11 -05:00

31 lines
No EOL
1.5 KiB
Markdown

---
title: Upgrading
sidebarDepth: 0
description: >-
This page contains the list of deprecations and important or breaking changes
for Pomerium Enterprise. Please read it carefully.
---
# Upgrading Pomerium Enterprise
When new version of Pomerium Enterprise are released, check back to this page before you upgrade.
## 0.15.0
### Before You Upgrade
- `signing-key` is now a required option to improve request security from Pomerium Core. The value should match the one set in Pomerium Core. See the [signing key] reference page for more information on generating a key.
- `audience` is now a required option to improve request security from Pomerium Core. The value should match the Enterprise Console's external URL hostname, as defined in the [`from`](/reference/readme.md#routes) field in the Routes entry (not including the protocol).
[signing key]: /reference/readme.md#signing-key
### Helm Installations
- As of v0.15.0, All Helm charts have been consolidated to a single repository. Remove the `pomerium-enterprise` repo and upgrade from `pomerium`:
```bash
helm repo remove pomerium-enterprise
helm upgrade --install pomerium-console pomerium/pomerium-console --values=./pomerium-console-values.yaml
```
- As noted above, `signing-key` must be shared between Pomerium and Enterprise. See the [Update Pomerium](/enterprise/install/helm.md#update-pomerium) section of [Install Pomerium Enterprise in Helm](/enterprise/install/helm.md) for more information.