In order to check if the AWSManagedControlPlane object is healthy, I wrote this custom check in Lua, as explained in the documentation.

This custom health check is needed because when experimented a bit with this resource, saw that the .status.ready field becomes true a long time before the resource was created and every dependency was provisioned.

Example of a condition that was False for some minutes even if the .status.ready was true

...
status:
  conditions:
    ...
    - lastTransitionTime: "2024-07-25T09:22:46Z"
      message: "failed reconciling OIDC provider for cluster: failed to create OIDC provider: error creating provider: LimitExceeded: Cannot exceed quota for OpenIdConnectProvidersPerAccount: 100\n\tstatus code: 409, request id: e6f1bfdd-7a41-4685-8c2d-a081c511f3d8"
      reason: EKSControlPlaneReconciliationFailed
      severity: Error
      status: "False"
    ...
    ready: true
    ...

Example of an AWSManagedControlPlane status field

...
status:
  conditions:
    - lastTransitionTime: "2024-07-25T09:40:21Z"
      status: "True"
      type: Ready
    - lastTransitionTime: "2024-07-25T09:14:12Z"
      status: "True"
      type: ClusterSecurityGroupsReady
    - lastTransitionTime: "2024-07-25T09:40:17Z"
      status: "True"
      type: EKSAddonsConfigured
    - lastTransitionTime: "2024-07-25T09:22:19Z"
      reason: created
      severity: Info
      status: "False"
      type: EKSControlPlaneCreating
    - lastTransitionTime: "2024-07-25T09:40:19Z"
      status: "True"
      type: EKSControlPlaneReady
    - lastTransitionTime: "2024-07-25T09:40:19Z"
      status: "True"
      type: EKSIdentityProviderConfigured
    - lastTransitionTime: "2024-07-25T09:40:21Z"
      status: "True"
      type: IAMAuthenticatorConfigured
    - lastTransitionTime: "2024-07-25T09:14:13Z"
      status: "True"
      type: IAMControlPlaneRolesReady
    - lastTransitionTime: "2024-07-25T09:14:11Z"
      status: "True"
      type: SubnetsReady
    - lastTransitionTime: "2024-07-25T09:14:10Z"
      status: "True"
      type: VpcReady
  ...
  ready: true
  ...

Thus, the basic flow is the following:

• No status or no conditions -> Still in progress
• Iterate over all conditions
  • If the current condition is Ready and its current status is True, then the control plane is ready
  • If we find a condition with False status and Error severity, then we append the err msg to an err msgs accumulator to return at the end and report the Degraded status
• .status.ready == false -> Is not ready
• If didn't encounter any errors and the Ready condition is not True, it means that the creation is still in progress, so we report the Progressing status to ArgoCD.

Now, in terms of testing the health check in a real environment, we performed a full CAPA cluster build. Below are some screenshots during the testing process.

1. First the .status.ready was False

2. After some time, .status.ready became True, but OIDC reached the 100 limit (err messages are in the Health Details)

3. Then, I deleted an old sbx cluster and an OIDC became available. Immediately, after the OIDC assignment, the chart synced.

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.
• Optional. My organization is added to USERS.md.
• Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).