aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

Add support for applying EKS manifest yaml files from CloudFormation

Open
#1,441 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

AWS::EKS::Cluster

### Resource name

_No response_

### Description

A bare bones EKS cluster requires a lot of additional software be installed to be truly functional. EKS provides it's addon concept for the opinionated provisioning of some of this software (ie vpc cni, ebs csi drivers, coredns, etc). However, the addons are not configurable, and are limited in scope.

It would be hugely useful to be able to apply kubernetes manifest yaml files stored in S3 (or inline) via CloudFormation. This would allow infrastructure teams to build reusable cluster configurations in CloudFormation without having to introduce another mechanism to complete cluster setup.

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the AWS::EKS::Cluster resource and review how CloudFormation handles EKS add-ons and resource properties. Investigate the proposed S3 and inline Kubernetes manifest inputs, including their application lifecycle and ordering. Done means CloudFormation can declaratively apply the manifests as part of reusable EKS cluster configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.