apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:29:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-104-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-104.us-west-2.compute.internal
      uid: 25777abc-66e9-47bd-980d-fbed3b1b0481
    resourceVersion: "26141"
    uid: a7bba413-8559-48bf-9613-2cc39a2a85d8
  spec:
    sourcePod: network-check-source-6f78d59f99-vgldm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:37:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 997.796µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:43:52Z"
    - latency: 853.134µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:42:52Z"
    - latency: 876.659µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:41:52Z"
    - latency: 1.118743ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:40:52Z"
    - latency: 1.073926ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:39:52Z"
    - latency: 861.977µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:38:52Z"
    - latency: 1.059818ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:37:52Z"
    - latency: 1.144278ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:36:52Z"
    - latency: 1.019999ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:35:52Z"
    - latency: 1.254885ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:34:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:29:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-104-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-104.us-west-2.compute.internal
      uid: 25777abc-66e9-47bd-980d-fbed3b1b0481
    resourceVersion: "25044"
    uid: 2c46bc53-35a2-41d1-9856-3f81407cd14c
  spec:
    sourcePod: network-check-source-6f78d59f99-vgldm
    targetEndpoint: a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:35:52Z"
      message: 'load-balancer-api-external: tcp connection to a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 51.987081ms
      message: 'load-balancer-api-external: tcp connection to a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:41:52Z"
    - latency: 6.990091ms
      message: 'load-balancer-api-external: resolved host name a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:41:52Z"
    - latency: 49.236923ms
      message: 'load-balancer-api-external: tcp connection to a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:40:52Z"
    - latency: 7.181587ms
      message: 'load-balancer-api-external: resolved host name a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:40:52Z"
    - latency: 50.243013ms
      message: 'load-balancer-api-external: tcp connection to a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:39:52Z"
    - latency: 7.999362ms
      message: 'load-balancer-api-external: resolved host name a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:39:52Z"
    - latency: 51.923995ms
      message: 'load-balancer-api-external: tcp connection to a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:38:52Z"
    - latency: 8.219141ms
      message: 'load-balancer-api-external: resolved host name a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:38:52Z"
    - latency: 50.512921ms
      message: 'load-balancer-api-external: tcp connection to a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:37:52Z"
    - latency: 7.71298ms
      message: 'load-balancer-api-external: resolved host name a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:37:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:29:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-104-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-104.us-west-2.compute.internal
      uid: 25777abc-66e9-47bd-980d-fbed3b1b0481
    resourceVersion: "25046"
    uid: a893b23b-b0c4-40a0-887b-e8c94c18a856
  spec:
    sourcePod: network-check-source-6f78d59f99-vgldm
    targetEndpoint: a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:35:52Z"
      message: 'load-balancer-api-internal: tcp connection to a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.217804ms
      message: 'load-balancer-api-internal: tcp connection to a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:41:52Z"
    - latency: 7.045148ms
      message: 'load-balancer-api-internal: resolved host name a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:41:52Z"
    - latency: 52.618266ms
      message: 'load-balancer-api-internal: tcp connection to a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:40:52Z"
    - latency: 7.202549ms
      message: 'load-balancer-api-internal: resolved host name a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:40:52Z"
    - latency: 54.829474ms
      message: 'load-balancer-api-internal: tcp connection to a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:39:52Z"
    - latency: 8.05107ms
      message: 'load-balancer-api-internal: resolved host name a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:39:52Z"
    - latency: 51.942722ms
      message: 'load-balancer-api-internal: tcp connection to a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:38:52Z"
    - latency: 8.179993ms
      message: 'load-balancer-api-internal: resolved host name a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:38:52Z"
    - latency: 50.515268ms
      message: 'load-balancer-api-internal: tcp connection to a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:37:52Z"
    - latency: 7.743086ms
      message: 'load-balancer-api-internal: resolved host name a0b690d1e7ab24dd09bdd443920af197-9bacf9f94db242c4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:37:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:29:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-104-to-network-check-target-ip-10-0-136-243
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-104.us-west-2.compute.internal
      uid: 25777abc-66e9-47bd-980d-fbed3b1b0481
    resourceVersion: "26138"
    uid: 5e5c52f4-89c6-42df-a754-164eb8a84eff
  spec:
    sourcePod: network-check-source-6f78d59f99-vgldm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:36:52Z"
      message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.806175ms
      message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:43:52Z"
    - latency: 1.876487ms
      message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:42:52Z"
    - latency: 1.657754ms
      message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:41:52Z"
    - latency: 1.943872ms
      message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:40:52Z"
    - latency: 2.046343ms
      message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:39:52Z"
    - latency: 1.532559ms
      message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:38:52Z"
    - latency: 14.791799ms
      message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:37:52Z"
    - latency: 1.961803ms
      message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:36:52Z"
    - latency: 1.935974ms
      message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:35:52Z"
    - latency: 1.987006ms
      message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:34:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:29:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-104-to-network-check-target-ip-10-0-140-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-104.us-west-2.compute.internal
      uid: 25777abc-66e9-47bd-980d-fbed3b1b0481
    resourceVersion: "26137"
    uid: 6463399a-1de6-41c2-aabf-3f1490cd1c3b
  spec:
    sourcePod: network-check-source-6f78d59f99-vgldm
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:36:52Z"
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.229271ms
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:43:52Z"
    - latency: 2.079887ms
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:42:52Z"
    - latency: 2.040769ms
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:41:52Z"
    - latency: 2.590178ms
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:40:52Z"
    - latency: 1.983966ms
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:39:52Z"
    - latency: 2.078146ms
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:38:52Z"
    - latency: 3.190221ms
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:37:52Z"
    - latency: 2.039065ms
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:36:52Z"
    - latency: 2.108868ms
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:35:52Z"
    - latency: 2.303173ms
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:34:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:38:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-104-to-network-check-target-ip-10-0-141-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-104.us-west-2.compute.internal
      uid: 25777abc-66e9-47bd-980d-fbed3b1b0481
    resourceVersion: "27138"
    uid: 19734fcc-fc93-4e94-9847-86fbd40d9c06
  spec:
    sourcePod: network-check-source-6f78d59f99-vgldm
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:45:41Z"
      message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.137118ms
      message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:45:41Z"
    - latency: 936.069µs
      message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:44:41Z"
    - latency: 989.797µs
      message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:43:41Z"
    - latency: 1.047377ms
      message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:42:41Z"
    - latency: 917.95µs
      message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:41:41Z"
    - latency: 1.11031ms
      message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:40:41Z"
    - latency: 1.188891ms
      message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:39:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:29:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-104-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-104.us-west-2.compute.internal
      uid: 25777abc-66e9-47bd-980d-fbed3b1b0481
    resourceVersion: "25045"
    uid: 4a45cfa3-b87d-42af-a24c-027da3b50c1d
  spec:
    sourcePod: network-check-source-6f78d59f99-vgldm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:35:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 955.194µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:41:52Z"
    - latency: 611.011µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:41:52Z"
    - latency: 1.361785ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:40:52Z"
    - latency: 599.955µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:40:52Z"
    - latency: 956.023µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:39:52Z"
    - latency: 784.398µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:39:52Z"
    - latency: 1.166891ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:38:52Z"
    - latency: 601.059µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:38:52Z"
    - latency: 899.935µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T18:37:52Z"
    - latency: 765.835µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T18:37:52Z"
kind: List
metadata:
  resourceVersion: ""