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
Not all k8s resources implement the conditions in their status. However it may still be necessary to wait on them being ready. Since operations in K8s are asynchronous, an item later depending on this may fail.
A good example is the kind Service. This does not implement conditions as shown in kubernetes/kubernetes#80828. My ansible may need to wait for this service to have acquired an External IP address before using in a further task - perhaps feeding that IP into a network infrastructure rule (firewall, DNS or other).
A similar ticket exists for the Kubectl command - kubernetes/kubernetes#83094 - waiting for an arbitrary json path.
ISSUE TYPE
Feature Idea
COMPONENT NAME
module k8s
ADDITIONAL INFORMATION
- name: Deploy the dashboard service (lb)community.kubernetes.k8s:
<<: *k8s_authtemplate: dash-service.yamlwait: yeswait_for: .status.loadBalancer.ingress[*].ip
SUMMARY
Not all k8s resources implement the conditions in their status. However it may still be necessary to wait on them being ready. Since operations in K8s are asynchronous, an item later depending on this may fail.
A good example is the kind Service. This does not implement conditions as shown in kubernetes/kubernetes#80828. My ansible may need to wait for this service to have acquired an External IP address before using in a further task - perhaps feeding that IP into a network infrastructure rule (firewall, DNS or other).
A similar ticket exists for the Kubectl command - kubernetes/kubernetes#83094 - waiting for an arbitrary json path.
ISSUE TYPE
COMPONENT NAME
module k8s
ADDITIONAL INFORMATION
Something like that could be waiting for an ingress IP to appear. Perhaps inspiration could come from kubernetes/kubernetes#83094 (comment).
The text was updated successfully, but these errors were encountered: