AWS Kubernetes Support + Command Menu

[marcuskohlberg]

Amazon EKS Support

We're happy to share that Encore now supports deploying to Amazon Elastic Kubernetes Service (EKS)! 🎉
This also means you can now deploy your app to Kubernetes on both GCP and AWS.

Encore uses EKS AWS Fargate (which is a very confusing name — Thanks Amazon!) to run your Kubernetes applications using serverless compute. This removes the need to provision and manage servers, lets you specify and pay for resources per application, and improves security through application isolation by design.

To deploy your app to EKS: Go to Create Environment, select Amazon Web Services as the cloud, then select Kubernetes: EKS Fargate.

Command Menu

As we add more and more features to Encore, we also want to make navigation simpler and faster. We're now introducing the Command Menu as a new lightning-fast method of moving around the Cloud Dashboard (coming soon to Local Dev Dash!).⚡️

Try it out yourself by opening your app in the Cloud Dashboard and pressing ⌘+K (Mac) or Ctrl+K!

In this first release, Command Menu lets you search for pages in the Cloud Dashboard and Docs. Soon we'll add much more functionality, like the ability to search for apps, services, endpoints, and more.

We'd love to hear your feedback and ideas for how to improve it — jump on Slack and share your thoughts!

commandmenu.mp4

Thanks to all contributors

🙏 We continue to be overwhelmed by your support, feedback, and suggestions!
Together we're building the future of backend development and we couldn't be more excited.

❤️ As always, we're excited to hear what you think!
Please share your feedback on Slack.

Full Changelog: v1.27.7...v1.28.0

---

This discussion was created from the release AWS Kubernetes Support + Command Menu.

[mdwitr0]

Hi, is there any plans to support a personal kubernetes cluster without AWS?

[marcuskohlberg]

Hey, great question! Not in the short term.
For small scale use, you can use Encore's built-in development cloud for free (fair use limits) — if cost is your concern. Or if you have a use case where you have to run it yourself, you can potentially use the encore eject command to create a standalone docker image and deploy that. (See docs)