You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i think the reason the addons failed to deploy is we started deploying cluster services too quickly before the nodegroups were healthy.
However, the Addon in crossplane should NEVER show as healthy if the remote resource is not. It almost feels like it was a fire and forget and not necessarily look at the actual health of the resource.
What happened?
coredns and cloudwatch addons failed to deploy
Relevant Error Output Snippet
No response
Crossplane Version
1.16
Provider Version
v1.14
Kubernetes Version
1.29
Kubernetes Distribution
EKS
Additional Info
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Affected Resource(s)
Resource MRs required to reproduce the bug
Steps to Reproduce
i think the reason the addons failed to deploy is we started deploying cluster services too quickly before the nodegroups were healthy.
However, the Addon in crossplane should NEVER show as healthy if the remote resource is not. It almost feels like it was a fire and forget and not necessarily look at the actual health of the resource.
What happened?
coredns and cloudwatch addons failed to deploy
Relevant Error Output Snippet
No response
Crossplane Version
1.16
Provider Version
v1.14
Kubernetes Version
1.29
Kubernetes Distribution
EKS
Additional Info
No response
The text was updated successfully, but these errors were encountered: