apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T00:53:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-48-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-48.ec2.internal
      uid: b20ecb34-e92c-42d2-9673-12e2b68cb76c
    resourceVersion: "31111"
    uid: 110500dd-3710-4831-9c69-93b63cf3955c
  spec:
    sourcePod: network-check-source-56d84b9f44-5h5b7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T01:00:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.155917ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:07:10Z"
    - latency: 1.191194ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:06:10Z"
    - latency: 1.356633ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:05:10Z"
    - latency: 1.144099ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:04:10Z"
    - latency: 1.026508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:03:10Z"
    - latency: 1.052434ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:02:10Z"
    - latency: 1.026006ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:01:10Z"
    - latency: 1.03496ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:00:10Z"
    - latency: 1.375421ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T00:59:10Z"
    - latency: 1.057254ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T00:58:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T00:53:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-48-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-48.ec2.internal
      uid: b20ecb34-e92c-42d2-9673-12e2b68cb76c
    resourceVersion: "29214"
    uid: 7df5cd23-07e1-4fca-8a87-9fb35a3dcbd0
  spec:
    sourcePod: network-check-source-56d84b9f44-5h5b7
    targetEndpoint: a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T00:59:10Z"
      message: 'load-balancer-api-external: tcp connection to a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.382766ms
      message: 'load-balancer-api-external: tcp connection to a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:05:10Z"
    - latency: 8.574372ms
      message: 'load-balancer-api-external: resolved host name a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:05:10Z"
    - latency: 4.403225ms
      message: 'load-balancer-api-external: tcp connection to a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:04:10Z"
    - latency: 7.348711ms
      message: 'load-balancer-api-external: resolved host name a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:04:10Z"
    - latency: 4.906576ms
      message: 'load-balancer-api-external: tcp connection to a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:03:10Z"
    - latency: 10.229807ms
      message: 'load-balancer-api-external: resolved host name a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:03:10Z"
    - latency: 4.85571ms
      message: 'load-balancer-api-external: tcp connection to a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:02:10Z"
    - latency: 7.26265ms
      message: 'load-balancer-api-external: resolved host name a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:02:10Z"
    - latency: 4.77848ms
      message: 'load-balancer-api-external: tcp connection to a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:01:10Z"
    - latency: 6.644314ms
      message: 'load-balancer-api-external: resolved host name a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:01:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T00:53:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-48-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-48.ec2.internal
      uid: b20ecb34-e92c-42d2-9673-12e2b68cb76c
    resourceVersion: "29213"
    uid: 0aae43e1-6a7a-4a64-b13f-c75512b7e744
  spec:
    sourcePod: network-check-source-56d84b9f44-5h5b7
    targetEndpoint: a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T00:59:10Z"
      message: 'load-balancer-api-internal: tcp connection to a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.333586ms
      message: 'load-balancer-api-internal: tcp connection to a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:05:10Z"
    - latency: 8.6325ms
      message: 'load-balancer-api-internal: resolved host name a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:05:10Z"
    - latency: 3.480353ms
      message: 'load-balancer-api-internal: tcp connection to a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:04:10Z"
    - latency: 7.293131ms
      message: 'load-balancer-api-internal: resolved host name a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:04:10Z"
    - latency: 4.96078ms
      message: 'load-balancer-api-internal: tcp connection to a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:03:10Z"
    - latency: 10.2102ms
      message: 'load-balancer-api-internal: resolved host name a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:03:10Z"
    - latency: 4.86216ms
      message: 'load-balancer-api-internal: tcp connection to a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:02:10Z"
    - latency: 7.110468ms
      message: 'load-balancer-api-internal: resolved host name a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:02:10Z"
    - latency: 4.238772ms
      message: 'load-balancer-api-internal: tcp connection to a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:01:10Z"
    - latency: 6.626938ms
      message: 'load-balancer-api-internal: resolved host name a16ec071551194b96bb8a2180008baf4-95f74a4d07490307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:01:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T00:53:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-48-to-network-check-target-ip-10-0-134-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-48.ec2.internal
      uid: b20ecb34-e92c-42d2-9673-12e2b68cb76c
    resourceVersion: "31108"
    uid: f63af9b2-dc85-4b75-b388-1f3cbef7d4bb
  spec:
    sourcePod: network-check-source-56d84b9f44-5h5b7
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T01:00:10Z"
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 868.601µs
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:07:10Z"
    - latency: 797.895µs
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:06:10Z"
    - latency: 1.520187ms
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:05:10Z"
    - latency: 818.745µs
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:04:10Z"
    - latency: 902.584µs
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:03:10Z"
    - latency: 1.174679ms
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:02:10Z"
    - latency: 934.358µs
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:01:10Z"
    - latency: 832.642µs
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:00:10Z"
    - latency: 734.514µs
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T00:59:10Z"
    - latency: 1.312145ms
      message: 'network-check-target-ip-10-0-134-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T00:58:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T00:53:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-48-to-network-check-target-ip-10-0-140-130
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-48.ec2.internal
      uid: b20ecb34-e92c-42d2-9673-12e2b68cb76c
    resourceVersion: "31109"
    uid: 365dfca8-be7f-4524-9a5c-09cb72b68724
  spec:
    sourcePod: network-check-source-56d84b9f44-5h5b7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T01:00:10Z"
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.325348ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:07:10Z"
    - latency: 2.643952ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:06:10Z"
    - latency: 2.146194ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:05:10Z"
    - latency: 2.350145ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:04:10Z"
    - latency: 2.416265ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:03:10Z"
    - latency: 2.29724ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:02:10Z"
    - latency: 2.320349ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:01:10Z"
    - latency: 2.085952ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:00:10Z"
    - latency: 3.281402ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T00:59:10Z"
    - latency: 1.887116ms
      message: 'network-check-target-ip-10-0-140-130: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T00:58:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T00:53:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-48-to-network-check-target-ip-10-0-141-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-48.ec2.internal
      uid: b20ecb34-e92c-42d2-9673-12e2b68cb76c
    resourceVersion: "31110"
    uid: 6275a044-d432-47e6-ab0e-d7b024e1ee88
  spec:
    sourcePod: network-check-source-56d84b9f44-5h5b7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T01:00:10Z"
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.31617ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:07:10Z"
    - latency: 2.354394ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:06:10Z"
    - latency: 2.070231ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:05:10Z"
    - latency: 2.463543ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:04:10Z"
    - latency: 2.42217ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:03:10Z"
    - latency: 2.158821ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:02:10Z"
    - latency: 2.614348ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:01:10Z"
    - latency: 2.651862ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:00:10Z"
    - latency: 2.026804ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T00:59:10Z"
    - latency: 2.320591ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T00:58:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T00:53:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-48-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-48.ec2.internal
      uid: b20ecb34-e92c-42d2-9673-12e2b68cb76c
    resourceVersion: "29212"
    uid: 9cb2edef-cb0e-4d4f-b99a-bcd50e7ccd8c
  spec:
    sourcePod: network-check-source-56d84b9f44-5h5b7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T00:59:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 891.258µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:05:10Z"
    - latency: 2.234757ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:05:10Z"
    - latency: 1.214601ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:04:10Z"
    - latency: 1.945659ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:04:10Z"
    - latency: 914.032µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:03:10Z"
    - latency: 1.657698ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:03:10Z"
    - latency: 1.502497ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:02:10Z"
    - latency: 1.756097ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:02:10Z"
    - latency: 840.804µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T01:01:10Z"
    - latency: 1.758342ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T01:01:10Z"
kind: List
metadata:
  resourceVersion: ""