This message was deleted.

Check out this ingress example below, full article here: https://itnext.io/simplest-minimal-k8s-app-tutorial-with-rancher-desktop-in-5-min-5481edb9a4a5

apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>
kind: Ingress
metadata:
  name: jade-shooter
spec:
  rules:
  - host: jade-shooter.rancher.localhost
    http:
      paths:
      - pathType: Prefix
        path: /
        backend:
          service:
            name: jade-shooter-service
            port:
              number: 8080
  tls:
  - hosts:
    - jade-shooter.rancher.localhost

That doesn't work out-of-the-box. For example, If I deploy Grafana with the ingress host set to

grafana.rancher.locahost

, The OS can't resolve the hostname:

curl <http://grafana.rancher.localhost>
curl: (6) Could not resolve host: grafana.rancher.localhost

Ugh I left that step out to add an entry in etc hosts where rancher.localhost maps to 127.0.0.1

Yes, I figured that out. I also found that you can get a wildcard mapping if you use

dnsmasq

. I haven't tried that yet.

I tested it again, and it works with a Chrome or Firefox-based browser. I've updated the docs