apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:17:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-41-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-41.ec2.internal
      uid: f509e200-b506-42b4-a907-3b919ab11d17
    resourceVersion: "53926"
    uid: 45f0cc53-ba74-4dae-b986-d8a76b0c1a89
  spec:
    sourcePod: network-check-source-685456655f-k4f7g
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:24:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 841.932µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:45:08Z"
    - latency: 1.143185ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:44:08Z"
    - latency: 907.383µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:43:08Z"
    - latency: 1.512181ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:42:08Z"
    - latency: 1.120973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:41:08Z"
    - latency: 1.403293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:40:08Z"
    - latency: 2.021181ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:39:08Z"
    - latency: 1.361313ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:38:08Z"
    - latency: 1.101271ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:37:08Z"
    - latency: 1.018276ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:36:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:17:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-41-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-41.ec2.internal
      uid: f509e200-b506-42b4-a907-3b919ab11d17
    resourceVersion: "55572"
    uid: f6c9feef-a05e-4ea9-be95-4447442df34b
  spec:
    sourcePod: network-check-source-685456655f-k4f7g
    targetEndpoint: a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:23:08Z"
      message: 'load-balancer-api-external: tcp connection to a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.930118ms
      message: 'load-balancer-api-external: tcp connection to a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:47:08Z"
    - latency: 7.25135ms
      message: 'load-balancer-api-external: resolved host name a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:47:08Z"
    - latency: 2.874404ms
      message: 'load-balancer-api-external: tcp connection to a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:46:08Z"
    - latency: 6.304623ms
      message: 'load-balancer-api-external: resolved host name a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:46:08Z"
    - latency: 3.72737ms
      message: 'load-balancer-api-external: tcp connection to a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:45:08Z"
    - latency: 7.053455ms
      message: 'load-balancer-api-external: resolved host name a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:45:08Z"
    - latency: 5.999023ms
      message: 'load-balancer-api-external: tcp connection to a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:44:08Z"
    - latency: 6.078388ms
      message: 'load-balancer-api-external: resolved host name a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:44:08Z"
    - latency: 5.186673ms
      message: 'load-balancer-api-external: tcp connection to a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:43:08Z"
    - latency: 6.952719ms
      message: 'load-balancer-api-external: resolved host name a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:43:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:17:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-41-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-41.ec2.internal
      uid: f509e200-b506-42b4-a907-3b919ab11d17
    resourceVersion: "55571"
    uid: 5db6110d-4b55-404a-b3e3-662f78e455d3
  spec:
    sourcePod: network-check-source-685456655f-k4f7g
    targetEndpoint: a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:23:08Z"
      message: 'load-balancer-api-internal: tcp connection to a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.08876ms
      message: 'load-balancer-api-internal: tcp connection to a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:47:08Z"
    - latency: 7.222733ms
      message: 'load-balancer-api-internal: resolved host name a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:47:08Z"
    - latency: 3.369143ms
      message: 'load-balancer-api-internal: tcp connection to a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:46:08Z"
    - latency: 6.276858ms
      message: 'load-balancer-api-internal: resolved host name a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:46:08Z"
    - latency: 3.740958ms
      message: 'load-balancer-api-internal: tcp connection to a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:45:08Z"
    - latency: 6.998071ms
      message: 'load-balancer-api-internal: resolved host name a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:45:08Z"
    - latency: 5.951646ms
      message: 'load-balancer-api-internal: tcp connection to a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:44:08Z"
    - latency: 6.011922ms
      message: 'load-balancer-api-internal: resolved host name a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:44:08Z"
    - latency: 5.244915ms
      message: 'load-balancer-api-internal: tcp connection to a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:43:08Z"
    - latency: 6.937476ms
      message: 'load-balancer-api-internal: resolved host name a962bf6c176f24b378d6466d245c09de-27ca98881f60b2bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:43:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:17:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-41-to-network-check-target-ip-10-0-128-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-41.ec2.internal
      uid: f509e200-b506-42b4-a907-3b919ab11d17
    resourceVersion: "53923"
    uid: 38a6cdc2-f93d-4c44-addd-ca86b259237e
  spec:
    sourcePod: network-check-source-685456655f-k4f7g
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:24:08Z"
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 960.649µs
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:45:08Z"
    - latency: 979.361µs
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:44:08Z"
    - latency: 981.654µs
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:43:08Z"
    - latency: 1.279121ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:42:08Z"
    - latency: 1.043578ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:41:08Z"
    - latency: 837.269µs
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:40:08Z"
    - latency: 884.993µs
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:39:08Z"
    - latency: 906.349µs
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:38:08Z"
    - latency: 1.063102ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:37:08Z"
    - latency: 1.067107ms
      message: 'network-check-target-ip-10-0-128-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:36:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:17:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-41-to-network-check-target-ip-10-0-131-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-41.ec2.internal
      uid: f509e200-b506-42b4-a907-3b919ab11d17
    resourceVersion: "53925"
    uid: 528f1c42-8142-41da-9af0-493635f468d1
  spec:
    sourcePod: network-check-source-685456655f-k4f7g
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:24:08Z"
      message: 'network-check-target-ip-10-0-131-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.422499ms
      message: 'network-check-target-ip-10-0-131-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:45:08Z"
    - latency: 2.428188ms
      message: 'network-check-target-ip-10-0-131-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:44:08Z"
    - latency: 2.745544ms
      message: 'network-check-target-ip-10-0-131-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:43:08Z"
    - latency: 2.468871ms
      message: 'network-check-target-ip-10-0-131-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:42:08Z"
    - latency: 2.342695ms
      message: 'network-check-target-ip-10-0-131-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:41:08Z"
    - latency: 2.454499ms
      message: 'network-check-target-ip-10-0-131-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:40:08Z"
    - latency: 2.934718ms
      message: 'network-check-target-ip-10-0-131-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:39:08Z"
    - latency: 2.917402ms
      message: 'network-check-target-ip-10-0-131-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:38:08Z"
    - latency: 2.314372ms
      message: 'network-check-target-ip-10-0-131-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:37:08Z"
    - latency: 2.639424ms
      message: 'network-check-target-ip-10-0-131-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:36:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:17:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-41-to-network-check-target-ip-10-0-137-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-41.ec2.internal
      uid: f509e200-b506-42b4-a907-3b919ab11d17
    resourceVersion: "53924"
    uid: 4cf614eb-7614-4e55-a7ed-f1e1065efeae
  spec:
    sourcePod: network-check-source-685456655f-k4f7g
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:24:08Z"
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.063721ms
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:45:08Z"
    - latency: 2.704435ms
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:44:08Z"
    - latency: 2.440424ms
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:43:08Z"
    - latency: 2.811071ms
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:42:08Z"
    - latency: 2.255533ms
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:41:08Z"
    - latency: 2.73266ms
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:40:08Z"
    - latency: 2.376274ms
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:39:08Z"
    - latency: 2.492835ms
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:38:08Z"
    - latency: 2.239754ms
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:37:08Z"
    - latency: 2.168799ms
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:36:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:17:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-41-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-41.ec2.internal
      uid: f509e200-b506-42b4-a907-3b919ab11d17
    resourceVersion: "55570"
    uid: f5cd0a02-c3fb-4200-a174-442126284259
  spec:
    sourcePod: network-check-source-685456655f-k4f7g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:23:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.19013ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:47:08Z"
    - latency: 1.857121ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:47:08Z"
    - latency: 911.458µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:46:08Z"
    - latency: 1.733274ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:46:08Z"
    - latency: 979.801µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:45:08Z"
    - latency: 1.970476ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:45:08Z"
    - latency: 903.18µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:44:08Z"
    - latency: 1.649911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:44:08Z"
    - latency: 937.404µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:43:08Z"
    - latency: 1.776776ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:43:08Z"
kind: List
metadata:
  resourceVersion: ""