apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T09:50:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-51-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-51.ec2.internal
      uid: a7eab05a-32e8-42f2-a65e-01dd998facca
    resourceVersion: "20602"
    uid: 46c4c515-ef95-45c3-b161-70b627db1280
  spec:
    sourcePod: network-check-source-685456655f-2v425
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T09:57:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 943.568µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:11:57Z"
    - latency: 820.712µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:10:57Z"
    - latency: 1.260698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:09:57Z"
    - latency: 992.312µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:08:57Z"
    - latency: 940.577µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:07:57Z"
    - latency: 1.164313ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:06:57Z"
    - latency: 1.120416ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:05:57Z"
    - latency: 918.639µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:04:57Z"
    - latency: 1.211601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:03:57Z"
    - latency: 1.101663ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:02:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T09:50:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-51-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-51.ec2.internal
      uid: a7eab05a-32e8-42f2-a65e-01dd998facca
    resourceVersion: "22233"
    uid: 9a524c47-f19b-41db-8a51-f9330af82b14
  spec:
    sourcePod: network-check-source-685456655f-2v425
    targetEndpoint: acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T09:56:57Z"
      message: 'load-balancer-api-external: tcp connection to acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.962316ms
      message: 'load-balancer-api-external: tcp connection to acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:14:57Z"
    - latency: 6.446025ms
      message: 'load-balancer-api-external: resolved host name acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:14:57Z"
    - latency: 3.773963ms
      message: 'load-balancer-api-external: tcp connection to acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:13:57Z"
    - latency: 7.797619ms
      message: 'load-balancer-api-external: resolved host name acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:13:57Z"
    - latency: 5.089777ms
      message: 'load-balancer-api-external: tcp connection to acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:12:57Z"
    - latency: 8.380303ms
      message: 'load-balancer-api-external: resolved host name acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:12:57Z"
    - latency: 5.04404ms
      message: 'load-balancer-api-external: tcp connection to acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:11:57Z"
    - latency: 11.592794ms
      message: 'load-balancer-api-external: resolved host name acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:11:57Z"
    - latency: 5.661746ms
      message: 'load-balancer-api-external: tcp connection to acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:10:57Z"
    - latency: 7.682975ms
      message: 'load-balancer-api-external: resolved host name acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:10:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T09:50:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-51-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-51.ec2.internal
      uid: a7eab05a-32e8-42f2-a65e-01dd998facca
    resourceVersion: "22232"
    uid: 137f864b-dc4b-4cbf-b95b-f798365f0360
  spec:
    sourcePod: network-check-source-685456655f-2v425
    targetEndpoint: acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T09:56:57Z"
      message: 'load-balancer-api-internal: tcp connection to acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.003009ms
      message: 'load-balancer-api-internal: tcp connection to acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:14:57Z"
    - latency: 6.411528ms
      message: 'load-balancer-api-internal: resolved host name acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:14:57Z"
    - latency: 5.923319ms
      message: 'load-balancer-api-internal: tcp connection to acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:13:57Z"
    - latency: 7.723612ms
      message: 'load-balancer-api-internal: resolved host name acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:13:57Z"
    - latency: 4.297362ms
      message: 'load-balancer-api-internal: tcp connection to acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:12:57Z"
    - latency: 8.287535ms
      message: 'load-balancer-api-internal: resolved host name acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:12:57Z"
    - latency: 5.032802ms
      message: 'load-balancer-api-internal: tcp connection to acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:11:57Z"
    - latency: 11.599874ms
      message: 'load-balancer-api-internal: resolved host name acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:11:57Z"
    - latency: 5.481382ms
      message: 'load-balancer-api-internal: tcp connection to acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:10:57Z"
    - latency: 7.592074ms
      message: 'load-balancer-api-internal: resolved host name acbc8dfe459de414cb5a6b318e8a20c2-92ab7a1c7e3ad848.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:10:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T09:50:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-51-to-network-check-target-ip-10-0-132-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-51.ec2.internal
      uid: a7eab05a-32e8-42f2-a65e-01dd998facca
    resourceVersion: "20599"
    uid: 0fb5783c-a56f-45b5-95a1-2f0d29787451
  spec:
    sourcePod: network-check-source-685456655f-2v425
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T09:57:57Z"
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 924.056µs
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:11:57Z"
    - latency: 790.012µs
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:10:57Z"
    - latency: 1.03798ms
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:09:57Z"
    - latency: 691.515µs
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:08:57Z"
    - latency: 1.348419ms
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:07:57Z"
    - latency: 728.572µs
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:06:57Z"
    - latency: 775.811µs
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:05:57Z"
    - latency: 1.001149ms
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:04:57Z"
    - latency: 805.325µs
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:03:57Z"
    - latency: 1.122516ms
      message: 'network-check-target-ip-10-0-132-51: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:02:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T09:50:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-51-to-network-check-target-ip-10-0-135-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-51.ec2.internal
      uid: a7eab05a-32e8-42f2-a65e-01dd998facca
    resourceVersion: "20600"
    uid: 44e761a3-8a70-49b6-97e1-81f7f0564e6e
  spec:
    sourcePod: network-check-source-685456655f-2v425
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T09:57:57Z"
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.916811ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:11:57Z"
    - latency: 1.799518ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:10:57Z"
    - latency: 1.613307ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:09:57Z"
    - latency: 1.47857ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:08:57Z"
    - latency: 1.733859ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:07:57Z"
    - latency: 2.029035ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:06:57Z"
    - latency: 1.984788ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:05:57Z"
    - latency: 2.124192ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:04:57Z"
    - latency: 1.662081ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:03:57Z"
    - latency: 1.689424ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:02:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T09:50:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-51-to-network-check-target-ip-10-0-143-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-51.ec2.internal
      uid: a7eab05a-32e8-42f2-a65e-01dd998facca
    resourceVersion: "20601"
    uid: 9472f508-a17f-4b1e-a400-da9a3cfe422d
  spec:
    sourcePod: network-check-source-685456655f-2v425
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T09:57:57Z"
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.935988ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:11:57Z"
    - latency: 2.228103ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:10:57Z"
    - latency: 2.134763ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:09:57Z"
    - latency: 2.067166ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:08:57Z"
    - latency: 2.228121ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:07:57Z"
    - latency: 2.071417ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:06:57Z"
    - latency: 2.649684ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:05:57Z"
    - latency: 2.130496ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:04:57Z"
    - latency: 2.150755ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:03:57Z"
    - latency: 2.19335ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:02:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T09:50:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-51-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-51.ec2.internal
      uid: a7eab05a-32e8-42f2-a65e-01dd998facca
    resourceVersion: "22231"
    uid: 8cae7b65-7d30-42a0-96ad-3e0dbb9b9481
  spec:
    sourcePod: network-check-source-685456655f-2v425
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T09:56:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 993.373µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:14:57Z"
    - latency: 1.566151ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:14:57Z"
    - latency: 917.999µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:13:57Z"
    - latency: 1.75492ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:13:57Z"
    - latency: 669.141µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:12:57Z"
    - latency: 2.182908ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:12:57Z"
    - latency: 717.362µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:11:57Z"
    - latency: 1.944411ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:11:57Z"
    - latency: 800.886µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T10:10:57Z"
    - latency: 1.56439ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T10:10:57Z"
kind: List
metadata:
  resourceVersion: ""