apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:39:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-218-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-218.ec2.internal
      uid: 04953218-01a2-4a0b-9315-e40ff165eb89
    resourceVersion: "53049"
    uid: 7ad54b8e-5703-440f-9a16-1160c40087a6
  spec:
    sourcePod: network-check-source-6f8b768455-mdqv5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:46:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.011535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:45Z"
    - latency: 1.209304ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:45Z"
    - latency: 1.339865ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:45Z"
    - latency: 1.116159ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:45Z"
    - latency: 1.126634ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:45Z"
    - latency: 869.27µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:45Z"
    - latency: 833.057µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:45Z"
    - latency: 1.820885ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:45Z"
    - latency: 1.081024ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:45Z"
    - latency: 1.044021ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:58:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:39:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-218-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-218.ec2.internal
      uid: 04953218-01a2-4a0b-9315-e40ff165eb89
    resourceVersion: "54572"
    uid: ec8335aa-edf5-497f-a0c4-ae29f1fa9f97
  spec:
    sourcePod: network-check-source-6f8b768455-mdqv5
    targetEndpoint: addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:45:45Z"
      message: 'load-balancer-api-external: tcp connection to addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.187573ms
      message: 'load-balancer-api-external: tcp connection to addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:09:45Z"
    - latency: 8.228478ms
      message: 'load-balancer-api-external: resolved host name addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:09:45Z"
    - latency: 5.387176ms
      message: 'load-balancer-api-external: tcp connection to addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:08:45Z"
    - latency: 8.586203ms
      message: 'load-balancer-api-external: resolved host name addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:08:45Z"
    - latency: 4.806ms
      message: 'load-balancer-api-external: tcp connection to addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:45Z"
    - latency: 9.243399ms
      message: 'load-balancer-api-external: resolved host name addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:07:45Z"
    - latency: 4.733815ms
      message: 'load-balancer-api-external: tcp connection to addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:45Z"
    - latency: 9.005588ms
      message: 'load-balancer-api-external: resolved host name addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:06:45Z"
    - latency: 5.091257ms
      message: 'load-balancer-api-external: tcp connection to addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:45Z"
    - latency: 12.821645ms
      message: 'load-balancer-api-external: resolved host name addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:05:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:39:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-218-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-218.ec2.internal
      uid: 04953218-01a2-4a0b-9315-e40ff165eb89
    resourceVersion: "54573"
    uid: b90151ab-6dbd-45e9-9d47-8e1987ae8038
  spec:
    sourcePod: network-check-source-6f8b768455-mdqv5
    targetEndpoint: addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:45:45Z"
      message: 'load-balancer-api-internal: tcp connection to addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.838355ms
      message: 'load-balancer-api-internal: tcp connection to addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:09:45Z"
    - latency: 8.142278ms
      message: 'load-balancer-api-internal: resolved host name addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:09:45Z"
    - latency: 5.409662ms
      message: 'load-balancer-api-internal: tcp connection to addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:08:45Z"
    - latency: 8.490622ms
      message: 'load-balancer-api-internal: resolved host name addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:08:45Z"
    - latency: 4.836139ms
      message: 'load-balancer-api-internal: tcp connection to addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:45Z"
    - latency: 9.147996ms
      message: 'load-balancer-api-internal: resolved host name addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:07:45Z"
    - latency: 4.698169ms
      message: 'load-balancer-api-internal: tcp connection to addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:45Z"
    - latency: 8.892ms
      message: 'load-balancer-api-internal: resolved host name addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:06:45Z"
    - latency: 5.102363ms
      message: 'load-balancer-api-internal: tcp connection to addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:45Z"
    - latency: 12.76145ms
      message: 'load-balancer-api-internal: resolved host name addd040c5d3d741ef9c841e69df9285d-cbad15f883da0c66.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:05:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:39:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-218-to-network-check-target-ip-10-0-131-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-218.ec2.internal
      uid: 04953218-01a2-4a0b-9315-e40ff165eb89
    resourceVersion: "53048"
    uid: e7e656bd-33f1-4593-a2e6-26a955295b1f
  spec:
    sourcePod: network-check-source-6f8b768455-mdqv5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:46:45Z"
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.070742ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:45Z"
    - latency: 1.887478ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:45Z"
    - latency: 1.854078ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:45Z"
    - latency: 2.182963ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:45Z"
    - latency: 2.356964ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:45Z"
    - latency: 1.902944ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:45Z"
    - latency: 1.671806ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:45Z"
    - latency: 2.068855ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:45Z"
    - latency: 2.334012ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:45Z"
    - latency: 2.236353ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:58:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:39:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-218-to-network-check-target-ip-10-0-137-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-218.ec2.internal
      uid: 04953218-01a2-4a0b-9315-e40ff165eb89
    resourceVersion: "53046"
    uid: 48fe0108-6c72-4d47-a482-e2c64c473e83
  spec:
    sourcePod: network-check-source-6f8b768455-mdqv5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:46:45Z"
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.147µs
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:45Z"
    - latency: 980.065µs
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:45Z"
    - latency: 1.314259ms
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:45Z"
    - latency: 810.066µs
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:45Z"
    - latency: 1.600877ms
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:45Z"
    - latency: 1.376425ms
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:45Z"
    - latency: 995.005µs
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:45Z"
    - latency: 923.838µs
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:45Z"
    - latency: 759.098µs
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:45Z"
    - latency: 870.259µs
      message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:58:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:39:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-218-to-network-check-target-ip-10-0-138-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-218.ec2.internal
      uid: 04953218-01a2-4a0b-9315-e40ff165eb89
    resourceVersion: "53047"
    uid: a1b18477-7923-4a29-b97d-cba7f804d12e
  spec:
    sourcePod: network-check-source-6f8b768455-mdqv5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:46:45Z"
      message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.533063ms
      message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:45Z"
    - latency: 2.101739ms
      message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:45Z"
    - latency: 2.189027ms
      message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:45Z"
    - latency: 2.446052ms
      message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:45Z"
    - latency: 2.401519ms
      message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:45Z"
    - latency: 2.337508ms
      message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:45Z"
    - latency: 1.75894ms
      message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:45Z"
    - latency: 2.364484ms
      message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:45Z"
    - latency: 2.412388ms
      message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:45Z"
    - latency: 2.475888ms
      message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:58:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:39:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-218-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-218.ec2.internal
      uid: 04953218-01a2-4a0b-9315-e40ff165eb89
    resourceVersion: "54571"
    uid: 2f254d90-a501-4ca5-abbb-1a7c015d5852
  spec:
    sourcePod: network-check-source-6f8b768455-mdqv5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:45:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.317µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:09:45Z"
    - latency: 2.150868ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:09:45Z"
    - latency: 1.3906ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:08:45Z"
    - latency: 1.971037ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:08:45Z"
    - latency: 841.769µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:45Z"
    - latency: 2.547323ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:07:45Z"
    - latency: 845.466µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:45Z"
    - latency: 1.829073ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:06:45Z"
    - latency: 951.605µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:45Z"
    - latency: 2.196902ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:05:45Z"
kind: List
metadata:
  resourceVersion: ""