Does anyone know why “health” checking is implicitly part of the “create” lifecycle for k8s objects? If health fails, it thinks that create fails, and the object doesn’t get stored in state. Subsequent runs fail with “already exists” error from kubernetes.
I filed an issue:
I think this is a fairly high priority / common use case.
05/29/2022, 12:58 AM
By default, the provider's await logic for resources like services is to wait for availability. This can be disabled by adding the following annotation to the resource: