apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:55:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-201-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-201.ec2.internal
      uid: 5c018c71-5a4c-4a14-b40f-ce12a0ff91f7
    resourceVersion: "67914"
    uid: b502172d-4bc1-4677-b0ee-5fe2f0d65fd5
  spec:
    sourcePod: network-check-source-6f8b768455-hjw6g
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T22:02:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 882.849µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:30:09Z"
    - latency: 1.077787ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:29:09Z"
    - latency: 868.796µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:28:09Z"
    - latency: 1.186584ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:27:09Z"
    - latency: 1.00042ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:26:09Z"
    - latency: 942.477µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:25:09Z"
    - latency: 1.102616ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:24:09Z"
    - latency: 1.144702ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:23:09Z"
    - latency: 940.237µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:22:09Z"
    - latency: 1.089892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:21:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:55:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-201-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-201.ec2.internal
      uid: 5c018c71-5a4c-4a14-b40f-ce12a0ff91f7
    resourceVersion: "68839"
    uid: 4b9f09c7-17b6-40ab-8675-22cdc7a373e9
  spec:
    sourcePod: network-check-source-6f8b768455-hjw6g
    targetEndpoint: aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T22:01:09Z"
      message: 'load-balancer-api-external: tcp connection to aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.194867ms
      message: 'load-balancer-api-external: tcp connection to aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:31:09Z"
    - latency: 8.979243ms
      message: 'load-balancer-api-external: resolved host name aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:31:09Z"
    - latency: 5.482462ms
      message: 'load-balancer-api-external: tcp connection to aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:30:09Z"
    - latency: 8.993607ms
      message: 'load-balancer-api-external: resolved host name aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:30:09Z"
    - latency: 5.088008ms
      message: 'load-balancer-api-external: tcp connection to aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:29:09Z"
    - latency: 8.041608ms
      message: 'load-balancer-api-external: resolved host name aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:29:09Z"
    - latency: 4.023939ms
      message: 'load-balancer-api-external: tcp connection to aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:28:09Z"
    - latency: 8.978976ms
      message: 'load-balancer-api-external: resolved host name aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:28:09Z"
    - latency: 4.858232ms
      message: 'load-balancer-api-external: tcp connection to aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:27:09Z"
    - latency: 9.18019ms
      message: 'load-balancer-api-external: resolved host name aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:27:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:55:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-201-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-201.ec2.internal
      uid: 5c018c71-5a4c-4a14-b40f-ce12a0ff91f7
    resourceVersion: "68838"
    uid: e786145b-de51-460c-9a13-e87b76f25c5d
  spec:
    sourcePod: network-check-source-6f8b768455-hjw6g
    targetEndpoint: aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T22:01:09Z"
      message: 'load-balancer-api-internal: tcp connection to aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.147773ms
      message: 'load-balancer-api-internal: tcp connection to aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:31:09Z"
    - latency: 8.999699ms
      message: 'load-balancer-api-internal: resolved host name aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:31:09Z"
    - latency: 5.489886ms
      message: 'load-balancer-api-internal: tcp connection to aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:30:09Z"
    - latency: 8.949313ms
      message: 'load-balancer-api-internal: resolved host name aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:30:09Z"
    - latency: 4.947222ms
      message: 'load-balancer-api-internal: tcp connection to aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:29:09Z"
    - latency: 8.078144ms
      message: 'load-balancer-api-internal: resolved host name aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:29:09Z"
    - latency: 4.477367ms
      message: 'load-balancer-api-internal: tcp connection to aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:28:09Z"
    - latency: 8.881747ms
      message: 'load-balancer-api-internal: resolved host name aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:28:09Z"
    - latency: 4.987043ms
      message: 'load-balancer-api-internal: tcp connection to aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:27:09Z"
    - latency: 9.204495ms
      message: 'load-balancer-api-internal: resolved host name aaf46adbe11e44d26981defdf807d774-dd471d4de6341351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:27:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:55:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-201-to-network-check-target-ip-10-0-128-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-201.ec2.internal
      uid: 5c018c71-5a4c-4a14-b40f-ce12a0ff91f7
    resourceVersion: "67911"
    uid: becb86ef-0429-4447-9713-ee9c20177869
  spec:
    sourcePod: network-check-source-6f8b768455-hjw6g
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T22:02:09Z"
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 816.335µs
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:30:09Z"
    - latency: 1.334149ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:29:09Z"
    - latency: 946.123µs
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:28:09Z"
    - latency: 994.673µs
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:27:09Z"
    - latency: 1.09463ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:26:09Z"
    - latency: 946.718µs
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:25:09Z"
    - latency: 1.320363ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:24:09Z"
    - latency: 1.406514ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:23:09Z"
    - latency: 999.434µs
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:22:09Z"
    - latency: 973.643µs
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:21:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:55:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-201-to-network-check-target-ip-10-0-139-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-201.ec2.internal
      uid: 5c018c71-5a4c-4a14-b40f-ce12a0ff91f7
    resourceVersion: "67912"
    uid: 28a1e01d-5819-4b8e-9996-2a5b1dab5a11
  spec:
    sourcePod: network-check-source-6f8b768455-hjw6g
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T22:02:09Z"
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.453092ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:30:09Z"
    - latency: 2.542991ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:29:09Z"
    - latency: 2.24434ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:28:09Z"
    - latency: 2.530944ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:27:09Z"
    - latency: 2.589927ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:26:09Z"
    - latency: 2.701351ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:25:09Z"
    - latency: 2.576392ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:24:09Z"
    - latency: 2.435195ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:23:09Z"
    - latency: 2.367236ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:22:09Z"
    - latency: 2.489218ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:21:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:55:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-201-to-network-check-target-ip-10-0-141-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-201.ec2.internal
      uid: 5c018c71-5a4c-4a14-b40f-ce12a0ff91f7
    resourceVersion: "67913"
    uid: 70bc7b62-190f-42f1-a9b3-09974926a7b0
  spec:
    sourcePod: network-check-source-6f8b768455-hjw6g
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T22:02:09Z"
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.30863ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:30:09Z"
    - latency: 2.620574ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:29:09Z"
    - latency: 2.17749ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:28:09Z"
    - latency: 2.301539ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:27:09Z"
    - latency: 2.504754ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:26:09Z"
    - latency: 2.757476ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:25:09Z"
    - latency: 2.568892ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:24:09Z"
    - latency: 2.39474ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:23:09Z"
    - latency: 2.201507ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:22:09Z"
    - latency: 2.579915ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:21:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T21:55:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-201-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-201.ec2.internal
      uid: 5c018c71-5a4c-4a14-b40f-ce12a0ff91f7
    resourceVersion: "68837"
    uid: 5e58f681-d026-4112-b0d0-acdb82479031
  spec:
    sourcePod: network-check-source-6f8b768455-hjw6g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T22:01:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 835.078µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:31:09Z"
    - latency: 1.734806ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:31:09Z"
    - latency: 917.069µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:30:09Z"
    - latency: 1.807492ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:30:09Z"
    - latency: 773.03µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:29:09Z"
    - latency: 1.597407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:29:09Z"
    - latency: 1.180633ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:28:09Z"
    - latency: 1.71959ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:28:09Z"
    - latency: 860.825µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T22:27:09Z"
    - latency: 1.765699ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T22:27:09Z"
kind: List
metadata:
  resourceVersion: ""