github/k3s - k3s - https://git.xinac.net

Commit Graph

Author	SHA1	Message	Date
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.	2020-09-21 09:56:03 -07:00
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).	2020-05-05 15:54:51 -07:00

Author

SHA1

Message

Date

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.

2020-09-21 09:56:03 -07:00

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).

2020-05-05 15:54:51 -07:00

2 Commits (3b8ec74049e1e211ec84efb753a2935912b3e4d9)