apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:44:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-9-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-9.ec2.internal
      uid: ff33d2e2-a58e-48e5-8552-257dc7614407
    resourceVersion: "19054"
    uid: 8a4a21be-bd8b-4ef3-830e-c13475ca3b0c
  spec:
    sourcePod: network-check-source-869dcfcdcd-zg76h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:51:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.195µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:58:46Z"
    - latency: 1.022087ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:57:46Z"
    - latency: 921.044µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:56:46Z"
    - latency: 1.345519ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:55:46Z"
    - latency: 1.101656ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:54:46Z"
    - latency: 904.038µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:53:46Z"
    - latency: 1.008119ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:52:46Z"
    - latency: 851.418µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:51:46Z"
    - latency: 1.04204ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:50:46Z"
    - latency: 1.106998ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:49:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:44:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-9-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-9.ec2.internal
      uid: ff33d2e2-a58e-48e5-8552-257dc7614407
    resourceVersion: "21161"
    uid: e9d9a0ae-e2d7-425c-b832-96262060bf4f
  spec:
    sourcePod: network-check-source-869dcfcdcd-zg76h
    targetEndpoint: a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:50:46Z"
      message: 'load-balancer-api-external: tcp connection to a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.002179ms
      message: 'load-balancer-api-external: tcp connection to a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:02:46Z"
    - latency: 6.461463ms
      message: 'load-balancer-api-external: resolved host name a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:02:46Z"
    - latency: 5.525623ms
      message: 'load-balancer-api-external: tcp connection to a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:01:46Z"
    - latency: 7.06635ms
      message: 'load-balancer-api-external: resolved host name a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:01:46Z"
    - latency: 5.14638ms
      message: 'load-balancer-api-external: tcp connection to a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:00:46Z"
    - latency: 5.935901ms
      message: 'load-balancer-api-external: resolved host name a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:00:46Z"
    - latency: 4.928408ms
      message: 'load-balancer-api-external: tcp connection to a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:59:46Z"
    - latency: 7.933437ms
      message: 'load-balancer-api-external: resolved host name a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:59:46Z"
    - latency: 5.267378ms
      message: 'load-balancer-api-external: tcp connection to a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:58:46Z"
    - latency: 6.587623ms
      message: 'load-balancer-api-external: resolved host name a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:58:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:44:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-9-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-9.ec2.internal
      uid: ff33d2e2-a58e-48e5-8552-257dc7614407
    resourceVersion: "21160"
    uid: bd606830-a314-4140-bc37-da345fba25bb
  spec:
    sourcePod: network-check-source-869dcfcdcd-zg76h
    targetEndpoint: a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:50:46Z"
      message: 'load-balancer-api-internal: tcp connection to a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.014188ms
      message: 'load-balancer-api-internal: tcp connection to a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:02:46Z"
    - latency: 6.42557ms
      message: 'load-balancer-api-internal: resolved host name a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:02:46Z"
    - latency: 5.54039ms
      message: 'load-balancer-api-internal: tcp connection to a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:01:46Z"
    - latency: 6.972115ms
      message: 'load-balancer-api-internal: resolved host name a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:01:46Z"
    - latency: 5.189335ms
      message: 'load-balancer-api-internal: tcp connection to a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:00:46Z"
    - latency: 5.903946ms
      message: 'load-balancer-api-internal: resolved host name a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:00:46Z"
    - latency: 4.913398ms
      message: 'load-balancer-api-internal: tcp connection to a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:59:46Z"
    - latency: 7.861295ms
      message: 'load-balancer-api-internal: resolved host name a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:59:46Z"
    - latency: 5.234866ms
      message: 'load-balancer-api-internal: tcp connection to a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:58:46Z"
    - latency: 6.497157ms
      message: 'load-balancer-api-internal: resolved host name a16c9c9e28aba40318d22847e1ba3681-fe44b540abce494d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:58:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:44:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-9-to-network-check-target-ip-10-0-129-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-9.ec2.internal
      uid: ff33d2e2-a58e-48e5-8552-257dc7614407
    resourceVersion: "19052"
    uid: 2177828c-1c10-4026-80f8-242a21d8fe15
  spec:
    sourcePod: network-check-source-869dcfcdcd-zg76h
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:51:46Z"
      message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.32608ms
      message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:58:46Z"
    - latency: 2.350175ms
      message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:57:46Z"
    - latency: 2.078234ms
      message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:56:46Z"
    - latency: 2.320218ms
      message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:55:46Z"
    - latency: 2.282534ms
      message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:54:46Z"
    - latency: 2.116614ms
      message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:53:46Z"
    - latency: 2.183366ms
      message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:52:46Z"
    - latency: 2.229376ms
      message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:51:46Z"
    - latency: 2.256697ms
      message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:50:46Z"
    - latency: 2.245871ms
      message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:49:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:44:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-9-to-network-check-target-ip-10-0-130-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-9.ec2.internal
      uid: ff33d2e2-a58e-48e5-8552-257dc7614407
    resourceVersion: "19051"
    uid: 03e7e3c2-dc52-428d-a564-b1d4d85aa2ff
  spec:
    sourcePod: network-check-source-869dcfcdcd-zg76h
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:51:46Z"
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.824µs
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:58:46Z"
    - latency: 910.269µs
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:57:46Z"
    - latency: 910.203µs
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:56:46Z"
    - latency: 733.231µs
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:55:46Z"
    - latency: 835.802µs
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:54:46Z"
    - latency: 882.474µs
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:53:46Z"
    - latency: 898.389µs
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:52:46Z"
    - latency: 1.509242ms
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:51:46Z"
    - latency: 864.795µs
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:50:46Z"
    - latency: 955.715µs
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:49:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:44:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-9-to-network-check-target-ip-10-0-134-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-9.ec2.internal
      uid: ff33d2e2-a58e-48e5-8552-257dc7614407
    resourceVersion: "19053"
    uid: a0fdd1d7-95bc-4fe8-95fb-da77f7b1e986
  spec:
    sourcePod: network-check-source-869dcfcdcd-zg76h
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:51:46Z"
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.451003ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:58:46Z"
    - latency: 2.205817ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:57:46Z"
    - latency: 2.341109ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:56:46Z"
    - latency: 2.54367ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:55:46Z"
    - latency: 2.30187ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:54:46Z"
    - latency: 2.241229ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:53:46Z"
    - latency: 2.389783ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:52:46Z"
    - latency: 2.285256ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:51:46Z"
    - latency: 2.230637ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:50:46Z"
    - latency: 2.531467ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:49:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:44:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-9-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-9.ec2.internal
      uid: ff33d2e2-a58e-48e5-8552-257dc7614407
    resourceVersion: "21159"
    uid: ca3c9395-0480-4f2b-904b-87caeb0cb3ec
  spec:
    sourcePod: network-check-source-869dcfcdcd-zg76h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:50:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.613µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:02:46Z"
    - latency: 1.821436ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:02:46Z"
    - latency: 942.902µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:01:46Z"
    - latency: 2.159253ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:01:46Z"
    - latency: 854.029µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:00:46Z"
    - latency: 1.684185ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:00:46Z"
    - latency: 904.477µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:59:46Z"
    - latency: 1.830936ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:59:46Z"
    - latency: 1.111639ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:58:46Z"
    - latency: 1.899635ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:58:46Z"
kind: List
metadata:
  resourceVersion: ""