Replies: 1 comment
-
Little update, the typical "kubectl port-forward" worked. But I would like to handle this with a LoadBalancer or a NodePort. k3d uses traefik out of the box right? I would like to use this one, but there I get the External-IP: pending problem, right now. Update: I was able to get rid of the problem, now I only have to access my application, but I get no logs from traefic... Only that everything looks fine. But I still cannot ping from WSL/ Windows to the nodes. |
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
-
Hello guys,
I'm new to k3d, so I appreciate your help. I found some similar topics, but not exatly what I was looking for.
I'm using Docker Desktop with WSL (Ubuntu) and inside Ubuntu I created a cluster with the following command:
k3d cluster create three-node-cluster --agents 3 --registry-config "./registries.yaml"
The registries.yaml configures a local Docker registry. (That works 👍 )
Now i have deployed a web application as a service that runs on port 3000 and I would like to access it via the browser.
("WSL-IP:31002")
I tried exposing the port via NodePort, but am I missing some configurations to make it work?
This is my service.yaml:
apiVersion: v1 kind: Service metadata: annotations: kompose.cmd: kompose convert -f docker-compose.yml kompose.version: 1.32.0 (765fde254) labels: io.kompose.service: webtop1 name: webtop1 spec: type: NodePort ports: - name: http port: 3000 targetPort: 3000 nodePort: 31002 selector: io.kompose.service: webtop1
I found out that my WSL cannot ping the k3d cluster nodes, but the nodes can ping WSL.
I checked for firewall settings inside the nodes and I did not find any problems. Does anyone have an idea or is my approach wrong?
Thanks for the help,
Wosch
Beta Was this translation helpful? Give feedback.
All reactions