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

api_topologies: Don't put namespace filters on containers-by-dns/image #2506

Merged

Conversation

ekimekim
Copy link
Contributor

@ekimekim ekimekim commented May 8, 2017

This should never have been added. The IsNamespace filter will always return false for these nodes.
It isn't even clear what this filter would mean, even if implemented, since those nodes don't map to a single
container and therefore not to a single namespace.

This bug was introduced in #2285 and is very problematic
because it means the default view on those topologies is blank if the 'default' k8s namespace is present.

This should never have been added. The IsNamespace filter will always return false for these nodes.
It isn't even clear what this filter would mean, even if implemented, since those nodes don't map to a single
container and therefore not to a single namespace.
@ekimekim ekimekim requested a review from 2opremio May 8, 2017 21:00
@rade
Copy link
Member

rade commented May 8, 2017

It may be worth releasing a 1.3.1 for this.

@2opremio
Copy link
Contributor

2opremio commented May 9, 2017

It may be worth releasing a 1.3.1 for this.

Agreed

@ekimekim ekimekim merged commit d6c1308 into master May 9, 2017
@ekimekim ekimekim deleted the mike/k8s-filters/remove-on-container-subtopologies branch May 9, 2017 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants