custom timeouts are available for all resources, but our Kubernetes provider also has custom await options which can be overridden via annotations
e
echoing-activity-32278
12/29/2021, 10:04 AM
This sounds like dup of functionality.
q
quiet-wolf-18467
12/29/2021, 10:14 AM
There's some nuances to each option. Timeouts at the resource level are for resource CRUD operations. Timeouts on Kubernetes annotations allow finer control over the lifecycle / readiness of those resources. SkipAwait might be what you're looking for and I'd love to see this available at a provider level. Leave it with me 😀