Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EKS] [request]: Independent control plane and cluster addons management #217

Closed
cpoole opened this issue Mar 20, 2019 · 2 comments
Closed
Labels
EKS Amazon Elastic Kubernetes Service Proposed Community submitted issue

Comments

@cpoole
Copy link

cpoole commented Mar 20, 2019

Tell us about your request
I would like to be able to install/upgrade/configure the control plane version (1.11-eks.n) and the cluster addons (vpc cni, CSI driver, kube-dns) versions independently.

Which service(s) is this request for?
EKS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I would like to have a more consistent cluster instantiation and cluster upgrade process. I want to know that regardless of the timing in AWS release cycle I can declaratively state the components present within my cluster and have them come online without any guesswork.

This should allow me to also specify null versions for each cluster addon and have amazon present a cluster without any addons present. This would allow me to fully control the versions of these services outside of amazons release process

Are you currently working around this issue?
Currently we delete all resources on first cluster start and install our own from helm charts.

Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

@cpoole cpoole added the Proposed Community submitted issue label Mar 20, 2019
@dawidmalina
Copy link

It's very good idea! 👍

@tabern tabern added the EKS Amazon Elastic Kubernetes Service label Mar 26, 2019
@tabern
Copy link
Contributor

tabern commented Nov 15, 2020

This should be solved by #252

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EKS Amazon Elastic Kubernetes Service Proposed Community submitted issue
Projects
None yet
Development

No branches or pull requests

4 participants