kubernetes-sigs/cluster-api-provider-aws

Identity Provider Status stuck in CREATING

Open

#5,123 opened on Sep 16, 2024

View on GitHub
 (4 comments) (0 reactions) (1 assignee)Go (689 forks)auto 404
help wantedkind/bugpriority/important-longtermtriage/accepted

Repository metrics

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

Description

/kind bug

What steps did you take and what happened: Provision AWS managed control plane with Identity provider config. We are currently using Azure Active Directory (AAD) as our Identity provider.

Checking the status in AWS console shows the Status as Active but AWS Managed Control plane status shows the status stuck in CREATING phase.

image

image

We use CAPA in combination with ArgoCD and due to Identity Provider Config status stuck in CREATING phase, we are unable to use this to check the status of ManagedControlPlane readiness

What did you expect to happen: Identity Provider status in AWS Managed Control Plane status change to "Active/Provisioned/Created"

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

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

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.