You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Today when bootstrapping a kubernetes cluster it's quite hard to properly orchestrate the cluster deployment and required system addons for monitoring, security, argocd, etc.
There is actually an issue in the AWS containers roadmap to tackle similar issue, but sounds like there are no willing to move forward on this. Probably because they don't want to maintain it by themselves but are willing the community to step up for that. Just guessing here.
Describe the solution you'd like
The solution is only for EKS workload, but most of the work will be reusable for all Kubernetes platforms. Actually, the idea will be to create a helm chart for the argocd-operator with a proper json schema. The last part is to distribute that through AWS Marketplce.
AWS Marketplace is already used to distribute other open source software like Debian, Centos, etc.
Describe alternatives you've considered
Today alternative is to leverage on a complex orchestration system we built in our CI and CD systems.
Hi @barryib , I see a lot of upvotes 👍 on the EKS request. Looks like lot of users are interested in it. I haven't really went through EKS add-ons docs but looks like it is something similar to OperatorHub or Openshift Marketplace. I'll need to spend some time understanding it better. Do you have any documentation links on how to add new add-ons or any example opensource projects particularly in operator domain that are available through EKS add-ons. I’m trying to understand whether it’s feasible and the maintenance overhead involved in supporting it..
Is your feature request related to a problem? Please describe.
Today when bootstrapping a kubernetes cluster it's quite hard to properly orchestrate the cluster deployment and required system addons for monitoring, security, argocd, etc.
As for AWS EKS, there are what is called EKS Add-on
which are built for that purpose. AWS EKS let independent software to provide their add-on through the marketplace. See https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.html#workloads-add-ons-available-vendors for the actual list.
There is actually an issue in the AWS containers roadmap to tackle similar issue, but sounds like there are no willing to move forward on this. Probably because they don't want to maintain it by themselves but are willing the community to step up for that. Just guessing here.
Describe the solution you'd like
The solution is only for EKS workload, but most of the work will be reusable for all Kubernetes platforms. Actually, the idea will be to create a helm chart for the argocd-operator with a proper json schema. The last part is to distribute that through AWS Marketplce.
AWS Marketplace is already used to distribute other open source software like Debian, Centos, etc.
Describe alternatives you've considered
Today alternative is to leverage on a complex orchestration system we built in our CI and CD systems.
Additional context
The text was updated successfully, but these errors were encountered: