Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove cloning label from target pods to fix pod affinity. #280

Merged
merged 1 commit into from
Jul 31, 2018
Merged

Remove cloning label from target pods to fix pod affinity. #280

merged 1 commit into from
Jul 31, 2018

Commits on Jul 31, 2018

  1. Having the cloning label in the target pod, make the pod affinity fails. 

    The target pod looks for a pod with a specific label (specified in the pod affinity) that matches the source pod label.
In my case the target pod included this label as well, so we can see that the target pod found matching pod, but it is the WRONG pod. It's itself!!
The target was running without finding the source pod first.
If we remove this label from the target pod, it will find the source pod and then will be scheduled on the same node.
If it does not find the source pod (because the scheduler tried to schedule it before the source pod), it will be in 'Pending' state until the source pod is scheduled, and then will be running on the same node.
kubevirt#279
    @zvikorn
    zvikorn committed Jul 31, 2018
    Configuration menu
    Copy the full SHA
    2432b0c View commit details
    Browse the repository at this point in the history