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

Drop extensions.NetworkPolicy #46626

Closed
danwinship opened this issue May 30, 2017 · 3 comments
Closed

Drop extensions.NetworkPolicy #46626

danwinship opened this issue May 30, 2017 · 3 comments
Assignees
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@danwinship
Copy link
Contributor

After #39164 we now have two separate "internal" NetworkPolicy objects: extensions.NetworkPolicy, and networking.NetworkPolicy. Additionally, there are two separate packages under pkg/registry (pkg/registry/extensions/networkpolicy and pkg/registry/network/networkpolicy), two sets of kubectl printers/describers, and some handwritten conversions in pkg/apis/extensions/v1beta1 and pkg/apis/networking/v1.

It ought to be possible to get rid of this duplication, without changing the externally-visible API.

@danwinship
Copy link
Contributor Author

/assign @thockin

@thockin
Copy link
Member

thockin commented May 31, 2017 via email

@thockin
Copy link
Member

thockin commented May 31, 2017

Worst case is we do this after 1.7 cuts

@thockin thockin added the sig/network Categorizes an issue or PR as relevant to SIG Network. label May 31, 2017
k8s-github-robot pushed a commit that referenced this issue Aug 15, 2017
Automatic merge from submit-queue

Drop extensions internal Network* types

Fixes #46626
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Development

No branches or pull requests

2 participants