kubernetes-sigs/cluster-api-provider-aws

Re-think how we manage prerequisites in clusterawsadm (LFX Spring 2023 Mentorship)

Open

#3,715 opened on Sep 8, 2022

View on GitHub
 (12 comments) (9 reactions) (2 assignees)Go (689 forks)auto 404
area/clusterawsadmhelp wantedkind/featureneeds-triagepriority/important-soon

Repository metrics

Stars
 (723 stars)
PR merge metrics
 (PR metrics pending)

Description

/kind feature /area clusterawsadm

Describe the solution you'd like

Currently, we use clusterawsadm to create the AWS prerequisites (i.e. IAM stuff). This creates a Cloud Formation stack.

Users are running into issues with the clusterawsadm/cloud formation approach because CloudFormation is region specific but IAM is global. Customers end up in the position where the stacks are created in multiple regions but some fail as the IAM resources have been created by another stack in another reason. Other users have run into other issues with the cloud formation stack for various reasons.

Anything else you would like to add: I personally think we should remove the use of Cloud Formation and look at another solution.

Environment:

  • Cluster-api-provider-aws version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.