damp-dusk-21502
04/28/2023, 3:58 PMBad Gateway
. And I am out of ideas.
I have a fresh installation of rancher-desktop and I can see traefik
running in the kube-system
namespace.
I have applied an http demo deployment (comes from ingress-nginx, but the deployment should be agnostic) and the ingress file below:
kubectl apply -f <https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/docs/examples/http-svc.yaml>
---
apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>
kind: Ingress
metadata:
name: demo-ingress
spec:
rules:
- http:
paths:
- pathType: Prefix
path: "/"
backend:
service:
name: http-svc
port:
number: 80
---
I end up with this ingress:
kubectl get <http://ingresses.networking.k8s.io|ingresses.networking.k8s.io>
NAME CLASS HOSTS ADDRESS PORTS AGE
demo-ingress traefik * 192.168.130.178 80 24m
However, all requests to localhost or 192.168.130.178 return bad gateway:
# same with <http://192.168.130.178>
curl <http://127.0.0.1:80>
Bad Gateway
annotation
, which apparently is now superseded spec.ingressClassName
kubectl exec -it http-svc-6b9f69759b-8hkpr -- /bin/sh
I can't even wget 127.0.0.1:8080
, which supposedly is the port on which the server inside the container is listeningsparse-fireman-14239
04/29/2023, 7:47 AM