github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/pkg/proxy/util/BUILD

57 lines
1.6 KiB
Python
Raw Normal View History

move UDP conntrack operations together to pkg/proxy/util/conntrack.go
2017-07-24 07:02:07 +00:00
load("@io_bazel_rules_go//go:def.bzl", "go_library", "go_test")
Userspace proxy should remove conntrack entries This changes the userspace proxy so that it cleans up its conntrack settings when a service is removed (as the iptables proxy already does). This could theoretically cause problems when a UDP service as deleted and recreated quickly (with the same IP address). As long as packets from the same UDP source IP and port were going to the same destination IP and port, the the conntrack would apply and the packets would be sent to the old destination. This is astronomically unlikely if you did not specify the IP address to use in the service, and even then, only happens with an "established" UDP connection. However, in cases where a service could be "switched" between using the iptables proxy and the userspace proxy, this case becomes much more frequent.
2016-07-22 18:26:36 +00:00
go_library(
name = "go_default_library",
move IsLocalIP() and ShouldSkipService() to pkg/proxy/util
2017-08-16 07:17:36 +00:00
srcs = [
consume endpoints IPPart function in util
2017-10-10 03:16:06 +00:00
"endpoints.go",
update bazel
2018-02-26 09:03:26 +00:00
"network.go",
clean up LocalPort in proxier.go
2017-08-22 02:49:24 +00:00
"port.go",
move IsLocalIP() and ShouldSkipService() to pkg/proxy/util
2017-08-16 07:17:36 +00:00
"utils.go",
],
update BUILD files
2017-10-12 20:52:10 +00:00
importpath = "k8s.io/kubernetes/pkg/proxy/util",
move UDP conntrack operations together to pkg/proxy/util/conntrack.go
2017-07-24 07:02:07 +00:00
visibility = ["//visibility:public"],
move IsLocalIP() and ShouldSkipService() to pkg/proxy/util
2017-08-16 07:17:36 +00:00
deps = [
update bazel
2018-08-15 14:04:42 +00:00
"//pkg/apis/core/v1/helper:go_default_library",
Run hack/update-bazel.sh
2018-06-21 21:51:55 +00:00
"//staging/src/k8s.io/api/core/v1:go_default_library",
"//staging/src/k8s.io/apimachinery/pkg/types:go_default_library",
"//staging/src/k8s.io/apimachinery/pkg/util/sets:go_default_library",
"//staging/src/k8s.io/client-go/tools/record:go_default_library",
Move from glog to klog - Move from the old github.com/golang/glog to k8s.io/klog - klog as explicit InitFlags() so we add them as necessary - we update the other repositories that we vendor that made a similar change from glog to klog * github.com/kubernetes/repo-infra * k8s.io/gengo/ * k8s.io/kube-openapi/ * github.com/google/cadvisor - Entirely remove all references to glog - Fix some tests by explicit InitFlags in their init() methods Change-Id: I92db545ff36fcec83afe98f550c9e630098b3135
2018-11-09 18:49:10 +00:00
"//vendor/k8s.io/klog:go_default_library",
Refactor to use k8s.io/utils/net/ package instead of kubernetes/pkg/util/net/sets Signed-off-by: Ashish Ranjan <ashishranjan738@gmail.com>
2019-02-02 07:01:21 +00:00
"//vendor/k8s.io/utils/net:go_default_library",
move IsLocalIP() and ShouldSkipService() to pkg/proxy/util
2017-08-16 07:17:36 +00:00
],
Userspace proxy should remove conntrack entries This changes the userspace proxy so that it cleans up its conntrack settings when a service is removed (as the iptables proxy already does). This could theoretically cause problems when a UDP service as deleted and recreated quickly (with the same IP address). As long as packets from the same UDP source IP and port were going to the same destination IP and port, the the conntrack would apply and the packets would be sent to the old destination. This is astronomically unlikely if you did not specify the IP address to use in the service, and even then, only happens with an "established" UDP connection. However, in cases where a service could be "switched" between using the iptables proxy and the userspace proxy, this case becomes much more frequent.
2016-07-22 18:26:36 +00:00
)
go_test(
name = "go_default_test",
move IsLocalIP() and ShouldSkipService() to pkg/proxy/util
2017-08-16 07:17:36 +00:00
srcs = [
consume endpoints IPPart function in util
2017-10-10 03:16:06 +00:00
"endpoints_test.go",
clean up LocalPort in proxier.go
2017-08-22 02:49:24 +00:00
"port_test.go",
move IsLocalIP() and ShouldSkipService() to pkg/proxy/util
2017-08-16 07:17:36 +00:00
"utils_test.go",
],
Autogenerate BUILD files
2017-12-23 21:06:26 +00:00
embed = [":go_default_library"],
update godep
2017-07-19 20:19:12 +00:00
deps = [
update bazel
2018-02-26 09:03:26 +00:00
"//pkg/proxy/util/testing:go_default_library",
update bazel
2018-08-15 14:04:42 +00:00
"//staging/src/k8s.io/api/core/v1:go_default_library",
Run hack/update-bazel.sh
2018-06-21 21:51:55 +00:00
"//staging/src/k8s.io/apimachinery/pkg/apis/meta/v1:go_default_library",
"//staging/src/k8s.io/apimachinery/pkg/types:go_default_library",
"//staging/src/k8s.io/apimachinery/pkg/util/sets:go_default_library",
update godep
2017-07-19 20:19:12 +00:00
],
Userspace proxy should remove conntrack entries This changes the userspace proxy so that it cleans up its conntrack settings when a service is removed (as the iptables proxy already does). This could theoretically cause problems when a UDP service as deleted and recreated quickly (with the same IP address). As long as packets from the same UDP source IP and port were going to the same destination IP and port, the the conntrack would apply and the packets would be sent to the old destination. This is astronomically unlikely if you did not specify the IP address to use in the service, and even then, only happens with an "established" UDP connection. However, in cases where a service could be "switched" between using the iptables proxy and the userspace proxy, this case becomes much more frequent.
2016-07-22 18:26:36 +00:00
)
filegroup(
name = "package-srcs",
srcs = glob(["**"]),
tags = ["automanaged"],
visibility = ["//visibility:private"],
)
filegroup(
name = "all-srcs",
update bazel
2018-02-26 09:03:26 +00:00
srcs = [
":package-srcs",
"//pkg/proxy/util/testing:all-srcs",
],
Userspace proxy should remove conntrack entries This changes the userspace proxy so that it cleans up its conntrack settings when a service is removed (as the iptables proxy already does). This could theoretically cause problems when a UDP service as deleted and recreated quickly (with the same IP address). As long as packets from the same UDP source IP and port were going to the same destination IP and port, the the conntrack would apply and the packets would be sent to the old destination. This is astronomically unlikely if you did not specify the IP address to use in the service, and even then, only happens with an "established" UDP connection. However, in cases where a service could be "switched" between using the iptables proxy and the userspace proxy, this case becomes much more frequent.
2016-07-22 18:26:36 +00:00
tags = ["automanaged"],
move UDP conntrack operations together to pkg/proxy/util/conntrack.go
2017-07-24 07:02:07 +00:00
visibility = ["//visibility:public"],
Userspace proxy should remove conntrack entries This changes the userspace proxy so that it cleans up its conntrack settings when a service is removed (as the iptables proxy already does). This could theoretically cause problems when a UDP service as deleted and recreated quickly (with the same IP address). As long as packets from the same UDP source IP and port were going to the same destination IP and port, the the conntrack would apply and the packets would be sent to the old destination. This is astronomically unlikely if you did not specify the IP address to use in the service, and even then, only happens with an "established" UDP connection. However, in cases where a service could be "switched" between using the iptables proxy and the userspace proxy, this case becomes much more frequent.
2016-07-22 18:26:36 +00:00
)