-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
k8s: add support for ipFamilies to services #14914
Conversation
1114368
to
e20e1c9
Compare
test-me-please |
retest-4.9 |
7f7c3d8
to
05599e3
Compare
retest-4.9 |
05599e3
to
8f17644
Compare
8f17644
to
b69bada
Compare
29c8f7d
to
7063e1e
Compare
7063e1e
to
9fbd076
Compare
test-gke |
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.
🚀
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.
I'm not quite sure why GitHub pulled in janitor codeowners for review, all of the files seem to have other codeowners already. Reviewers seem otherwise happy so I see no need to interdict.
NewClusterService() and EqualsClusterService() were inadvertently broken when support for ipFamilies was added, leaving the 'Ports' in service empty. This made all cluster services inaccessible to External Workloads. Fix this by collecting the ports accross all front-ends. This assumes that each front-end will be serving the same ports. Fixes: cilium#14914 Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
NewClusterService() and EqualsClusterService() were inadvertently broken when support for ipFamilies was added, leaving the 'Ports' in service empty. This made all cluster services inaccessible to External Workloads. Fix this by collecting the ports accross all front-ends. This assumes that each front-end will be serving the same ports. Fixes: #14914 Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
NewClusterService() and EqualsClusterService() were inadvertently broken when support for ipFamilies was added, leaving the 'Ports' in service empty. This made all cluster services inaccessible to External Workloads. Fix this by collecting the ports accross all front-ends. This assumes that each front-end will be serving the same ports. Fixes: #14914 Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
[ upstream commit 929c28f ] NewClusterService() and EqualsClusterService() were inadvertently broken when support for ipFamilies was added, leaving the 'Ports' in service empty. This made all cluster services inaccessible to External Workloads. Fix this by collecting the ports accross all front-ends. This assumes that each front-end will be serving the same ports. Fixes: cilium#14914 Signed-off-by: Jarno Rajahalme <jarno@isovalent.com> Signed-off-by: Tobias Klauser <tobias@cilium.io>
[ upstream commit 929c28f ] NewClusterService() and EqualsClusterService() were inadvertently broken when support for ipFamilies was added, leaving the 'Ports' in service empty. This made all cluster services inaccessible to External Workloads. Fix this by collecting the ports accross all front-ends. This assumes that each front-end will be serving the same ports. Fixes: #14914 Signed-off-by: Jarno Rajahalme <jarno@isovalent.com> Signed-off-by: Tobias Klauser <tobias@cilium.io>
Fixes #13074
Service spec:
Earlier a service created with dual-stack IP family was not parsed correctly for datapath service in Cilium:
After the patch: