Closed travisghansen closed 1 month ago
Also note, it appears traefik
is messing with the gateway
itself as well:
# kubectl -n istio-system get gateway eastwestgateway -o yaml
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
annotations:
gateway.istio.io/controller-version: "5"
creationTimestamp: "2024-09-20T15:48:22Z"
generation: 1
labels:
app: raw
argocd.argoproj.io/instance: dev-na01-workload-00-istio-system
chart: raw-0.2.5
heritage: Helm
release: istio-system-common
topology.istio.io/network: dev-na01-workload-00
name: eastwestgateway
namespace: istio-system
resourceVersion: "1630359689"
uid: 159e342d-7bdf-459f-b0e6-684975fc591b
spec:
gatewayClassName: istio
listeners:
- allowedRoutes:
namespaces:
from: Same
name: istiod-grpc
port: 15012
protocol: TLS
tls:
mode: Passthrough
- allowedRoutes:
namespaces:
from: Same
name: istiod-webhook
port: 15017
protocol: TLS
tls:
mode: Passthrough
- allowedRoutes:
namespaces:
from: Same
hostname: '*.local'
name: tls-passthrough
port: 15443
protocol: TLS
tls:
mode: Passthrough
status:
addresses:
- type: IPAddress
value: 172.28.42.32
conditions:
- lastTransitionTime: "2024-09-20T16:32:55Z"
message: Gateway successfully scheduled
observedGeneration: 1
reason: Accepted
status: "True"
type: Accepted
- lastTransitionTime: "2024-09-20T16:32:55Z"
message: Gateway successfully scheduled
observedGeneration: 1
reason: Programmed
status: "True"
type: Programmed
Notice the 2 conditions (presumably 1 from traefik and 1 from istio) but the key here is the IPAddress
getting set is the traefik
svc IP.
addresses:
- type: IPAddress
value: 172.28.42.32
kubectl -n adc-system get svc | grep 'traefik'
traefik-internal LoadBalancer 100.127.150.81 172.28.42.32 80:31355/TCP,3661:31245/TCP,443:30371/TCP,443:30997/UDP 426d
That also shouldn't be happening as well correct? Thankfully it appears istio is setting an address somewhere else as well...
kubectl -n istio-system get gateway eastwestgateway NAME CLASS ADDRESS PROGRAMMED AGE
eastwestgateway istio 172.28.42.77 True 51m
kubectl -n istio-system get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
eastwestgateway-istio LoadBalancer 100.127.197.10 172.28.42.77 15021:30241/TCP,15012:31728/TCP,15017:30610/TCP,15443:31255/TCP 51m
Yeah, traefik
is fighting istio
and the IP is constantly switching around for gateways with the class set to istio
. Conversely, I have dedicated gateway classes for traefik
which are being left alone by istio
.
Hello @travisghansen,
Thanks for reporting this!
We have confirmed the bug and have opened #11170 which should fix this issue.
Great! Let me know when it hits a release and I will test it out!
Hello @travisghansen,
The PR is merged, you can test the fix with the experimental-v3.2 image until the new v3.2.0-rc2 is released.
I'm closing this issue accordingly.
Welcome!
What did you do?
Consider the following set of assets:
When applied it appears traefik is attempting to handle the tlsroutes even though the parent gateways does not include a traefik-managed gateway.
What did you see instead?
Should I expect
traefik
to touch these assets at all given they are not associated with a traefik-managed gateway?What version of Traefik are you using?
3.1.3
What is your environment & configuration?
Add more configuration information here.
If applicable, please paste the log output in DEBUG level
No response