Kuryr ignores namespaces

Bug #1731486 reported by Michal Dulko
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kuryr-kubernetes
Fix Released
High
Luis Tomas Bolivar

Bug Description

Kuryr uses pod names to distinguish pods. Turns out we can have multiple pods with the same name in different namespaces. Kuryr needs to take that into account.

Changed in kuryr-kubernetes:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to kuryr-kubernetes (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/548313

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to kuryr-kubernetes (master)

Reviewed: https://review.openstack.org/548313
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=7061f4abac6d27c3b68dd6b55c6a3b0095f4b2c9
Submitter: Zuul
Branch: master

commit 7061f4abac6d27c3b68dd6b55c6a3b0095f4b2c9
Author: Luis Tomas Bolivar <email address hidden>
Date: Tue Feb 27 14:46:40 2018 +0000

    Make CNI Registry Plugin namespace aware

    As with the k8sCNIRegistryPlugin the watching is for the
    complete node, instead of per pod and namespace, we need
    to make registry information to account for the namespace
    where the pod is created to differentiate between different
    containers running on the same node, with the same name, but
    in a different namespace

    Related-Bug: 1731486
    Change-Id: I26e1dec6ae613c5316a45f93563c4a015df59441

Changed in kuryr-kubernetes:
assignee: nobody → Luis Tomas Bolivar (ltomasbo)
Changed in kuryr-kubernetes:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.