14 Commits (c6d0afd0cbce7ee69dcb6c9d98deef60aa62b1c6)

Author	SHA1	Message	Date
Brad Davidson	7e447692c5	Fix issue with RKE2 servers hanging on listing apiserver addresses ... Signed-off-by: Brad Davidson <brad.davidson@rancher.com>	3 years ago
Roberto Bonafiglia	06c779c57d	Fixed loadbalancer in case of IPv6 addresses ... Signed-off-by: Roberto Bonafiglia <roberto.bonafiglia@suse.com>	3 years ago
Luther Monson	9a849b1bb7	[master] changing package to k3s-io (#4846) ... * changing package to k3s-io Signed-off-by: Luther Monson <luther.monson@gmail.com> Co-authored-by: Derek Nola <derek.nola@suse.com>	3 years ago
Brad Davidson	5014c9e0e8	Fix adding etcd-only node to existing cluster ... Signed-off-by: Brad Davidson <brad.davidson@rancher.com>	3 years ago
Brad Davidson	8ace8975d2	Don't start up multiple apiserver load balancers ... get() is called in a loop until client configuration is successfully retrieved. Each iteration will try to configure the apiserver proxy, which will in turn create a new load balancer. Skip creating a new load balancer if we already have one. Signed-off-by: Brad Davidson <brad.davidson@rancher.com>	4 years ago
Brad Davidson	c0d129003b	Handle loadbalancer port in TIME_WAIT ... If the port wanted by the client load balancer is in TIME_WAIT, startup will fail. Set SO_REUSEPORT so that it can be listened on again immediately. The configurable Listen call wants a context, so plumb that through as well. Signed-off-by: Brad Davidson <brad.davidson@rancher.com>	4 years ago
Brad Davidson	7cdfaad6ce	Always use static ports for client load-balancers (#3026) ... * Always use static ports for the load-balancers This fixes an issue where RKE2 kube-proxy daemonset pods were failing to communicate with the apiserver when RKE2 was restarted because the load-balancer used a different port every time it started up. This also changes the apiserver load-balancer port to be 1 below the supervisor port instead of 1 above it. This makes the apiserver port consistent at 6443 across servers and agents on RKE2. Additional fixes below were required to successfully test and use this change on etcd-only nodes. * Actually add lb-server-port flag to CLI * Fix nil pointer when starting server with --disable-etcd but no --server * Don't try to use full URI as initial load-balancer endpoint * Fix etcd load-balancer pool updates * Update dynamiclistener to fix cert updates on etcd-only nodes * Handle recursive initial server URL in load balancer * Don't run the deploy controller on etcd-only nodes	4 years ago
Hussein Galal	5749f66aa3	Add disable flags for control components (#2900) ... * Add disable flags to control components Signed-off-by: galal-hussein <hussein.galal.ahmed.11@gmail.com> * golint Signed-off-by: galal-hussein <hussein.galal.ahmed.11@gmail.com> * more fixes Signed-off-by: galal-hussein <hussein.galal.ahmed.11@gmail.com> * fixes to disable flags Signed-off-by: galal-hussein <hussein.galal.ahmed.11@gmail.com> * Add comments to functions Signed-off-by: galal-hussein <hussein.galal.ahmed.11@gmail.com> * Fix joining problem Signed-off-by: galal-hussein <hussein.galal.ahmed.11@gmail.com> * more fixes Signed-off-by: galal-hussein <hussein.galal.ahmed.11@gmail.com> * golint Signed-off-by: galal-hussein <hussein.galal.ahmed.11@gmail.com> * fix ticker Signed-off-by: galal-hussein <hussein.galal.ahmed.11@gmail.com> * fix role labels Signed-off-by: galal-hussein <hussein.galal.ahmed.11@gmail.com> * more fixes Signed-off-by: galal-hussein <hussein.galal.ahmed.11@gmail.com>	4 years ago
Brian Downs	ba70c41cce	Initial Logging Output Update (#2246) ... This attempts to update logging statements to make them consistent through out the code base. It also adds additional context to messages where possible, simplifies messages, and updates level where necessary.	4 years ago
Darren Shepherd	2f5ee914f9	Add supervisor port ... In k3s today the kubernetes API and the /v1-k3s API are combined into one http server. In rke2 we are running unmodified, non-embedded Kubernetes and as such it is preferred to run k8s and the /v1-k3s API on different ports. The /v1-k3s API port is called the SupervisorPort in the code. To support this separation of ports a new shim was added on the client in then pkg/agent/proxy package that will launch two load balancers instead of just one load balancer. One load balancer for 6443 and the other for 9345 (which is the supervisor port).	5 years ago
Erik Wilson	29865fd9c9	Remove agent proxy	5 years ago
Erik Wilson	2c9444399b	Refactor certs	5 years ago
Darren Shepherd	c0702b0492	Port to wrangler	6 years ago
Darren Shepherd	62c62cc7b4	Continued refactoring	6 years ago