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

Bug 1825355: node/vnids: Correctly handle case where NetNamespace watch is far behind #134

Merged
merged 1 commit into from Apr 29, 2020
Merged

Bug 1825355: node/vnids: Correctly handle case where NetNamespace watch is far behind #134

merged 1 commit into from Apr 29, 2020

Commits on Apr 28, 2020

  1. node/vnids: Correctly handle case where NetNamespace watch is far behind 

    When adding a pod, if the NetNamespace isn't found, we'll issue a GET
directly to the apiserver and treat it as an ADD. Except we didn't
actually handle it correctly, and caused NetworkPolicy to ignore this
NetNS forever.

Fixes: rhbz 1825355
    @squeed
    squeed committed Apr 28, 2020
    Copy the full SHA
    b5f89a6 View commit details
    Browse the repository at this point in the history