# Ziti Mobile Edge on ChromeOS (Google Workspace Managed Device) Auto-Closes Immediately After Launch

**URL:** <https://openziti.discourse.group/t/ziti-mobile-edge-on-chromeos-google-workspace-managed-device-auto-closes-immediately-after-launch/5340>\
**Category:** Ziti Mobile Edge for Android\
**Created:** [November 16, 2025, 11:12pm UTC](https://openziti.discourse.group/t/ziti-mobile-edge-on-chromeos-google-workspace-managed-device-auto-closes-immediately-after-launch/5340 "2025-11-16T23:12:00Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![qrkourier](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/qrkourier/32/52_2.png) [@qrkourier](https://openziti.discourse.group/u/qrkourier)\
**Post date:** [December 8, 2025, 4:57pm UTC](https://openziti.discourse.group/t/ziti-mobile-edge-on-chromeos-google-workspace-managed-device-auto-closes-immediately-after-launch/5340/21 "2025-12-08T16:57:43Z")

</div>

Let's separate two concepts:

1. Upgrade the Ziti version you're deploying with Helm
2. Upgrade the Chart version you're using to deploy Ziti with Helm

For any production environment, you'll benefit from having a test stage as close to it as practically possible so you can prove upgrade candidates.

You're asking about upgrading Ziti version 1.1.5 to 1.6.9. This is not a question of Helm Chart versions, but Ziti versions. You can [review the differences in the Ziti CHANGELOG](https://github.com/openziti/ziti/blob/v1.6.9/CHANGELOG.md) before overriding the Ziti version in your Ziti Controller Helm Chart Release like `image.tag: 1.6.9`.

After the Ziti Controller Helm Chart was released with default Ziti version 1.1.5, the Helm Chart major version was incremented to `v2.0.0` due to a breaking change. To upgrade your chart version, you must perform the one-time migration procedure in the "Breaking Change" section of the controller deployment guide for Kubernetes: [Install the Controller in Kubernetes | NetFoundry Documentation](https://netfoundry.io/docs/openziti/guides/deployments/kubernetes/kubernetes-controller#breaking-change). The purpose of the breaking change is to break the dependency on Cert Manager and Trust Manager so they can be upgraded separately from Ziti Controller.

* * *

### The Ziti Version

Each Helm Chart comes with a default Ziti version. You can upgrade the Ziti version by overriding the `image.tag` input value. As a rule, there's no reason you shouldn't override the Ziti version to upgrade or downgrade.

⚠ Upgrading Ziti may trigger a datastore migration. If this happens, it will not be possible to downgrade the Ziti version without first restoring a database with the same or lower datastore version required by the target Ziti version. Ziti automatically triggers a database snapshot before migration. The snapshot is stored in the same directory as the Bolt DB file in the controller's storage volume.

* * *

### The Chart Version

Helm uses semver, and we follow suit, so you may use Helm version constraints to express your level of risk acceptance.

Examples:

- `--version='^2.0.0'` means "upgrade unless **major** (breaking) revision", or
- `--version='~2.0.0'` means "upgrade unless **minor** (features added) revision".

---

_[View the full topic](https://openziti.discourse.group/t/ziti-mobile-edge-on-chromeos-google-workspace-managed-device-auto-closes-immediately-after-launch/5340)._