A Gateway API route binds to the correct listener, but the backendRef points...

시나리오

Everything looks connected until …

단서

구독하면 이어서 볼 수 있어요

이 문제의 전체 시나리오와 점검 체크리스트, 복구 순서, 모범 풀이는 Pro 구독에서 열립니다.

구독 안내 보기

먼저 볼 것

점검 체크리스트

복구와 재발 방지

같이 보면 좋은 질문

현장에서 본 비슷한 케이스

다음으로 이어서 보기 좋은 문제

K8s Advanced

A route binds to the right listener while a cross-namespace backend reference is still unauthorized during a failover rehearsal

The object graph looks connected and the security boundary still prevents end-to-end flow. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.

19 min

View problem

K8s Intermediate

Gateway API route is accepted but the ReferenceGrant does not cover the namespace of the backend service

The route object itself looks valid, yet traffic never forwards because the cross-namespace backend reference is not explicitly granted.

18 min

View problem

K8s Intermediate

Ingress class mismatch sends traffic to the wrong controller

Ingress class mismatch sends traffic to the wrong controller is a hands-on troubleshooting drill. Routing rules are valid, but the ingress object is reconciled by a different controller than the team expected. Kubernetes Ingress and Traffic needs to be checked by narrowing sco...

19 min

View problem

K8s Intermediate

A gateway API route is admitted while one backend reference still points to a namespace alias only the old ingress controller understood during a staged decommission

The route object looks valid and one controller-specific assumption no longer applies. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.

16 min

View problem

A Gateway API route binds to the correct listener, but the backendRef points at a Service in another namespace without the required ReferenceGrant

A route binds to the right listener while a cross-namespace backend reference is still unauthorized during a failover rehearsal

Gateway API route is accepted but the ReferenceGrant does not cover the namespace of the backend service

Ingress class mismatch sends traffic to the wrong controller

A gateway API route is admitted while one backend reference still points to a namespace alias only the old ingress controller understood during a staged decommission