Epinio v0.2.0 Release
This release adds Epinio to the Rancher UI dashboard, but that is not the only significant change; many more features have been added.
A future blog post might talk more about the new UI, but in short, once you install Epinio on your cluster, it shows up automatically in Rancher’s web interface. Then you can upload your app sources, which will automatically deploy. Please look at Epinio UI installation instructions for more instructions.
This update was possible due to redesigning the Epinio API server, making it easier to manage multiple users.
Under the hood, Epinio became more modular and can optionally use existing S3 storage and container registries. Gitea was removed, but Epinio can still deploy apps from a Git source, and Linkerd is also optional.
Upstream no longer maintains the service catalog component, so Epinio services are now just secrets containing the service’s connection details provided to the workloads. In contrast to the env var feature, the service secrets can be shared between applications.
This release was tested with more public, private, and local cluster offerings. You can find the growing list in the installation docs. Epinio v0.2.0 also comes with a Helm chart that supports the integration into Rancher.
Several improvements were implemented regarding the application workloads:
- Workloads are now deployed with a manifest. The manifest can also be generated from an existing workload.
- Application health is reported in more detail.
- Workloads were previously limited to the system domain. However, different domains per workload are now possible, and path-based routing is supported.