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
In some cases, I have different instances of the same daemonset with slightly different config based on hardware. for example, I might run two different daemonsets for flannel, each specifying which --interface xxx to bind to, if the host has multiple nics and floating names.
When launching a pod that depends on the daemonset, it may not really care which of them it runs against, but instead should match a daemonset pod based on a label, so it can match either. Could a new type be added that lets wait until a given labeled pod is running on the same host as you?
The text was updated successfully, but these errors were encountered:
In some cases, I have different instances of the same daemonset with slightly different config based on hardware. for example, I might run two different daemonsets for flannel, each specifying which --interface xxx to bind to, if the host has multiple nics and floating names.
When launching a pod that depends on the daemonset, it may not really care which of them it runs against, but instead should match a daemonset pod based on a label, so it can match either. Could a new type be added that lets wait until a given labeled pod is running on the same host as you?
The text was updated successfully, but these errors were encountered: