apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:06:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-217-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-217.us-east-2.compute.internal
      uid: c4bca572-ef54-4671-94fe-85bd8c5fa789
    resourceVersion: "64097"
    uid: a02ab2a0-c9ee-4190-8564-43963edc9bfa
  spec:
    sourcePod: network-check-source-6f78d59f99-sb9tl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:13:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.186137ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:34:05Z"
    - latency: 1.226277ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:33:05Z"
    - latency: 1.320568ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:32:05Z"
    - latency: 1.665701ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:31:05Z"
    - latency: 14.302356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:30:05Z"
    - latency: 1.333229ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:29:05Z"
    - latency: 1.435582ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:28:05Z"
    - latency: 1.260517ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:27:05Z"
    - latency: 1.281755ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:26:05Z"
    - latency: 1.854321ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:25:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:06:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-217-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-217.us-east-2.compute.internal
      uid: c4bca572-ef54-4671-94fe-85bd8c5fa789
    resourceVersion: "66122"
    uid: 05045b22-537f-4c41-8b58-d7770b6a3eb9
  spec:
    sourcePod: network-check-source-6f78d59f99-sb9tl
    targetEndpoint: a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:12:05Z"
      message: 'load-balancer-api-external: tcp connection to a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.149848ms
      message: 'load-balancer-api-external: tcp connection to a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:36:05Z"
    - latency: 10.398643ms
      message: 'load-balancer-api-external: resolved host name a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:36:05Z"
    - latency: 6.670427ms
      message: 'load-balancer-api-external: tcp connection to a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:35:05Z"
    - latency: 6.789557ms
      message: 'load-balancer-api-external: resolved host name a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:35:05Z"
    - latency: 5.973132ms
      message: 'load-balancer-api-external: tcp connection to a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:34:05Z"
    - latency: 7.429407ms
      message: 'load-balancer-api-external: resolved host name a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:34:05Z"
    - latency: 5.237396ms
      message: 'load-balancer-api-external: tcp connection to a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:33:05Z"
    - latency: 7.300337ms
      message: 'load-balancer-api-external: resolved host name a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:33:05Z"
    - latency: 5.49885ms
      message: 'load-balancer-api-external: tcp connection to a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:32:05Z"
    - latency: 11.001666ms
      message: 'load-balancer-api-external: resolved host name a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:32:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:06:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-217-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-217.us-east-2.compute.internal
      uid: c4bca572-ef54-4671-94fe-85bd8c5fa789
    resourceVersion: "66123"
    uid: 91a43724-4591-4d9e-8122-2a416d4a197c
  spec:
    sourcePod: network-check-source-6f78d59f99-sb9tl
    targetEndpoint: a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:12:05Z"
      message: 'load-balancer-api-internal: tcp connection to a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.163397ms
      message: 'load-balancer-api-internal: tcp connection to a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:36:05Z"
    - latency: 10.331057ms
      message: 'load-balancer-api-internal: resolved host name a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:36:05Z"
    - latency: 6.68562ms
      message: 'load-balancer-api-internal: tcp connection to a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:35:05Z"
    - latency: 6.843649ms
      message: 'load-balancer-api-internal: resolved host name a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:35:05Z"
    - latency: 5.980831ms
      message: 'load-balancer-api-internal: tcp connection to a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:34:05Z"
    - latency: 7.323678ms
      message: 'load-balancer-api-internal: resolved host name a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:34:05Z"
    - latency: 5.171246ms
      message: 'load-balancer-api-internal: tcp connection to a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:33:05Z"
    - latency: 7.211958ms
      message: 'load-balancer-api-internal: resolved host name a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:33:05Z"
    - latency: 5.53794ms
      message: 'load-balancer-api-internal: tcp connection to a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:32:05Z"
    - latency: 10.941921ms
      message: 'load-balancer-api-internal: resolved host name a4e20f0dbc064426394ab1d728f3b224-236c724be50ab12d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:32:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:06:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-217-to-network-check-target-ip-10-0-129-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-217.us-east-2.compute.internal
      uid: c4bca572-ef54-4671-94fe-85bd8c5fa789
    resourceVersion: "64095"
    uid: cdd6ba02-6f87-4600-b557-76383a9df9b8
  spec:
    sourcePod: network-check-source-6f78d59f99-sb9tl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:13:05Z"
      message: 'network-check-target-ip-10-0-129-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.389506ms
      message: 'network-check-target-ip-10-0-129-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:34:05Z"
    - latency: 2.373552ms
      message: 'network-check-target-ip-10-0-129-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:33:05Z"
    - latency: 2.552394ms
      message: 'network-check-target-ip-10-0-129-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:32:05Z"
    - latency: 2.330213ms
      message: 'network-check-target-ip-10-0-129-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:31:05Z"
    - latency: 21.264297ms
      message: 'network-check-target-ip-10-0-129-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:30:05Z"
    - latency: 2.452498ms
      message: 'network-check-target-ip-10-0-129-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:29:05Z"
    - latency: 2.254483ms
      message: 'network-check-target-ip-10-0-129-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:28:05Z"
    - latency: 2.513432ms
      message: 'network-check-target-ip-10-0-129-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:27:05Z"
    - latency: 2.774653ms
      message: 'network-check-target-ip-10-0-129-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:26:05Z"
    - latency: 2.819411ms
      message: 'network-check-target-ip-10-0-129-14: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:25:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:06:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-217-to-network-check-target-ip-10-0-139-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-217.us-east-2.compute.internal
      uid: c4bca572-ef54-4671-94fe-85bd8c5fa789
    resourceVersion: "64094"
    uid: 0c72315a-6533-4396-8642-70b923301284
  spec:
    sourcePod: network-check-source-6f78d59f99-sb9tl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:13:05Z"
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.082326ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:34:05Z"
    - latency: 1.417482ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:33:05Z"
    - latency: 1.046665ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:32:05Z"
    - latency: 1.780599ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:31:05Z"
    - latency: 14.203219ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:30:05Z"
    - latency: 1.183277ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:29:05Z"
    - latency: 823.238µs
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:28:05Z"
    - latency: 1.614304ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:27:05Z"
    - latency: 1.023409ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:26:05Z"
    - latency: 1.805603ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:25:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:06:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-217-to-network-check-target-ip-10-0-141-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-217.us-east-2.compute.internal
      uid: c4bca572-ef54-4671-94fe-85bd8c5fa789
    resourceVersion: "64096"
    uid: ebfa9b8a-069c-4b13-872d-5a4870bcf086
  spec:
    sourcePod: network-check-source-6f78d59f99-sb9tl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:13:05Z"
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.272032ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:34:05Z"
    - latency: 2.483439ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:33:05Z"
    - latency: 1.98073ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:32:05Z"
    - latency: 2.1638ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:31:05Z"
    - latency: 13.935961ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:30:05Z"
    - latency: 2.434399ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:29:05Z"
    - latency: 2.465565ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:28:05Z"
    - latency: 2.349925ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:27:05Z"
    - latency: 2.361101ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:26:05Z"
    - latency: 2.249574ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:25:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:06:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-217-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-217.us-east-2.compute.internal
      uid: c4bca572-ef54-4671-94fe-85bd8c5fa789
    resourceVersion: "66121"
    uid: 3be5b73b-a6b7-4107-97e2-d5449dd7883e
  spec:
    sourcePod: network-check-source-6f78d59f99-sb9tl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:12:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.000578ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:36:05Z"
    - latency: 2.012046ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:36:05Z"
    - latency: 941.931µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:35:05Z"
    - latency: 2.418172ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:35:05Z"
    - latency: 1.199871ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:34:05Z"
    - latency: 1.746595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:34:05Z"
    - latency: 1.221203ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:33:05Z"
    - latency: 2.520972ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:33:05Z"
    - latency: 1.091251ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:32:05Z"
    - latency: 1.707721ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:32:05Z"
kind: List
metadata:
  resourceVersion: ""