-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
anget node working but access fail on anget node #10109
Comments
install logs
|
I'm not really sure what I'm looking at here, most of this output appears to be from autok3s. However, I do see that both of your nodes have the same internal IP address:
That is not going to work. Your nodes need unique IPs. Also note that the external-ip field is meant to be used for a public IP that is NATed to the private IP, it is not meant to be another interface with a private IP directly attached to the node. |
ok i redo the network and try it again, thanks! |
Environmental Info:
K3s Version:
k3s version v1.30.0+k3s1 (1454953)
go version go1.22.2
Node(s) CPU architecture, OS, and Version:
Linux server-01 5.4.0-181-generic #201-Ubuntu SMP Thu Mar 28 15:39:01 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
1 servers, 1 agents
Describe the bug:
anget node working but access fail on anget node
Steps To Reproduce:
use autok3s to install cluster
Expected behavior:
able to access logs on all pod
Actual behavior:
cant access on some pod
Additional context / logs:
deployment
ingress
The text was updated successfully, but these errors were encountered: