Mirror/k3s
1
0
Fork 0
mirror of https://github.com/k3s-io/k3s.git synced 2024-06-07 19:41:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix code spell check

Browse Source 
Signed-off-by: Manuel Buil <mbuil@suse.com>
This commit is contained in:
Manuel Buil 2023-07-04 13:02:06 +02:00
parent 9c48d10eba
commit bca0adbca8
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/adrs/core-controller-user.md
View File

@ -17,7 +17,7 @@ Users may have policies in place that prohibit use of the `system:admin` account
* We will add a new kubeconfig for the K3s supervisor controllers: core functionality, deploy (AddOns; aka the manifests directory), and helm (HelmChart/HelmChartConfig). * We will add a new kubeconfig for the K3s supervisor controllers: core functionality, deploy (AddOns; aka the manifests directory), and helm (HelmChart/HelmChartConfig).
* Each of the three controllers will use a dedicated user-agent to further assist in discriminating between events, via both audit logs and resource ManageFields tracking. * Each of the three controllers will use a dedicated user-agent to further assist in discriminating between events, via both audit logs and resource ManageFields tracking.
* The new user account will use exisiting core Kubernetes group RBAC. * The new user account will use existing core Kubernetes group RBAC.
## Consequences ## Consequences

2
pkg/agent/tunnel/tunnel.go
View File

@ -337,7 +337,7 @@ func (a *agentTunnel) watchEndpoints(ctx context.Context, apiServerReady <-chan
var debounceCtx context.Context var debounceCtx context.Context
debounceCtx, cancelUpdate = context.WithCancel(ctx) debounceCtx, cancelUpdate = context.WithCancel(ctx)
// When joining the cluster, the apiserver adds, removes, and then readds itself to // When joining the cluster, the apiserver adds, removes, and then re-adds itself to
// the endpoint list several times. This causes a bit of thrashing if we react to // the endpoint list several times. This causes a bit of thrashing if we react to
// endpoint changes immediately. Instead, perform the endpoint update in a // endpoint changes immediately. Instead, perform the endpoint update in a
// goroutine that sleeps for a short period before checking for changes and updating // goroutine that sleeps for a short period before checking for changes and updating