pomerium/docs/enterprise/upgrading.md
bobby 8b755a36b3
Update enterprise changelog for v0.16.0 (#2977)
* Update enterprise changelog for v0.16.0

* fmt

Signed-off-by: Bobby DeSimone <bobbydesimone@gmail.com>

* Update upgrading.md

Co-authored-by: Travis Groth <travisgroth@users.noreply.github.com>
2022-01-28 15:23:22 -08:00

1.8 KiB

title sidebarDepth description
Upgrading 0 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.16.0

Before You Upgrade

  • Configuring signing-key has been replaced by setting authenticate-service-url. The signing key will be automatically retrieved by Pomerium Enterprise Console. signing-key will continue to work, however authenticate-service-url is required for device enrollment.

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 field in the Routes entry (not including the protocol).

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:

    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 section of Install Pomerium Enterprise in Helm for more information.