apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T15:37:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-137-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-137.ec2.internal
      uid: 753666aa-8e1d-4a0c-907e-e0e1a9edbb4c
    resourceVersion: "66162"
    uid: 15b7cf55-7cf2-486d-b393-c54f987e25f0
  spec:
    sourcePod: network-check-source-7cbc45fddc-7qzjj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:44:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.45561ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:12:52Z"
    - latency: 1.320868ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:11:52Z"
    - latency: 1.153476ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:10:52Z"
    - latency: 1.370478ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:09:52Z"
    - latency: 1.141704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:08:52Z"
    - latency: 1.255173ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:07:52Z"
    - latency: 1.068654ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:06:52Z"
    - latency: 1.349605ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:05:52Z"
    - latency: 1.373311ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:04:52Z"
    - latency: 942.959µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:03:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T15:37:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-137-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-137.ec2.internal
      uid: 753666aa-8e1d-4a0c-907e-e0e1a9edbb4c
    resourceVersion: "61533"
    uid: aeab4c32-5d23-4142-9506-1a1b9a11155d
  spec:
    sourcePod: network-check-source-7cbc45fddc-7qzjj
    targetEndpoint: ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:43:52Z"
      message: 'load-balancer-api-external: tcp connection to ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.217641ms
      message: 'load-balancer-api-external: tcp connection to ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:07:52Z"
    - latency: 9.34979ms
      message: 'load-balancer-api-external: resolved host name ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:07:52Z"
    - latency: 4.099868ms
      message: 'load-balancer-api-external: tcp connection to ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:06:52Z"
    - latency: 8.89868ms
      message: 'load-balancer-api-external: resolved host name ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:06:52Z"
    - latency: 4.37199ms
      message: 'load-balancer-api-external: tcp connection to ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:05:52Z"
    - latency: 8.498364ms
      message: 'load-balancer-api-external: resolved host name ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:05:52Z"
    - latency: 4.322721ms
      message: 'load-balancer-api-external: tcp connection to ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:04:52Z"
    - latency: 9.010559ms
      message: 'load-balancer-api-external: resolved host name ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:04:52Z"
    - latency: 5.459507ms
      message: 'load-balancer-api-external: tcp connection to ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:03:52Z"
    - latency: 9.031162ms
      message: 'load-balancer-api-external: resolved host name ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:03:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T15:37:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-137-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-137.ec2.internal
      uid: 753666aa-8e1d-4a0c-907e-e0e1a9edbb4c
    resourceVersion: "61534"
    uid: c41ecb7b-8692-4a12-b253-1f8241e0dbe5
  spec:
    sourcePod: network-check-source-7cbc45fddc-7qzjj
    targetEndpoint: ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:43:52Z"
      message: 'load-balancer-api-internal: tcp connection to ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.155462ms
      message: 'load-balancer-api-internal: tcp connection to ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:07:52Z"
    - latency: 9.281596ms
      message: 'load-balancer-api-internal: resolved host name ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:07:52Z"
    - latency: 4.142882ms
      message: 'load-balancer-api-internal: tcp connection to ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:06:52Z"
    - latency: 8.820599ms
      message: 'load-balancer-api-internal: resolved host name ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:06:52Z"
    - latency: 4.374308ms
      message: 'load-balancer-api-internal: tcp connection to ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:05:52Z"
    - latency: 8.416134ms
      message: 'load-balancer-api-internal: resolved host name ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:05:52Z"
    - latency: 4.335907ms
      message: 'load-balancer-api-internal: tcp connection to ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:04:52Z"
    - latency: 8.952805ms
      message: 'load-balancer-api-internal: resolved host name ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:04:52Z"
    - latency: 5.455746ms
      message: 'load-balancer-api-internal: tcp connection to ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:03:52Z"
    - latency: 8.979031ms
      message: 'load-balancer-api-internal: resolved host name ab2b521ef7e924b80a490bdc96e6d2f3-3fece5242ee9e96e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:03:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T15:37:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-137-to-network-check-target-ip-10-0-130-208
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-137.ec2.internal
      uid: 753666aa-8e1d-4a0c-907e-e0e1a9edbb4c
    resourceVersion: "66160"
    uid: 85685554-846b-4917-8ef4-b8df6e09865a
  spec:
    sourcePod: network-check-source-7cbc45fddc-7qzjj
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:44:52Z"
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.823013ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:12:52Z"
    - latency: 2.401598ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:11:52Z"
    - latency: 2.437343ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:10:52Z"
    - latency: 2.208621ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:09:52Z"
    - latency: 2.390116ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:08:52Z"
    - latency: 2.097045ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:07:52Z"
    - latency: 2.359655ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:06:52Z"
    - latency: 2.534952ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:05:52Z"
    - latency: 2.358153ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:04:52Z"
    - latency: 2.388972ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:03:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T15:37:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-137-to-network-check-target-ip-10-0-130-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-137.ec2.internal
      uid: 753666aa-8e1d-4a0c-907e-e0e1a9edbb4c
    resourceVersion: "66161"
    uid: 1d302d45-0e39-46bd-9443-14f17e45c59b
  spec:
    sourcePod: network-check-source-7cbc45fddc-7qzjj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:44:52Z"
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.740233ms
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:12:52Z"
    - latency: 2.061885ms
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:11:52Z"
    - latency: 2.062714ms
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:10:52Z"
    - latency: 1.923017ms
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:09:52Z"
    - latency: 1.996936ms
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:08:52Z"
    - latency: 1.759585ms
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:07:52Z"
    - latency: 2.217368ms
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:06:52Z"
    - latency: 1.983133ms
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:05:52Z"
    - latency: 2.061072ms
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:04:52Z"
    - latency: 1.595198ms
      message: 'network-check-target-ip-10-0-130-223: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:03:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T15:37:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-137-to-network-check-target-ip-10-0-133-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-137.ec2.internal
      uid: 753666aa-8e1d-4a0c-907e-e0e1a9edbb4c
    resourceVersion: "66159"
    uid: fc109be4-1d2b-45de-bda0-2a091503aa86
  spec:
    sourcePod: network-check-source-7cbc45fddc-7qzjj
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:44:52Z"
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.034059ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:12:52Z"
    - latency: 948.177µs
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:11:52Z"
    - latency: 996.246µs
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:10:52Z"
    - latency: 884.849µs
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:09:52Z"
    - latency: 1.444431ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:08:52Z"
    - latency: 1.470033ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:07:52Z"
    - latency: 1.437861ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:06:52Z"
    - latency: 935.943µs
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:05:52Z"
    - latency: 1.079762ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:04:52Z"
    - latency: 1.13484ms
      message: 'network-check-target-ip-10-0-133-137: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:03:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T15:37:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-137-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-137.ec2.internal
      uid: 753666aa-8e1d-4a0c-907e-e0e1a9edbb4c
    resourceVersion: "61532"
    uid: b0fb79c0-fab1-4921-b29d-ec021fcdca12
  spec:
    sourcePod: network-check-source-7cbc45fddc-7qzjj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T15:43:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.120372ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:07:52Z"
    - latency: 1.533202ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:07:52Z"
    - latency: 1.057692ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:06:52Z"
    - latency: 2.303524ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:06:52Z"
    - latency: 1.013938ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:05:52Z"
    - latency: 1.783156ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:05:52Z"
    - latency: 900.089µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:04:52Z"
    - latency: 1.82188ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:04:52Z"
    - latency: 1.067795ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T16:03:52Z"
    - latency: 2.098255ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T16:03:52Z"
kind: List
metadata:
  resourceVersion: ""