https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
w
I used
Copy code
metadata:
  annotations:
    <http://traefik.ingress.kubernetes.io/service.serversscheme|traefik.ingress.kubernetes.io/service.serversscheme>: https
a
Copy code
Thank you! for the reply, 

Do you mean I should use '<http://traefik.ingress.kubernetes.io/service.serversscheme|traefik.ingress.kubernetes.io/service.serversscheme>: https' rather '<http://traefik.ingress.kubernetes.io/ssl.passthrough|traefik.ingress.kubernetes.io/ssl.passthrough>: "True"' for SSL-PASSTHROUGH?

Though I have tired your options, but it is still not working, could you please reconfirm it.
w
most important thing to do is enable logging on Traefik then watch it to see what's happening
there are so many variables between setups
a
Okay, let me try to enable the logging and see it, meantime I found an Traefik blog where they are talking about how to configure the Pass-through(IngressRouteTCP) in Kubernetes, but the configure is different in K3S. https://doc.traefik.io/traefik/v2.1/routing/providers/kubernetes-crd/#kind-ingressroutetcp
w
oooh, you want full pass thru! yeah, that's different to what I'm using. AIUI you'll need to use a Traefik IngressRoute, rather than an Ingress
a
I'm glad you understood what I meant. I have noticed CRD (ingressroutetcps.traefik.containo.us), is already enabled and IngressRoute is a possible configuration, however do you have any sample settings which can be configured in K3S?
w
their example is for TLS termination but there's a note on the pass thru option that sounds like what you want
a
I tried that option also, but no luck 😞 .
71 Views
Open in Slack
PreviousNext
Powered by