search

aws / aws-proton-public-roadmap

This is the public roadmap for AWS Proton
https://aws.amazon.com/proton
Other
199 stars 13 forks source link

EKS support #31

Open rafavallina opened 3 years ago

rafavallina commented 3 years ago

Incorporate native support for EKS, allowing customers to describe infrastructure using Kubernetes YAML and provision infrastructure using a GitOps engine

resouer commented 3 years ago

Will EKS be considered as infrastructure ony? How services template looks like then?

clareliguori commented 3 years ago

@resouer The word "infrastructure" is used in a general sense here to describe provisioning Kubernetes objects via Proton. So an environment template or service template that is deployed by Proton to your EKS cluster could be a Kubernetes manifest that contains any Kubernetes objects: Deployment, Service, Ingress, etc, as well as CRD-based objects and other cluster configuration.

resouer commented 3 years ago

@clareliguori Thanks it makes lots sense now. Though the existing GitOps engines in Kubernetes world all have dependency on Kubernetes itself. Not sure how this be fixed in Proton.

mohitanchlia commented 3 years ago

Is there an idea of when this would be available?

rafavallina commented 3 years ago

@mohitanchlia can't really make a public commitment on this, I'm sorry. We are definitely aware of the relevance and it's top of mind for us, I can say that!

lgs commented 3 years ago

+1 for EKS support,
that is the only driver in our use case. No EKS and related CI/CD no Proton

rafavallina commented 2 years ago

Hi everyone! This request is a bit stale at this point as I have not updated it in a while. However, we are working on this, currently on the design phase. Here are some updates:

Our current plans are to rely on a GitOps engine (e.g. Flux) for the actual provisioning. Proton would render a manifest based on the Proton template and the specification provided by the developer, and then make a PR to the cluster configuration repository, triggering the GitOps engine. Our goal is that customers can work with the GitOps engine of their choice, but will look to support easy integrations with a few of them when possible.

Some open questions we have at this point are:

As usual, I'm happy to discuss in detail, either here or in 1:1s. Please leave a comment if you want to chat more!

tatcoo commented 1 year ago

Hi to those in the thread - we're working on a model that could help with customers who want to empower their app developers to self-serve namespaces to a Kubernetes cluster (with the right configuration / policies in place). Is anyone interested in that model, or open to discussing how they're implementing it today?