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.

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

Bindings were not correctly removed across namespaces on pod update and delete #4329

Merged

Conversation

smarterclayton
Copy link
Contributor

When pods are deleted (or updated) and there is another pod bound to that host with the same pod name in a different namespace, the wrong binding can get removed. It's likely people out there using multiple namespaces today have corrupted bindings - we really need to be able to regenerate / check the bindings.

…nd delete

BoundPods must be checked for Name and Namespace equality, not just name
equality. In the future, we should also check for UID equality.
@smarterclayton smarterclayton added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. kind/bug Categorizes issue or PR as related to a bug. labels Feb 11, 2015
@roberthbailey
Copy link
Contributor

The fix LGTM but I'll defer to someone who knows more about this part of the code.

/cc @brendandburns @thockin

@smarterclayton
Copy link
Contributor Author

@derekwaynecarr please review - I want to get this merged

@derekwaynecarr
Copy link
Member

LGTM - that was a bad bug ;-)

smarterclayton added a commit that referenced this pull request Feb 12, 2015
…oved

Bindings were not correctly removed across namespaces on pod update and delete
@smarterclayton smarterclayton merged commit b2d50ce into kubernetes:master Feb 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants