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 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.