-
Notifications
You must be signed in to change notification settings - Fork 275
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
setting HA on opensuse microOS #4908
Comments
the three nodes has ceph storage with podman. |
|
|
containerd logs and kubelet logs.
|
I think it's network issue. |
The VPN seems to be causing network issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environmental Info:
RKE2 Version:
rke2 version v1.27.6+rke2r1 (5cc9c77)
go version go1.20.8 X:boringcrypto
Node(s) CPU architecture, OS, and Version:
Linux se4.cola23subnet.cola123.oraclevcn.com 6.5.6-1-default #1 SMP PREEMPT_DYNAMIC Fri Oct 6 11:20:48 UTC 2023 (c97c2df) aarch64 aarch64 aarch64 GNU/Linux
Cluster Configuration:
to be: 3servers, 2 agents
Describe the bug:
kubelet and kube-proxy container not run correctly
Steps To Reproduce:
Install 1st server whit this /etc/rancher/rke2/config.yaml
start rke2-server on 2nd server with this /etc/rancher/rke2/config.yaml
Expected behavior:
runing kubelet and kube-proxy container
Actual behavior:
keep dyed that containers
Additional context / logs:
how can I get the dead continaer's logs?
The text was updated successfully, but these errors were encountered: