-
Notifications
You must be signed in to change notification settings - Fork 344
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
[IPv6] Add IPv6 support in NetworkPolicy #1272
Conversation
Thanks for your PR. The following commands are available:
|
9a2af81
to
de2efe5
Compare
1c94652
to
15eea1d
Compare
de2efe5
to
f0f069f
Compare
Codecov Report
@@ Coverage Diff @@
## ipv6 #1272 +/- ##
==========================================
+ Coverage 57.88% 57.93% +0.05%
==========================================
Files 155 155
Lines 13034 13164 +130
==========================================
+ Hits 7545 7627 +82
- Misses 4685 4726 +41
- Partials 804 811 +7
Flags with carried forward coverage won't be shown. Click here to find out more.
|
ffc1e77
to
90d2f6c
Compare
/test-ipv6-e2e |
0297228
to
82870ac
Compare
9969d93
to
62043fb
Compare
/test-ipv6-e2e |
62043fb
to
1de8152
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you consider changing the commit message to: Add IPv6 support for NetworkPolicy
@@ -57,7 +57,7 @@ type GroupMemberPod struct { | |||
// Pod maintains the reference to the Pod. | |||
Pod *PodReference | |||
// IP maintains the IPAddress of the Pod. | |||
IP IPAddress |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems an incompatible API group change. @tnqn
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, unversioned type can be changed any time, but v1beta1 type cannot be changed in this way directly. otherwise it breaks backwards compatibility. I think v1beta2.GroupMember supports multiple IPs per Pod, you could base on it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The controlplane.v1beta2 API is here #1405
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having some offline discussion with Quan, I will rebase the change on v1beta2. Since the PR to upgrade v1beta1 to v1beta2 is not merged yet, will rebase the code after that PR is ready.
1de8152
to
a9bf3a9
Compare
a9bf3a9
to
0c78aef
Compare
/test-all |
0c78aef
to
2a0a24d
Compare
Codecov Report
@@ Coverage Diff @@
## ipv6 #1272 +/- ##
===========================================
- Coverage 58.95% 41.87% -17.08%
===========================================
Files 157 85 -72
Lines 13072 10734 -2338
===========================================
- Hits 7706 4495 -3211
- Misses 4552 5838 +1286
+ Partials 814 401 -413
Flags with carried forward coverage won't be shown. Click here to find out more.
|
/test-ipv6-networkpolicy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor comment in addition to the changes needed to support v1beta2 for control plane APIs
/test-ipv6-networkpolicy |
ad98470
to
9fc5ebf
Compare
fc10cfc
to
3c3ec42
Compare
dd85a9e
to
267d1c0
Compare
Add support for IPv6 addresses in Network Policy.