Add a direct dependency on cluster_id before deciding it's ready

GSA-TTS / datagov-brokerpak-eks

Broker AWS EKS instances using the OSBAPI (eg from cloud.gov)

Other

9 stars 7 forks source link

Add a direct dependency on cluster_id before deciding it's ready #71

Closed mogul closed 2 years ago

mogul commented 2 years ago

With count=0 on some Fargate resources, there's no dependency that prevents, say, helm_releases from attempting to apply/destroy immediately, even when the cluster's not healthy and nodes aren't available.

mogul commented 2 years ago

@nickumia-reisys FYI... I am keeping this in draft state until I've determined that there are no other fixes preventing clean apply/destroy.

mogul commented 2 years ago

No luck. 😞