6 Commits

Author	SHA1	Message	Date
Matthias Schneider	56a083c812	fixed panic in network_policy_controller ... I have rebooted a newly created k3s etcd cluster and this panic was triggered: ``` k3s[948]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x45f2945] k3s[948]: goroutine 1 [running]: k3s[948]: github.com/rancher/k3s/pkg/agent/netpol.NewNetworkPolicyController(0xc00159e180, 0x61b4a60, 0xc006294000, 0xdf8475800, 0xc011d9a360, 0xc, 0x0, 0xc00bf545b8, 0x2b2edbc) k3s[948]: /home/x/git/k3s/pkg/agent/netpol/network_policy_controller.go:1698 +0x275 ``` Signed-off-by: Matthias Schneider <ms@wck.biz>	2020-06-29 20:49:24 +02:00
Darren Shepherd	a8d96112d9	Updates for k8s v1.18 support	2020-04-18 23:59:08 -07:00
Knic Knic	2346ccc63f	get build on windows and get api_server to work	2020-02-22 23:17:59 -08:00
Erik Wilson	5b98d10e4b	Warn if NPC can't start rather than fatal error ... If the ip_set kernel module is not available we should warn that the network policy controller can not start rather than cause a fatal error. Also adds module probing and config checks for ip_set.	2020-01-14 14:30:12 -07:00
yuzhiquan	7cc0110081	fix typo	2019-11-28 19:24:19 +08:00
Erik Wilson	da3a7c6bbc	Add network policy controller	2019-10-18 16:11:42 -07:00