apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:57:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-185-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-185.ec2.internal
      uid: 0547a775-f9e3-4082-a024-380ed45d2f4a
    resourceVersion: "55571"
    uid: ed44ad2b-3fc9-47e8-be46-d57abec69e0b
  spec:
    sourcePod: network-check-source-989f8b8dc-djpx9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:04:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.002829ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:32:04Z"
    - latency: 1.226616ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:31:04Z"
    - latency: 895.781µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:30:04Z"
    - latency: 867.653µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:29:04Z"
    - latency: 984.143µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:28:04Z"
    - latency: 1.150033ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:27:04Z"
    - latency: 1.370626ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:04Z"
    - latency: 948.894µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:04Z"
    - latency: 999.426µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:04Z"
    - latency: 1.138449ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:57:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-185-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-185.ec2.internal
      uid: 0547a775-f9e3-4082-a024-380ed45d2f4a
    resourceVersion: "56635"
    uid: 28721f2d-8642-4a4e-b225-977290414d4e
  spec:
    sourcePod: network-check-source-989f8b8dc-djpx9
    targetEndpoint: a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:03:04Z"
      message: 'load-balancer-api-external: tcp connection to a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.605081ms
      message: 'load-balancer-api-external: tcp connection to a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:33:04Z"
    - latency: 9.488157ms
      message: 'load-balancer-api-external: resolved host name a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:33:04Z"
    - latency: 4.767036ms
      message: 'load-balancer-api-external: tcp connection to a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:32:04Z"
    - latency: 7.555301ms
      message: 'load-balancer-api-external: resolved host name a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:32:04Z"
    - latency: 4.702833ms
      message: 'load-balancer-api-external: tcp connection to a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:31:04Z"
    - latency: 14.49562ms
      message: 'load-balancer-api-external: resolved host name a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:31:04Z"
    - latency: 4.289887ms
      message: 'load-balancer-api-external: tcp connection to a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:30:04Z"
    - latency: 7.198186ms
      message: 'load-balancer-api-external: resolved host name a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:30:04Z"
    - latency: 3.813236ms
      message: 'load-balancer-api-external: tcp connection to a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:29:04Z"
    - latency: 6.675609ms
      message: 'load-balancer-api-external: resolved host name a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:29:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:57:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-185-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-185.ec2.internal
      uid: 0547a775-f9e3-4082-a024-380ed45d2f4a
    resourceVersion: "56634"
    uid: 44da50e8-80ec-4d07-ac1d-2b2549b8a0ce
  spec:
    sourcePod: network-check-source-989f8b8dc-djpx9
    targetEndpoint: a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:03:04Z"
      message: 'load-balancer-api-internal: tcp connection to a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.577905ms
      message: 'load-balancer-api-internal: tcp connection to a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:33:04Z"
    - latency: 9.507998ms
      message: 'load-balancer-api-internal: resolved host name a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:33:04Z"
    - latency: 4.780411ms
      message: 'load-balancer-api-internal: tcp connection to a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:32:04Z"
    - latency: 7.472007ms
      message: 'load-balancer-api-internal: resolved host name a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:32:04Z"
    - latency: 3.884647ms
      message: 'load-balancer-api-internal: tcp connection to a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:31:04Z"
    - latency: 14.589307ms
      message: 'load-balancer-api-internal: resolved host name a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:31:04Z"
    - latency: 4.348107ms
      message: 'load-balancer-api-internal: tcp connection to a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:30:04Z"
    - latency: 7.085981ms
      message: 'load-balancer-api-internal: resolved host name a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:30:04Z"
    - latency: 4.145552ms
      message: 'load-balancer-api-internal: tcp connection to a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:29:04Z"
    - latency: 6.709926ms
      message: 'load-balancer-api-internal: resolved host name a1d41a3e2ad3a442ca4c47926a536cd8-8634b67572f03ce6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:29:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:57:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-185-to-network-check-target-ip-10-0-131-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-185.ec2.internal
      uid: 0547a775-f9e3-4082-a024-380ed45d2f4a
    resourceVersion: "55569"
    uid: 45772151-d3e5-4445-b02f-701e33251285
  spec:
    sourcePod: network-check-source-989f8b8dc-djpx9
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:04:04Z"
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.12456ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:32:04Z"
    - latency: 2.564345ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:31:04Z"
    - latency: 2.484485ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:30:04Z"
    - latency: 2.446378ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:29:04Z"
    - latency: 2.725149ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:28:04Z"
    - latency: 2.663366ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:27:04Z"
    - latency: 2.445655ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:04Z"
    - latency: 2.262991ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:04Z"
    - latency: 2.426963ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:04Z"
    - latency: 2.297361ms
      message: 'network-check-target-ip-10-0-131-66: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:57:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-185-to-network-check-target-ip-10-0-135-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-185.ec2.internal
      uid: 0547a775-f9e3-4082-a024-380ed45d2f4a
    resourceVersion: "55568"
    uid: edfa8c4d-161d-45e3-a8aa-c2dde56661c4
  spec:
    sourcePod: network-check-source-989f8b8dc-djpx9
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:04:04Z"
      message: 'network-check-target-ip-10-0-135-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.035835ms
      message: 'network-check-target-ip-10-0-135-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:32:04Z"
    - latency: 904.366µs
      message: 'network-check-target-ip-10-0-135-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:31:04Z"
    - latency: 1.007535ms
      message: 'network-check-target-ip-10-0-135-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:30:04Z"
    - latency: 836.697µs
      message: 'network-check-target-ip-10-0-135-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:29:04Z"
    - latency: 877.914µs
      message: 'network-check-target-ip-10-0-135-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:28:04Z"
    - latency: 1.178932ms
      message: 'network-check-target-ip-10-0-135-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:27:04Z"
    - latency: 1.45757ms
      message: 'network-check-target-ip-10-0-135-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:04Z"
    - latency: 813.082µs
      message: 'network-check-target-ip-10-0-135-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:04Z"
    - latency: 963.378µs
      message: 'network-check-target-ip-10-0-135-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:04Z"
    - latency: 1.028102ms
      message: 'network-check-target-ip-10-0-135-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:57:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-185-to-network-check-target-ip-10-0-139-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-185.ec2.internal
      uid: 0547a775-f9e3-4082-a024-380ed45d2f4a
    resourceVersion: "55570"
    uid: 2e383d44-2be4-4a4d-a820-2245e776ca1d
  spec:
    sourcePod: network-check-source-989f8b8dc-djpx9
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:04:04Z"
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.52276ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:32:04Z"
    - latency: 2.265698ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:31:04Z"
    - latency: 2.39758ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:30:04Z"
    - latency: 2.45829ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:29:04Z"
    - latency: 2.33776ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:28:04Z"
    - latency: 2.423856ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:27:04Z"
    - latency: 3.125597ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:04Z"
    - latency: 2.351055ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:04Z"
    - latency: 2.393892ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:04Z"
    - latency: 2.111044ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:57:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-185-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-185.ec2.internal
      uid: 0547a775-f9e3-4082-a024-380ed45d2f4a
    resourceVersion: "56633"
    uid: 539f5ca4-9976-43eb-8f9b-731a34c0e347
  spec:
    sourcePod: network-check-source-989f8b8dc-djpx9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:03:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.107858ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:33:04Z"
    - latency: 2.06224ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:33:04Z"
    - latency: 861.149µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:32:04Z"
    - latency: 1.869624ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:32:04Z"
    - latency: 881.323µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:31:04Z"
    - latency: 1.745127ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:31:04Z"
    - latency: 866.365µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:30:04Z"
    - latency: 1.782967ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:30:04Z"
    - latency: 986.778µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:29:04Z"
    - latency: 1.759895ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:29:04Z"
kind: List
metadata:
  resourceVersion: ""