kubernetes-sigs/cluster-api-provider-aws

Requeue after EKS cluster creation request is sent / cluster transitioned to UPDATING

Open

#2,949 opened on Nov 15, 2021

View on GitHub
 (12 comments) (0 reactions) (0 assignees)Go (689 forks)auto 404
area/provider/ekshelp wantedkind/refactorneeds-triagepriority/important-soon

Repository metrics

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

Description

/kind refactor

Describe the solution you'd like Currently, CAPA does not requeue for EKS cluster creation / update, instead, it continues on reconciliation.

CAPA should requeue (probably after a duration) after creation request is sent for creation / cluster transitioned to UPDATING for update.

Environment:

  • Cluster-api-provider-aws version: v1.0.0

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.