Skip to main content
Version: Next 🚧

Upgrading Epinio

Review the breaking changes and migration steps for your target version before upgrading. For the full list of releases and their release notes, see versions.

1.13.X and 1.14.0 to 1.14.1​

Git configuration handling changed. Selecting a configuration when deploying from a private repository is now explicit: Epinio no longer implicitly matches a stored configuration to a repository URL at push time.

  • New private-repo pushes must select a git configuration. In the dashboard, choose one in the application's Git source. From the CLI or automation, the git origin must carry origin.git.gitconfig; a push that sends no configuration clones unauthenticated and fails with authentication required.
  • Existing applications keep working. On redeploy, a compatibility fallback still matches configuration-less apps to a stored configuration by repository URL, so they continue to clone as before.
  • Credentials are bound to their instance host. A configuration's credentials are only sent to the host it is scoped to; selecting a configuration whose host does not match the repository is rejected.
  • Global configurations are administrator-only to create. Non-admin users can use global configurations but cannot create them.

This release also adds a spec.origin.git.gitconfig field to the apps CRD. If you install CRDs from the Helm chart's crds/ directory out of band, apply the updated CRD on upgrade so the field is not pruned. See Git Configuration.

1.13.X to 1.14.0​

There are no breaking changes in this release. Documentation around performance was added: see performance tuning for best practices and recommendations for optimizing Epinio performance.

1.12 and 1.13.X to 1.13.10​

Epinio 1.13.10 replaces MinIO with SeaweedFS as the default S3-compatible storage solution. If you do not have a custom configuration for your S3 storage, you can uninstall MinIO and SeaweedFS will be installed by default with the Epinio Helm chart. See the SeaweedFS documentation.

User permissions changed in 1.13.10. While fully backwards compatible, additional user-right actions and default installed roles were added. See the authorization documentation.

1.12 and 1.13.7 to 1.13.8​

Epinio 1.13.8 switches from kubed to reflector for syncing ConfigMaps and Secrets across namespaces, because kubed is deprecated and unmaintained.

If you are upgrading from 1.13.7 or earlier to 1.13.8 or later, you must manually uninstall kubed from your cluster after the upgrade completes.

You can view the changes in these files:

By default all namespaces are allowed, but the reflector can be customized for your deployment. If you were not customizing kubed previously, no action is needed other than uninstalling kubed.

1.12 to 1.13​

Epinio 1.13 rehomes configuration for staging workloads to a more Kubernetes-standardized format that supports a wider variety of configs. These are no longer set via environment variables on the Epinio Server or through CLI flags; they are read from an in-cluster ConfigMap at staging time.

Documentation has been updated for both the Epinio Server and the Epinio Helm chart. Refer to these before upgrading to 1.13.