You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I see, the keys present in the POD are different from those specified in the yaml file. kubectl get logs reports
wgrs-wireguard-xqvv9 sysctls net.ipv4.ip_forward = 1
wgrs-wireguard-xqvv9 sysctls net.ipv4.conf.all.forwarding = 1
wgrs-wireguard-xqvv9 wireguard [#] ip link add wg0 type wireguard
wgrs-wireguard-xqvv9 wireguard [#] wg setconf wg0 /dev/fd/63
wgrs-wireguard-xqvv9 wireguard [#] ip -4 address add 172.32.32.1/24 dev wg0
wgrs-wireguard-xqvv9 wireguard [#] ip link set mtu 1290 up dev wg0
wgrs-wireguard-xqvv9 wireguard [#] wg set wg0 private-key /etc/wireguard/privatekey && iptables -t nat -A POSTROUTING -s 172.32.32.0/24 -o eth0 -j MASQUERADE
wgrs-wireguard-xqvv9 wireguard Public key 'dRH4Ms/h+H3BmT/J.....'
Another things I note, is that the pod is very hard to debug, I can't get to any shell and kubectl exec gives errors in reading /etc/wireguard
What kubernetes version and kubernetes distribution are you using? Does your cluster have something applying role bindings impacting kubectl exec permissions? Or are you using a different wireguard container image?
The default image is alpine based and has a shell included so there shouldn't be anything from the image or chart preventing shell access through kubectl.
Hello,
I'm having issue with this chart.
From what I see, the keys present in the POD are different from those specified in the yaml file.
kubectl get logs
reportsBut in the yaml file, I specified:
wg show wg0
showsAnother things I note, is that the pod is very hard to debug, I can't get to any shell and
kubectl exec
gives errors in reading/etc/wireguard
The project seems promising but more focus should be put into documentation (also a way to debug)
--
Roberto
The text was updated successfully, but these errors were encountered: