apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:48:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-152-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-152.ec2.internal
      uid: 5729e419-839c-4f5f-9b68-5c2067f7f668
    resourceVersion: "32354"
    uid: 54977c67-0f2d-44eb-9abb-7a6fe858a0be
  spec:
    sourcePod: network-check-source-6f8b768455-96jtp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:55:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 769.284µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:33Z"
    - latency: 712.73µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:33Z"
    - latency: 895.81µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:33Z"
    - latency: 1.219427ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:33Z"
    - latency: 1.658371ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:33Z"
    - latency: 793.618µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:33Z"
    - latency: 1.09239ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:33Z"
    - latency: 1.088579ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:33Z"
    - latency: 1.160985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:33Z"
    - latency: 985.595µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:21:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:48:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-152-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-152.ec2.internal
      uid: 5729e419-839c-4f5f-9b68-5c2067f7f668
    resourceVersion: "32355"
    uid: 2270b3cd-94fb-4a35-a000-345e7af277a5
  spec:
    sourcePod: network-check-source-6f8b768455-96jtp
    targetEndpoint: ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:54:33Z"
      message: 'load-balancer-api-external: tcp connection to ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.266569ms
      message: 'load-balancer-api-external: tcp connection to ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:33Z"
    - latency: 6.267558ms
      message: 'load-balancer-api-external: resolved host name ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:30:33Z"
    - latency: 6.939625ms
      message: 'load-balancer-api-external: tcp connection to ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:33Z"
    - latency: 5.729997ms
      message: 'load-balancer-api-external: resolved host name ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:29:33Z"
    - latency: 4.92118ms
      message: 'load-balancer-api-external: tcp connection to ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:33Z"
    - latency: 6.637275ms
      message: 'load-balancer-api-external: resolved host name ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:28:33Z"
    - latency: 5.059429ms
      message: 'load-balancer-api-external: tcp connection to ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:33Z"
    - latency: 6.320453ms
      message: 'load-balancer-api-external: resolved host name ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:27:33Z"
    - latency: 4.565399ms
      message: 'load-balancer-api-external: tcp connection to ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:33Z"
    - latency: 8.503453ms
      message: 'load-balancer-api-external: resolved host name ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:26:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:48:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-152-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-152.ec2.internal
      uid: 5729e419-839c-4f5f-9b68-5c2067f7f668
    resourceVersion: "32356"
    uid: ce707cf2-80a6-487a-8f81-e72df693b0ef
  spec:
    sourcePod: network-check-source-6f8b768455-96jtp
    targetEndpoint: ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:54:33Z"
      message: 'load-balancer-api-internal: tcp connection to ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.46132ms
      message: 'load-balancer-api-internal: tcp connection to ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:33Z"
    - latency: 6.29786ms
      message: 'load-balancer-api-internal: resolved host name ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:30:33Z"
    - latency: 6.971797ms
      message: 'load-balancer-api-internal: tcp connection to ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:33Z"
    - latency: 5.819759ms
      message: 'load-balancer-api-internal: resolved host name ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:29:33Z"
    - latency: 4.997768ms
      message: 'load-balancer-api-internal: tcp connection to ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:33Z"
    - latency: 6.599436ms
      message: 'load-balancer-api-internal: resolved host name ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:28:33Z"
    - latency: 5.082607ms
      message: 'load-balancer-api-internal: tcp connection to ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:33Z"
    - latency: 6.285233ms
      message: 'load-balancer-api-internal: resolved host name ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:27:33Z"
    - latency: 4.572483ms
      message: 'load-balancer-api-internal: tcp connection to ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:33Z"
    - latency: 8.449531ms
      message: 'load-balancer-api-internal: resolved host name ade1d8b96f4144d60a9402dc7fce703a-fb1ed0bf3a199f22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:26:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:48:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-152-to-network-check-target-ip-10-0-129-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-152.ec2.internal
      uid: 5729e419-839c-4f5f-9b68-5c2067f7f668
    resourceVersion: "32350"
    uid: 39f05df5-c149-4bbc-8fe6-41d45539203a
  spec:
    sourcePod: network-check-source-6f8b768455-96jtp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:55:33Z"
      message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.341013ms
      message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:33Z"
    - latency: 796.754µs
      message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:33Z"
    - latency: 799.782µs
      message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:33Z"
    - latency: 1.572163ms
      message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:33Z"
    - latency: 1.200446ms
      message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:33Z"
    - latency: 1.015511ms
      message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:33Z"
    - latency: 688.993µs
      message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:33Z"
    - latency: 937.426µs
      message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:33Z"
    - latency: 990.837µs
      message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:33Z"
    - latency: 1.320973ms
      message: 'network-check-target-ip-10-0-129-152: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:21:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:48:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-152-to-network-check-target-ip-10-0-130-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-152.ec2.internal
      uid: 5729e419-839c-4f5f-9b68-5c2067f7f668
    resourceVersion: "32351"
    uid: f7839012-34c6-4f43-aa9f-0beeaafab7c8
  spec:
    sourcePod: network-check-source-6f8b768455-96jtp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:55:33Z"
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.717258ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:33Z"
    - latency: 2.079004ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:33Z"
    - latency: 1.679809ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:33Z"
    - latency: 1.840242ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:33Z"
    - latency: 1.982597ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:33Z"
    - latency: 1.980567ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:33Z"
    - latency: 1.423522ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:33Z"
    - latency: 1.906064ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:33Z"
    - latency: 1.72568ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:33Z"
    - latency: 1.764915ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:21:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:48:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-152-to-network-check-target-ip-10-0-138-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-152.ec2.internal
      uid: 5729e419-839c-4f5f-9b68-5c2067f7f668
    resourceVersion: "32352"
    uid: 51ef12b5-37e3-407b-9a64-67666a298cdc
  spec:
    sourcePod: network-check-source-6f8b768455-96jtp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:55:33Z"
      message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.12025ms
      message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:33Z"
    - latency: 2.000119ms
      message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:33Z"
    - latency: 1.879509ms
      message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:33Z"
    - latency: 2.244886ms
      message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:33Z"
    - latency: 2.23851ms
      message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:33Z"
    - latency: 1.925959ms
      message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:33Z"
    - latency: 2.030367ms
      message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:33Z"
    - latency: 2.099217ms
      message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:23:33Z"
    - latency: 2.101701ms
      message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:22:33Z"
    - latency: 2.124625ms
      message: 'network-check-target-ip-10-0-138-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:21:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:48:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-152-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-152.ec2.internal
      uid: 5729e419-839c-4f5f-9b68-5c2067f7f668
    resourceVersion: "32353"
    uid: b4608cdc-99df-4773-8c32-364017a5adb7
  spec:
    sourcePod: network-check-source-6f8b768455-96jtp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:54:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.658µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:33Z"
    - latency: 2.074717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:30:33Z"
    - latency: 877.991µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:33Z"
    - latency: 1.674489ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:29:33Z"
    - latency: 855.184µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:33Z"
    - latency: 2.011795ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:28:33Z"
    - latency: 802.134µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:33Z"
    - latency: 1.832265ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:27:33Z"
    - latency: 828.039µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:33Z"
    - latency: 1.927393ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:26:33Z"
kind: List
metadata:
  resourceVersion: ""