[Feature] timelimit on waitReadiness and/or barrier

[jcpunk]

Command

• check-image-updates
• delete
• deploy
• diff
• helm-pull
• helm-update
• list-images
• list-targets
• poke-images
• prune
• render
• seal
• validate
• version

Who are you?

No response

What do you want to do?

I'd like to set a timeout on waitReadiness and/or barrier.

Why do you need that?

My initial cluster init has 1 node. The Cilium CNI spawns a second pod to provide HA, but that pod cannot be scheduled on the same node as its primary. I'd like to set waitReadiness so that the CNI's basic functionality is indeed present before continuing, but with that container set to never launch it will never be ready. The ability to set a timeout would allow me to express my desire to wait for readiness or 30 seconds which ever is first.

[codablock]

@jcpunk can you fix the title of the issue?

[jcpunk]

oops, fixed.

[ukclivecox]

Is it also the case waitReadiness has a hard wired max as I see

⚠ timed out while waiting for readiness of milvus-operator/Deployment/milvus-operator (299s elapsed)

It would be great to have the ability to set longer timeouts?

** update **

I see actually there is a flag --readiness-timeout. So I suppose it would be nice if one could set it in a config file somewhere - is this possible?