jawabuu
jawabuu
Hey @osterman Great to hear from you. I don't believe I modified the README created generated by README.yaml. Kindly clarify.
@Mantany Kindly reopen. Can consistently reproduce Also see https://doc.traefik.io/traefik/routing/providers/kubernetes-ingress/#communication-between-traefik-and-pods Traefik will always assume communication to ghost pod to be TLS because the port on the service is named 'https' This...
@jotcodeofficial @rafariossaa Here's a POC chart you can use with traefik ``` helm repo add ghost-helm https://jawabuu.github.io/ghost-helm/ helm install ghost-helm/ghost --version 19.0.9 ```
My suggestions, 1. The ingress template should include this annotation by default ` ingress.kubernetes.io/ssl-proxy-headers: 'X-Forwarded-Proto: https'` 2. The service template should consider changing the port name from **https** to **tls**...
Hey @danderson @johananl just got bitten by this too when using k3s. Two questions; 1. Given the current behaviour how would one force updtae the LoadBalancer IP? 2. A common...
Hey @johananl Thank you for the workaround.
On point 2, I am spinning up a K3S Highly available cluster with 3 master nodes. I am adding the external IPs of the three master nodes to my metalLB...
Hey @russellb I do understand this. This is merely a workaround to `fake` a LoadBalancer on k3s or other setups where one cannot or does not wish to acquire a...
@champtar Thanks
@dbader, @DahlitzFlorian. Take a look.