Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Agent node disk inexplicably skyrocketed and then disconnected #9773

Closed
DokiDoki1103 opened this issue Mar 23, 2024 · 0 comments
Closed

Agent node disk inexplicably skyrocketed and then disconnected #9773

DokiDoki1103 opened this issue Mar 23, 2024 · 0 comments

Comments

@DokiDoki1103
Copy link

Environmental Info:
K3s Version:

k3s version v1.28.7+k3s1 (051b14b)
go version go1.21.7
Node(s) CPU architecture, OS, and Version:

Linux VM-20-16-centos 3.10.0-1160.108.1.el7.x86_64 #1 SMP Thu Jan 25 16:17:31 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:

1 servers, 5 agents
Describe the bug:

I deployed K3s through the public network。After using it for a period of time, the agent node's disk usage skyrocketed, and then the node crashed。Using the Wireguard native network plugin。
Steps To Reproduce:

  • Installed K3s:

Expected behavior:

Actual behavior:

Additional context / logs:

@k3s-io k3s-io locked and limited conversation to collaborators Mar 23, 2024
@brandond brandond converted this issue into discussion #9775 Mar 23, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
Status: Done Issue
Development

No branches or pull requests

1 participant