This message was deleted.
# rancher-desktopa
adamant-kite-43734
09/25/2024, 4:06 PMThis message was deleted.
h
helpful-butcher-75556
09/25/2024, 4:59 PMIt should be accessible from other pods via the K8s Service's name. (Not the Ingress).
w
wonderful-nightfall-4738
09/25/2024, 5:28 PMI know it should,... it is not! So I'm puzzled!
wonderful-nightfall-4738
09/25/2024, 5:34 PMAnd this works and I can access the port:
Copy code
kubectl port-forward service/my-service 8083:8083 Copy code
# wget <http://my-service:8083>
Connecting to service:8083 (10.42.0.45:8083)
wget: can't connect to remote host (10.42.0.45): Connection refusedh
helpful-butcher-75556
09/25/2024, 5:39 PMI was going to suggest busybox & wget. It's resolving the name, but can't connect to the port, as if it's not listening on 8083, but you forward it and it works. 🤷
w
wonderful-nightfall-4738
09/25/2024, 5:57 PMI now... Drives me nuts!
wonderful-nightfall-4738
09/25/2024, 6:11 PMAlmost like it's missing kube-proxy
h
helpful-butcher-75556
09/26/2024, 11:28 AMDid you figure it out?
w
wonderful-nightfall-4738
10/01/2024, 6:45 PMNo
wonderful-nightfall-4738
10/01/2024, 6:45 PMStill an issue for me
wonderful-nightfall-4738
10/01/2024, 7:55 PMFound my issue! I'm using an operator, and the thing creates a Network policy I didn't notice!
h
helpful-butcher-75556
10/02/2024, 10:40 AMGlad you found it!
6 Views