apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T00:06:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-136-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-136.ec2.internal
      uid: 278718cd-34d6-4a6b-9bd8-843e51a48b0d
    resourceVersion: "71330"
    uid: d8275be2-30a6-46a7-9c9e-3dc7849ba8b7
  spec:
    sourcePod: network-check-source-65bdbbff45-m222p
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T00:13:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.029555ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:55:18Z"
    - latency: 1.146349ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:54:18Z"
    - latency: 985.041µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:53:18Z"
    - latency: 877.293µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:52:18Z"
    - latency: 1.136541ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:51:18Z"
    - latency: 1.282571ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:50:18Z"
    - latency: 996.325µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:49:18Z"
    - latency: 1.184001ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:48:18Z"
    - latency: 1.228022ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:47:18Z"
    - latency: 1.146ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:46:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T00:06:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-136-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-136.ec2.internal
      uid: 278718cd-34d6-4a6b-9bd8-843e51a48b0d
    resourceVersion: "76691"
    uid: d56f6859-093c-49ef-8dad-2047ad989eb4
  spec:
    sourcePod: network-check-source-65bdbbff45-m222p
    targetEndpoint: ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T00:12:18Z"
      message: 'load-balancer-api-external: tcp connection to ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.629873ms
      message: 'load-balancer-api-external: tcp connection to ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T01:00:18Z"
    - latency: 14.260101ms
      message: 'load-balancer-api-external: resolved host name ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T01:00:18Z"
    - latency: 3.674271ms
      message: 'load-balancer-api-external: tcp connection to ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:59:18Z"
    - latency: 7.11457ms
      message: 'load-balancer-api-external: resolved host name ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T00:59:18Z"
    - latency: 6.557682ms
      message: 'load-balancer-api-external: tcp connection to ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:58:18Z"
    - latency: 7.426ms
      message: 'load-balancer-api-external: resolved host name ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T00:58:18Z"
    - latency: 3.765381ms
      message: 'load-balancer-api-external: tcp connection to ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:57:18Z"
    - latency: 7.614353ms
      message: 'load-balancer-api-external: resolved host name ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T00:57:18Z"
    - latency: 3.689999ms
      message: 'load-balancer-api-external: tcp connection to ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:56:18Z"
    - latency: 7.011925ms
      message: 'load-balancer-api-external: resolved host name ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T00:56:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T00:06:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-136-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-136.ec2.internal
      uid: 278718cd-34d6-4a6b-9bd8-843e51a48b0d
    resourceVersion: "76692"
    uid: 06b13618-717e-4d22-974c-4dcedf3bc3c0
  spec:
    sourcePod: network-check-source-65bdbbff45-m222p
    targetEndpoint: ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T00:12:18Z"
      message: 'load-balancer-api-internal: tcp connection to ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.620093ms
      message: 'load-balancer-api-internal: tcp connection to ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T01:00:18Z"
    - latency: 14.361361ms
      message: 'load-balancer-api-internal: resolved host name ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T01:00:18Z"
    - latency: 3.655716ms
      message: 'load-balancer-api-internal: tcp connection to ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:59:18Z"
    - latency: 7.156198ms
      message: 'load-balancer-api-internal: resolved host name ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T00:59:18Z"
    - latency: 6.588232ms
      message: 'load-balancer-api-internal: tcp connection to ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:58:18Z"
    - latency: 7.477934ms
      message: 'load-balancer-api-internal: resolved host name ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T00:58:18Z"
    - latency: 4.752093ms
      message: 'load-balancer-api-internal: tcp connection to ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:57:18Z"
    - latency: 7.643943ms
      message: 'load-balancer-api-internal: resolved host name ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T00:57:18Z"
    - latency: 3.852706ms
      message: 'load-balancer-api-internal: tcp connection to ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:56:18Z"
    - latency: 6.986598ms
      message: 'load-balancer-api-internal: resolved host name ad9b397797f8843bea27e8452039dd72-811f3ff92bf6d970.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T00:56:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T00:06:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-136-to-network-check-target-ip-10-0-138-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-136.ec2.internal
      uid: 278718cd-34d6-4a6b-9bd8-843e51a48b0d
    resourceVersion: "71328"
    uid: 8d46c47d-963d-4bec-97ec-3933b1cf99d6
  spec:
    sourcePod: network-check-source-65bdbbff45-m222p
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T00:13:18Z"
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.293839ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:55:18Z"
    - latency: 2.532982ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:54:18Z"
    - latency: 2.237557ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:53:18Z"
    - latency: 2.437706ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:52:18Z"
    - latency: 2.527255ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:51:18Z"
    - latency: 2.172047ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:50:18Z"
    - latency: 2.413603ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:49:18Z"
    - latency: 2.675286ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:48:18Z"
    - latency: 2.409357ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:47:18Z"
    - latency: 2.30542ms
      message: 'network-check-target-ip-10-0-138-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:46:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T00:06:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-136-to-network-check-target-ip-10-0-142-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-136.ec2.internal
      uid: 278718cd-34d6-4a6b-9bd8-843e51a48b0d
    resourceVersion: "71326"
    uid: 73387dcd-9514-4096-9d33-01146b79996e
  spec:
    sourcePod: network-check-source-65bdbbff45-m222p
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T00:13:18Z"
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.842µs
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:55:18Z"
    - latency: 1.929497ms
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:54:18Z"
    - latency: 925.067µs
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:53:18Z"
    - latency: 899.926µs
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:52:18Z"
    - latency: 939.086µs
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:51:18Z"
    - latency: 899.731µs
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:50:18Z"
    - latency: 1.583694ms
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:49:18Z"
    - latency: 1.024506ms
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:48:18Z"
    - latency: 1.32234ms
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:47:18Z"
    - latency: 1.734482ms
      message: 'network-check-target-ip-10-0-142-136: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:46:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T00:06:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-136-to-network-check-target-ip-10-0-143-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-136.ec2.internal
      uid: 278718cd-34d6-4a6b-9bd8-843e51a48b0d
    resourceVersion: "71329"
    uid: 957bfe98-55a9-4d1b-8e78-973aa1de9f98
  spec:
    sourcePod: network-check-source-65bdbbff45-m222p
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T00:13:18Z"
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.38108ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:55:18Z"
    - latency: 2.761009ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:54:18Z"
    - latency: 2.497854ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:53:18Z"
    - latency: 2.632662ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:52:18Z"
    - latency: 2.245547ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:51:18Z"
    - latency: 2.102549ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:50:18Z"
    - latency: 2.928948ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:49:18Z"
    - latency: 2.267885ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:48:18Z"
    - latency: 2.70219ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:47:18Z"
    - latency: 2.384055ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:46:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T00:06:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-136-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-136.ec2.internal
      uid: 278718cd-34d6-4a6b-9bd8-843e51a48b0d
    resourceVersion: "76690"
    uid: 53342101-e410-44fe-9d62-1d17f2700666
  spec:
    sourcePod: network-check-source-65bdbbff45-m222p
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T00:12:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.034892ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T01:00:18Z"
    - latency: 1.758319ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T01:00:18Z"
    - latency: 1.030545ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:59:18Z"
    - latency: 2.082244ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T00:59:18Z"
    - latency: 1.190808ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:58:18Z"
    - latency: 2.01325ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T00:58:18Z"
    - latency: 1.031837ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:57:18Z"
    - latency: 2.137577ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T00:57:18Z"
    - latency: 1.148436ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T00:56:18Z"
    - latency: 2.047626ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T00:56:18Z"
kind: List
metadata:
  resourceVersion: ""