Replies: 2 comments 4 replies
-
|
Beta Was this translation helpful? Give feedback.
4 replies
-
There must be some mistake in my process. I reworked all things and now it works. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I need to run K3S with ZFS backend, hence I followed the doc here. Everything worked except that the ports exposed by service type load balancer were not connectable. The svclb pods were running.
I thought it might be related to OS and ZFS, so I started an Archlinux VM in VirtualBox. For Containerd, I changed nothing but
And installed K3S via
curl -L https://get.k3s.io | CONTAINERD_HTTPS_PROXY=http://internal-proxy/ K3S_KUBECONFIG_MODE="644" INSTALL_K3S_EXEC="--container-runtime-endpoint unix:///run/containerd/containerd.sock" sh -
. (I know the PROXY env would not work here, just keep things as I did.)Same thing happened. The services are inaccessible. I do not have firewall or similar things running.
I posted the Iptables rules below. And tools info here:
kubectl version
Client Version: v1.30.6+k3s1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.6+k3s1
containerd version
Server:
containerd:
Version: v2.0.0
runc:
Version: 1.2.2
I tried to directly running something with
nerdctl
, the port mapping worked. And the same Kubernetes manifests worked in another host running K3S with built-in containerd.Beta Was this translation helpful? Give feedback.
All reactions