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
I was able to deploy this on a K3S cluster and it runs as expected so far. However I cant get around how to apply my clients public key in the server configuration. I did try to use the publicKey item under spec, but that does not seem to change anything except borking the private key. is there any way to pin the public key to the peer? Below is what I had tried.
kind: WireguardPeermetadata:
name: testnamespace: "wireguardvpn"spec:
wireguardRef: "wgserver"publicKey: "cBaucnK3ufdDm4/UGP/+d4WETwj1+E/xsVIAsiLyVzc="``kubectl get wireguardpeer test --template={{.status.config}} -n wireguardvpn | bash ``Error from server (NotFound): secrets "test-peer" not found [Interface]PrivateKey = Address = 10.8.0.3DNS = 10.43.0.10, wireguardvpn.svc.cluster.localMTU = 1380[Peer]PublicKey = qn+nbV9R3onKixAoXKcwLlPz+f/vW3O5nOZpVB3SjSQ=AllowedIPs = 0.0.0.0/0Endpoint = 192.168.3.237:51820 >
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I was able to deploy this on a K3S cluster and it runs as expected so far. However I cant get around how to apply my clients public key in the server configuration. I did try to use the publicKey item under spec, but that does not seem to change anything except borking the private key. is there any way to pin the public key to the peer? Below is what I had tried.
Beta Was this translation helpful? Give feedback.
All reactions