You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 98975fb
Browse filesBrowse the repository at this point in the historyBrowse files
Resolve Istio hosts only within the observed service domain (#2086)
Istio destination.host is not always a Kubernetes Service. Treating any
dotted host as a local service can connect an external address or an
incomplete DNS name to an unrelated cluster object.
The graph and renderers share the same rule: a short name resolves in
the resource's namespace; a fully qualified name resolves only under the
service domain observed from istiod. External, wildcard, incomplete and
conflicting-domain hosts remain unresolved. Resource and traffic modes
use the same host resolution.
API change: Relationships adds optional string istioServiceDomain, also
carried in Istio node metadata. This supplies standalone resource
drawers with the observation used by topology; it is present only when a
domain is known. An Istio relationships response may therefore be
non-null even when it contains no resource edges. Conflicting or invalid
explicit observations do not authorize FQDN navigation. When no istiod
Deployment is observed (including an external or unobserved control
plane), the existing `cluster.local` default applies; custom domains
require the control plane to be in Radar's cache.
Review focus: domain observation and consistent graph/drawer
interpretation. This is reference resolution, not proof of reachability
or mesh routing configuration.
Validation: full root and relevant shared-module Go suites;
resource/traffic host and observed/conflicting-domain tests; four
rendered host navigation cases; web/shared UI type checks; production
frontend/embed/backend build. Existing renderers and link presentation
are retained.
Visual-test: skipped because these corrections retain the existing
layouts; rendered navigation/evidence tests and real REST/MCP checks
cover the changed behavior.
Copy file name to clipboardExpand all lines: docs/integrations.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -692,6 +692,8 @@ See the main [README](../README.md#gitops) for the user-facing overview. This se
692
692
693
693
**Topology:** Full Istio traffic path — IstioGateway → VirtualService → Service, and DestinationRule → Service configuration edges. See how traffic flows through gateway listeners, virtual service routing rules, and into backend services.
694
694
695
+
Service links accept short names in the rule's namespace or full `name.namespace.svc.<domain>` names. Radar reads a unique registry domain from standard observed Istiod Deployments' `--domain` argument, using Istio's `cluster.local` default when no override is observed. Conflicting or unresolved control-plane arguments leave FQDN links unresolved. External control planes and nonstandard launch configurations may therefore need additional domain discovery; arbitrary dotted hosts are not treated as local Services.
696
+
695
697
**VirtualService Detail View:**
696
698
- HTTP/TCP/TLS routing rules with match conditions
0 commit comments