Ephemeral Kubernetes Clusters
This feature is still experimental and only available in Garden
>=0.13.14. Please let us know if you have any questions or if any issues come up!
At Garden, we're committed to reducing the friction with getting started and trialing our tooling with your projects. To make Garden adoption more accessible and convenient, we've introduced Ephemeral Kubernetes Clusters. We designed this feature to provide you with a hassle-free way to explore Garden's capabilities on Kubernetes without needing to configure or provision a local or remote cluster.
The Ephemeral Kubernetes Clusters are provided for free to all users in our Community Tier. These clusters are meant for short-term use and to allow you to run and test your applications with Garden on a remote Kubernetes cluster.
You can add or remove ephemeral Kubernetes cluster easily via the
There are multiple example garden projects that are already configured and ready to go with Garden ephemeral clusters. Checkout our quickstart guide or the ephemeral-cluster-demo example on GitHub. In the following steps you'll learn how to configure your own Garden projects to use the
ephemeral-kubernetesprovider to your project configuration file and associate it with an environment. If you are starting a new project copy this file:
- name: ephemeral
- name: ephemeral-kubernetes
From your project root run:
To deploy your project run:
garden deploy --env ephemeral
To access your application you need to expose it with an ingress. Each cluster is assigned its own unique hostname when created. To reference it in your ingress definition, consider this container action:
description: Frontend service container
- name: http
- path: /
ephemeral-kubernetesprovider outputs the dynamically created hostname for your cluster. You can reference this output in your Garden actions and Garden will print out your ingress links on deploy. To apply the changes deploy again and visit your application in the browser via the provided link.