containers-roadmap
containers-roadmap copied to clipboard
[EKS] Install AWS Controllers for Kubernetes (ACK) on control plane
AWS EKS should come with the ~aws-service-operator~ AWS Controllers for Kubernetes installed by default.
This will allow for users to create their "node pools" from within Kubernetes itself.
~There is a bit of information on this in the issue filed under the aws-service-operator project.~
@JordanDeBeer thanks for the issue, I'm excited to hear you are enjoying the AWS Service Operator. Are there other features/functions you would like for if the operator if was in the EKS control plane or only to provision node groups?
For example, would you want to be able to customize which services were manageable or would you leave that to the RBAC rules and let the cluster admin dole out permissions to which services where actually manageable to their teams? More information about the feature I'm talking about here https://github.com/awslabs/aws-service-operator/blob/master/cmd/aws-service-operator/main.go#L53
If you have more folks interested in this support please have them 👍 the issues. Thanks again!
Are there other features/functions you would like for if the operator if was in the EKS control plane or only to provision node groups?
I could see myself using it to provision other resources as well, but node groups would be the best feature.
For example, would you want to be able to customize which services were manageable or would you leave that to the RBAC rules and let the cluster admin dole out permissions to which services where actually manageable to their teams? More information about the feature I'm talking about here https://github.com/awslabs/aws-service-operator/blob/master/cmd/aws-service-operator/main.go#L53
As far as permissions goes, I think RBAC would be an appropriate way to limit which resources get created. Alternatively, couldn't the EKS Service Role be used to limit which resources can be created via IAM?
Thank you for looking into this. It's a feature I very much would like to see in EKS.
Thank you for the feedback, as the maintainer of the operator the fact that you added this is very exciting to me.
Update AWS Controllers for Kubernetes has replaced the service operator project, so I am updating the details of this request to reflect this change.
We will be able to deliver an automated installation of ACK through #252, likely as a future improvement to this feature after it launches. We will consider ACK support for the EKS controller to be the bar for closing this issue as that would allow you to define and control the managed node groups for the cluster through the cluster itself.
AWS EKS should come with the ~aws-service-operator~ AWS Controllers for Kubernetes installed by default.
This will allow for users to create their "node pools" from within Kubernetes itself.
~There is a bit of information on this in the issue filed under the aws-service-operator project.~
How would ACK allow for creating NodePools? I would request Karpenter be added to control-plane and managed by AWS? At a minimum make it an addon?
I would request Karpenter be added to control-plane and managed by AWS?
There's a separate feature request for that:
- #1792