apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:03:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-90-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-90.us-east-2.compute.internal
      uid: 2bd51030-7e31-4f5e-b8ca-8f377ea816aa
    resourceVersion: "162364"
    uid: d10955f2-f42c-4354-9659-6225a1d60420
  spec:
    sourcePod: network-check-source-6f78d59f99-fvdt8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:10:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.802035ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:52:23Z"
    - latency: 1.053681ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:51:23Z"
    - latency: 1.642019ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:50:23Z"
    - latency: 961.413µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:49:23Z"
    - latency: 1.408369ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:48:23Z"
    - latency: 1.794447ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:47:23Z"
    - latency: 1.670617ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:46:23Z"
    - latency: 8.308956ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:45:23Z"
    - latency: 1.100851ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:23Z"
    - latency: 926.83µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:03:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-90-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-90.us-east-2.compute.internal
      uid: 2bd51030-7e31-4f5e-b8ca-8f377ea816aa
    resourceVersion: "179463"
    uid: 9f3b0969-bd62-4796-b6d3-ccddf9dc5484
  spec:
    sourcePod: network-check-source-6f78d59f99-fvdt8
    targetEndpoint: a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:09:23Z"
      message: 'load-balancer-api-external: tcp connection to a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.21794ms
      message: 'load-balancer-api-external: tcp connection to a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:57:23Z"
    - latency: 8.879706ms
      message: 'load-balancer-api-external: resolved host name a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:57:23Z"
    - latency: 10.194215ms
      message: 'load-balancer-api-external: tcp connection to a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:56:23Z"
    - latency: 9.311591ms
      message: 'load-balancer-api-external: resolved host name a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:56:23Z"
    - latency: 5.262424ms
      message: 'load-balancer-api-external: tcp connection to a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:55:23Z"
    - latency: 7.233235ms
      message: 'load-balancer-api-external: resolved host name a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:55:23Z"
    - latency: 5.866102ms
      message: 'load-balancer-api-external: tcp connection to a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:54:23Z"
    - latency: 6.786443ms
      message: 'load-balancer-api-external: resolved host name a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:54:23Z"
    - latency: 6.397245ms
      message: 'load-balancer-api-external: tcp connection to a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:53:23Z"
    - latency: 7.289775ms
      message: 'load-balancer-api-external: resolved host name a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:53:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:03:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-90-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-90.us-east-2.compute.internal
      uid: 2bd51030-7e31-4f5e-b8ca-8f377ea816aa
    resourceVersion: "179464"
    uid: 6e52ffdb-57bc-4260-8d32-c5ee92f72dca
  spec:
    sourcePod: network-check-source-6f78d59f99-fvdt8
    targetEndpoint: a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:09:23Z"
      message: 'load-balancer-api-internal: tcp connection to a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.251695ms
      message: 'load-balancer-api-internal: tcp connection to a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:57:23Z"
    - latency: 8.957064ms
      message: 'load-balancer-api-internal: resolved host name a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:57:23Z"
    - latency: 10.63217ms
      message: 'load-balancer-api-internal: tcp connection to a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:56:23Z"
    - latency: 9.522278ms
      message: 'load-balancer-api-internal: resolved host name a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:56:23Z"
    - latency: 5.81134ms
      message: 'load-balancer-api-internal: tcp connection to a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:55:23Z"
    - latency: 7.256397ms
      message: 'load-balancer-api-internal: resolved host name a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:55:23Z"
    - latency: 5.066298ms
      message: 'load-balancer-api-internal: tcp connection to a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:54:23Z"
    - latency: 6.845442ms
      message: 'load-balancer-api-internal: resolved host name a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:54:23Z"
    - latency: 5.469471ms
      message: 'load-balancer-api-internal: tcp connection to a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:53:23Z"
    - latency: 7.234032ms
      message: 'load-balancer-api-internal: resolved host name a3a69380a59394643ab3370171d02419-025d038ed1951c9b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:53:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:03:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-90-to-network-check-target-ip-10-0-139-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-90.us-east-2.compute.internal
      uid: 2bd51030-7e31-4f5e-b8ca-8f377ea816aa
    resourceVersion: "162362"
    uid: 370723f2-20d2-4ea1-a767-52d7763e74af
  spec:
    sourcePod: network-check-source-6f78d59f99-fvdt8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:10:23Z"
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.042171ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:52:23Z"
    - latency: 2.141049ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:51:23Z"
    - latency: 2.837863ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:50:23Z"
    - latency: 2.93112ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:49:23Z"
    - latency: 3.111654ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:48:23Z"
    - latency: 1.919695ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:47:23Z"
    - latency: 2.834831ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:46:23Z"
    - latency: 7.749347ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:45:23Z"
    - latency: 2.171933ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:23Z"
    - latency: 1.942705ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:03:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-90-to-network-check-target-ip-10-0-139-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-90.us-east-2.compute.internal
      uid: 2bd51030-7e31-4f5e-b8ca-8f377ea816aa
    resourceVersion: "162363"
    uid: a618c9aa-41c2-4c9a-b827-69c59bf96aae
  spec:
    sourcePod: network-check-source-6f78d59f99-fvdt8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:10:23Z"
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.751383ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:52:23Z"
    - latency: 1.62651ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:51:23Z"
    - latency: 1.089333ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:50:23Z"
    - latency: 1.27707ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:49:23Z"
    - latency: 1.088596ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:48:23Z"
    - latency: 936.837µs
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:47:23Z"
    - latency: 973.297µs
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:46:23Z"
    - latency: 12.893608ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:45:23Z"
    - latency: 1.375424ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:23Z"
    - latency: 1.267158ms
      message: 'network-check-target-ip-10-0-139-90: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:03:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-90-to-network-check-target-ip-10-0-140-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-90.us-east-2.compute.internal
      uid: 2bd51030-7e31-4f5e-b8ca-8f377ea816aa
    resourceVersion: "162365"
    uid: cdfda9f4-8fb3-4510-9a4b-849c2af2cdba
  spec:
    sourcePod: network-check-source-6f78d59f99-fvdt8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:10:23Z"
      message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 38.211535ms
      message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:52:23Z"
    - latency: 2.969626ms
      message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:51:23Z"
    - latency: 3.326708ms
      message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:50:23Z"
    - latency: 2.466056ms
      message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:49:23Z"
    - latency: 2.241972ms
      message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:48:23Z"
    - latency: 2.539943ms
      message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:47:23Z"
    - latency: 2.733668ms
      message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:46:23Z"
    - latency: 6.630153ms
      message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:45:23Z"
    - latency: 2.229376ms
      message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:23Z"
    - latency: 2.034845ms
      message: 'network-check-target-ip-10-0-140-12: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:03:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-90-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-90.us-east-2.compute.internal
      uid: 2bd51030-7e31-4f5e-b8ca-8f377ea816aa
    resourceVersion: "179462"
    uid: 19eaa269-0abb-4608-a93f-8279dd177f6c
  spec:
    sourcePod: network-check-source-6f78d59f99-fvdt8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:09:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 995.324µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:57:23Z"
    - latency: 3.340772ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:57:23Z"
    - latency: 1.323087ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:56:23Z"
    - latency: 2.863283ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:56:23Z"
    - latency: 1.166488ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:55:23Z"
    - latency: 2.229062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:55:23Z"
    - latency: 1.188082ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:54:23Z"
    - latency: 2.082738ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:54:23Z"
    - latency: 1.29485ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:53:23Z"
    - latency: 2.168572ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:53:23Z"
kind: List
metadata:
  resourceVersion: ""