important-art-22288
08/05/2022, 4:59 PMx-forwarded-for
headers through the CNI — all requests were showing up internally with the internal IP of the CNI in the header. It looks like there are some complicated workarounds with Flannel there but I ditched that route given the complexity.
Is there any good way to do this, or am I thinking about it wrong? All I need to do is to have some ingresses only exposed to the local network, and others exposed to the public internet, if possible. The current Pi networking config just forwards 443 and 80 through the router configuration, but if there’s a better way to do that I’m open to itcreamy-pencil-82913
08/05/2022, 5:25 PM<http://traefik.ingress.kubernetes.io/router.entrypoints|traefik.ingress.kubernetes.io/router.entrypoints>
annotation to which entrypoints I want that ingress resource to be exposed on.important-art-22288
08/05/2022, 5:53 PM<http://traefik.ingress.kubernetes.io/router.entrypoints|traefik.ingress.kubernetes.io/router.entrypoints>: internalweb, internalwebsecure
? My traefik logs are saying entryPoint \"internalwebsecure\" doesn't exist
when I go to apply it despite it existing in the helmchartconfigcreamy-pencil-82913
08/05/2022, 7:09 PMimportant-art-22288
08/07/2022, 1:19 AM