-
Notifications
You must be signed in to change notification settings - Fork 581
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
Add EKS AutoMode support #5278
Comments
@richardcase: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Whoever picks this up we should think about the API changes upfront. Does it fit into |
This will require the upgrade to AWS SDK v2 in #2225. We created a fork to include EKS Auto Mode support in the v1 SDK: c445/aws-sdk-go@309a05d IMHO it fits into
I wished this could be aligned with ACK controller for EKS, but there is no progress yet: aws-controllers-k8s/community#2222 The AWS SDK exposes Auto Mode settings as follows:
type ComputeConfigRequest struct {
// Request to enable or disable the compute capability on your EKS Auto Mode
// cluster. If the compute capability is enabled, EKS Auto Mode will create
// and delete EC2 Managed Instances in your Amazon Web Services account.
Enabled *bool `locationName:"enabled" type:"boolean"`
// Configuration for node pools that defines the compute resources for your
// EKS Auto Mode cluster. For more information, see EKS Auto Mode Node Pools
// in the EKS User Guide.
NodePools []*string `locationName:"nodePools" type:"list"`
// The ARN of the IAM Role EKS will assign to EC2 Managed Instances in your
// EKS Auto Mode cluster. This value cannot be changed after the compute capability
// of EKS Auto Mode is enabled. For more information, see the IAM Reference
// in the EKS User Guide.
NodeRoleArn *string `locationName:"nodeRoleArn" type:"string"`
} Hint about node pools:
type StorageConfigRequest struct {
// Request to configure EBS Block Storage settings for your EKS Auto Mode cluster.
BlockStorage *BlockStorage `locationName:"blockStorage" type:"structure"`
}
type BlockStorage struct {
// Indicates if the block storage capability is enabled on your EKS Auto Mode
// cluster. If the block storage capability is enabled, EKS Auto Mode will create
// and delete EBS volumes in your Amazon Web Services account.
Enabled *bool `locationName:"enabled" type:"boolean"`
}
type KubernetesNetworkConfigRequest struct {
// Indicates the current configuration of the load balancing capability on your
// EKS Auto Mode cluster. For example, if the capability is enabled or disabled.
ElasticLoadBalancing *ElasticLoadBalancing
}
type ElasticLoadBalancing struct {
// Indicates if the load balancing capability is enabled on your EKS Auto Mode
// cluster. If the load balancing capability is enabled, EKS Auto Mode will
// create and delete load balancers in your Amazon Web Services account.
Enabled *bool `locationName:"enabled" type:"boolean"`
} API draft autoModeConfig:
nodeRoleArn: arn:aws:iam::123456789012:role/eks-node-role
nodePools:
generalPurpose: true
system: true
blockStorage: true
elasticLoadBalancing: true Logic for ComputeConfig:
Sean Schneeweiss [email protected], Mercedes-Benz Tech Innovation GmbH, Provider Information |
/kind feature
/priority important-soon
/triage accepted
/help
Describe the solution you'd like
Add support for EKS Auto mode to CAPA.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: