Comments (5)
Did you set --node-ip and --node-external-ip to the correct values for each of the agents, or just the servers?
Based on the information you shared, it sounds like the apiserver is trying to connect to the kubelet's external IP to get logs. Normally it would connect to the public IP using the agent tunnel, so I suspect that the internal and external IPs are not being set properly.
from k3s.
Thanks for the help Brandon!
For the servers, node-ip defaults to the private IP (I believed) which would be 192.x.x..
The agents don't have these set as they only have public IP addresses which are used as the nodes IP addresses.
Should I set node-ip and node-external-ip specifically to their public addresses?
This is the current setup
Server node 1: node-ip not set, node-external-ip set to NAT gateway
Server node 2: node-ip not set, node-external-ip set to NAT gateway
Server node 3: node-ip not set, node-external-ip set to NAT gateway
Agent 1: node-ip, node-external-ip not set but only public iP
Agent 2: node-ip, node-external-ip not set but only public iP
Agent 3: node-ip, node-external-ip not set but only public iP
from k3s.
Related to #7355 I think. Base on the comment #7355 (comment), I'm still unable to get it working right.
from k3s.
Thanks for linking that issue @tdtgit !
I don't think it is the same, but it helped me identify the issue a little bit better.
I'm not entirely sure if what I'm trying to achieve is even possible mind you, concretely this is where I'm doubtful:
Since I only have one NAT gateway, I only have one public IP address. So this is my server config:
MY_EXTERNAL_IP=80.xxx.xxx.xxx
server 1: --node-ip 192.168.88.2 --node-external-ip ${MY_EXTERNAL_IP} --flannel-external-ip
server 2: --node-ip <internal-ip> --node-external-ip ${MY_EXTERNAL_IP} --flannel-external-ip
server 3: --node-ip <internal-ip> --node-external-ip ${MY_EXTERNAL_IP} --flannel-external-ip
My agent config:
agent 1: --node-ip 80.xxx.xxx.xxx --node-external-ip 80.xxx.xxx.xxx --server https://80.xxx.xxx.xxx:6443
agent 2: --node-ip 80.xxx.xxx.xxx --node-external-ip 80.xxx.xxx.xxx --server https://80.xxx.xxx.xxx:6443
agent 3: --node-ip 80.xxx.xxx.xxx --node-external-ip 80.xxx.xxx.xxx --server https://80.xxx.xxx.xxx:6443
Here is some additional information:
- Pods deployed on server1 - server 3 are not able to contact services (f.e. the kubernetes API)
- When running
wg show
I get this output (server 3):
interface: flannel-wg
public key: xxxx
private key: (hidden)
listening port: 51820
peer: xxxx
endpoint: 80.xxx.xxx.xxx:51820
allowed ips: 10.42.3.0/24
latest handshake: 41 seconds ago
transfer: 1.96 KiB received, 764 B sent
persistent keepalive: every 25 seconds
peer: xxxx
endpoint: 80.xxx.xxx.xxx:51820
allowed ips: 10.42.4.0/24
latest handshake: 1 minute, 27 seconds ago
transfer: 1.23 KiB received, 1.27 KiB sent
persistent keepalive: every 25 seconds
peer: xxxx
endpoint: 80.xxx.xxx.xxx:51820
allowed ips: 10.42.5.0/24
latest handshake: 1 minute, 38 seconds ago
transfer: 556.30 KiB received, 282.04 KiB sent
persistent keepalive: every 25 seconds
peer: xxxx
endpoint: 80.xxx.xxx.xxx:51820
allowed ips: 10.42.0.0/24
transfer: 0 B received, 17.63 KiB sent
persistent keepalive: every 25 seconds
What I can see from this is, is that server three has only peered with one other server instead of two!
We're missing a peer here and I assume that is related to the NAT gateway that forwards all traffic to one server (server 1).
from k3s.
I've indeed managed to fix this by assigning public IPs to all of my servers.
I have one last issue that persists though.
I can read the logs from all pods except the ones on server2 & server3
, there I receive a "502: bad gateway" error.
I'm sure this was spotted before in the wild, could you give me some pointers?
from k3s.
Related Issues (20)
- Pods not always creating logs HOT 1
- Best practice of setting the cluster name at deployment level HOT 4
- k3s crashes if I do not start the cloud-provider
- sh: 0: cannot open –: No such file
- Report the use of components with vulnerabilities in k3s HOT 1
- Update etcd to >= v3.5.13
- Improve documentation for Tailscale + K3s with an example ACL HOT 1
- Pod priority enforcement without killing lower priority pods
- netpol controller does not honor debug: true HOT 1
- Availability of StructuredAuthenticationConfiguration in 1.30.0-k3s HOT 1
- k3s 使用mysql 8.0.20 版本存储kine表,启动k3s后,mysql进程会反复重启,k3s报错连接被拒绝 HOT 1
- etcd curl: (58) unable to load client key: -8178 (SEC_ERROR_BAD_KEY) HOT 6
- Image pulls from embedded registry fail if --bind-address is set (and not 127.0.0.1) HOT 5
- missing kernel config check
- k3s-agent Fails to start with with embedded registry and kill entire OS HOT 7
- Update kube-router to v2.1.2 HOT 1
- unable to get REST mapping for extensions HOT 1
- anget node working but access fail on anget node HOT 3
- container didn't get the environment var from CONTAINERD_XXX HOT 1
- Install script `INSTALL_K3S_PR` support does not work if CI has run more than once HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from k3s.