Skip to content

[Release-1.29] - K3s startup sequencing is inefficient #12131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
brandond opened this issue Apr 14, 2025 · 1 comment
Closed

[Release-1.29] - K3s startup sequencing is inefficient #12131

brandond opened this issue Apr 14, 2025 · 1 comment
Assignees

Comments

@brandond
Copy link
Member

Backport fix for K3s startup sequencing is inefficient

@fmoral2
Copy link
Contributor

fmoral2 commented Apr 24, 2025

-All tests from https://github.com/rancher/distros-test-framework/blob/main/entrypoint/validatecluster/validatecluster_test.go
PASS

Validated on Version:

-$ k3s version v1.29.15+k3s-5aac2aaf (5aac2aaf)

Environment Details

Infrastructure
Cloud EC2 instance

Node(s) CPU architecture, OS, and Version:
NAME="SLES"
VERSION="15-SP5"
VERSION_ID="15.5"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5"
ID="sles"
ID_LIKE="suse"

Cluster Configuration:
1 node servers

Steps to validate the fix

1.Install k3s
2. Validates start up logs
3. Check the API server readiness logs
4. Validate basic tests

Validation Results:

k3s version v1.29.15+k3s-5aac2aaf (5aac2aaf)


showing the new logs for api server readiness.
 ~$ sudo journalctl -u k3s | grep -B 10  -E "server readiness" 
Apr 24 09:24:09 ip-172-31-23-55 k3s[1773]: time="2025-04-24T09:24:09Z" level=info msg="certificate CN=system:kube-proxy signed by CN=k3s-client-ca@1745486648: notBefore=2025-04-24 09:24:08 +0000 UTC notAfter=2026-04-24 09:24:09 +0000 UTC"
Apr 24 09:24:10 ip-172-31-23-55 k3s[1773]: time="2025-04-24T09:24:10Z" level=info msg="certificate CN=system:k3s-controller signed by CN=k3s-client-ca@1745486648: notBefore=2025-04-24 09:24:08 +0000 UTC notAfter=2026-04-24 09:24:10 +0000 UTC"
Apr 24 09:24:10 ip-172-31-23-55 k3s[1773]: time="2025-04-24T09:24:10Z" level=info msg="Module overlay was already loaded"
Apr 24 09:24:10 ip-172-31-23-55 k3s[1773]: time="2025-04-24T09:24:10Z" level=info msg="Module br_netfilter was already loaded"
Apr 24 09:24:10 ip-172-31-23-55 k3s[1773]: time="2025-04-24T09:24:10Z" level=info msg="Set sysctl 'net/netfilter/nf_conntrack_tcp_timeout_close_wait' to 3600"
Apr 24 09:24:10 ip-172-31-23-55 k3s[1773]: time="2025-04-24T09:24:10Z" level=info msg="Set sysctl 'net/ipv4/conf/all/forwarding' to 1"
Apr 24 09:24:10 ip-172-31-23-55 k3s[1773]: time="2025-04-24T09:24:10Z" level=info msg="Set sysctl 'net/netfilter/nf_conntrack_max' to 131072"
Apr 24 09:24:10 ip-172-31-23-55 k3s[1773]: time="2025-04-24T09:24:10Z" level=info msg="Set sysctl 'net/netfilter/nf_conntrack_tcp_timeout_established' to 86400"
Apr 24 09:24:10 ip-172-31-23-55 k3s[1773]: time="2025-04-24T09:24:10Z" level=info msg="Logging containerd to /var/lib/rancher/k3s/agent/containerd/containerd.log"
Apr 24 09:24:10 ip-172-31-23-55 k3s[1773]: time="2025-04-24T09:24:10Z" level=info msg="Running containerd -c /var/lib/rancher/k3s/agent/etc/containerd/config.toml -a /run/k3s/containerd/containerd.sock --state /run/k3s/containerd --root /var/lib/rancher/k3s/agent/containerd"
Apr 24 09:24:10 ip-172-31-23-55 k3s[1773]: time="2025-04-24T09:24:10Z" level=info msg="Polling for API server readiness: GET /readyz failed: the server is currently unable to handle the request"
--
Apr 24 09:24:12 ip-172-31-23-55 k3s[1773]: I0424 09:24:12.583942    1773 handler.go:275] Adding GroupVersion apps v1 to ResourceManager
Apr 24 09:24:12 ip-172-31-23-55 k3s[1773]: W0424 09:24:12.583978    1773 genericapiserver.go:742] Skipping API apps/v1beta2 because it has no resources.
Apr 24 09:24:12 ip-172-31-23-55 k3s[1773]: W0424 09:24:12.583988    1773 genericapiserver.go:742] Skipping API apps/v1beta1 because it has no resources.
Apr 24 09:24:12 ip-172-31-23-55 k3s[1773]: I0424 09:24:12.584930    1773 handler.go:275] Adding GroupVersion admissionregistration.k8s.io v1 to ResourceManager
Apr 24 09:24:12 ip-172-31-23-55 k3s[1773]: W0424 09:24:12.584953    1773 genericapiserver.go:742] Skipping API admissionregistration.k8s.io/v1beta1 because it has no resources.
Apr 24 09:24:12 ip-172-31-23-55 k3s[1773]: W0424 09:24:12.584962    1773 genericapiserver.go:742] Skipping API admissionregistration.k8s.io/v1alpha1 because it has no resources.
Apr 24 09:24:12 ip-172-31-23-55 k3s[1773]: I0424 09:24:12.585571    1773 handler.go:275] Adding GroupVersion events.k8s.io v1 to ResourceManager
Apr 24 09:24:12 ip-172-31-23-55 k3s[1773]: W0424 09:24:12.585594    1773 genericapiserver.go:742] Skipping API events.k8s.io/v1beta1 because it has no resources.
Apr 24 09:24:12 ip-172-31-23-55 k3s[1773]: I0424 09:24:12.589008    1773 handler.go:275] Adding GroupVersion apiregistration.k8s.io v1 to ResourceManager
Apr 24 09:24:12 ip-172-31-23-55 k3s[1773]: W0424 09:24:12.589037    1773 genericapiserver.go:742] Skipping API apiregistration.k8s.io/v1beta1 because it has no resources.
Apr 24 09:24:12 ip-172-31-23-55 k3s[1773]: time="2025-04-24T09:24:12Z" level=info msg="Polling for API server readiness: GET /readyz failed: unknown"
 
 


    ```

@fmoral2 fmoral2 closed this as completed Apr 24, 2025
@github-project-automation github-project-automation bot moved this from To Test to Done Issue in K3s Development Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done Issue
Development

No branches or pull requests

2 participants