apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T00:00:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-216-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-216.ec2.internal
      uid: 62df0a1e-7086-4926-b7b7-59056a4ad204
    resourceVersion: "61083"
    uid: a598ebcd-6672-45fb-8c4c-72cd85a4c253
  spec:
    sourcePod: network-check-source-869dcfcdcd-9rspc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T00:07:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.091341ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:42:26Z"
    - latency: 894.323µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:41:26Z"
    - latency: 904.329µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:40:26Z"
    - latency: 914.599µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:39:26Z"
    - latency: 1.043666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:38:26Z"
    - latency: 1.604739ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:37:26Z"
    - latency: 1.060928ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:36:26Z"
    - latency: 1.128263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:35:26Z"
    - latency: 1.685748ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:34:26Z"
    - latency: 1.619308ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:33:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T00:00:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-216-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-216.ec2.internal
      uid: 62df0a1e-7086-4926-b7b7-59056a4ad204
    resourceVersion: "61084"
    uid: 49ceac94-74f1-4f74-b878-db1b9495d3d2
  spec:
    sourcePod: network-check-source-869dcfcdcd-9rspc
    targetEndpoint: ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T00:06:26Z"
      message: 'load-balancer-api-external: tcp connection to ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.395372ms
      message: 'load-balancer-api-external: tcp connection to ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:42:26Z"
    - latency: 9.701771ms
      message: 'load-balancer-api-external: resolved host name ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:42:26Z"
    - latency: 3.544383ms
      message: 'load-balancer-api-external: tcp connection to ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:41:26Z"
    - latency: 7.758562ms
      message: 'load-balancer-api-external: resolved host name ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:41:26Z"
    - latency: 4.695943ms
      message: 'load-balancer-api-external: tcp connection to ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:40:26Z"
    - latency: 11.889272ms
      message: 'load-balancer-api-external: resolved host name ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:40:26Z"
    - latency: 4.219345ms
      message: 'load-balancer-api-external: tcp connection to ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:39:26Z"
    - latency: 10.970982ms
      message: 'load-balancer-api-external: resolved host name ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:39:26Z"
    - latency: 3.414344ms
      message: 'load-balancer-api-external: tcp connection to ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:38:26Z"
    - latency: 9.304492ms
      message: 'load-balancer-api-external: resolved host name ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:38:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T00:00:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-216-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-216.ec2.internal
      uid: 62df0a1e-7086-4926-b7b7-59056a4ad204
    resourceVersion: "61085"
    uid: d4873385-8be5-4f3b-a00f-1a775cffd2af
  spec:
    sourcePod: network-check-source-869dcfcdcd-9rspc
    targetEndpoint: ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T00:06:26Z"
      message: 'load-balancer-api-internal: tcp connection to ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.012437ms
      message: 'load-balancer-api-internal: tcp connection to ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:42:26Z"
    - latency: 9.762092ms
      message: 'load-balancer-api-internal: resolved host name ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:42:26Z"
    - latency: 5.066434ms
      message: 'load-balancer-api-internal: tcp connection to ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:41:26Z"
    - latency: 7.690225ms
      message: 'load-balancer-api-internal: resolved host name ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:41:26Z"
    - latency: 4.439111ms
      message: 'load-balancer-api-internal: tcp connection to ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:40:26Z"
    - latency: 11.975142ms
      message: 'load-balancer-api-internal: resolved host name ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:40:26Z"
    - latency: 4.183114ms
      message: 'load-balancer-api-internal: tcp connection to ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:39:26Z"
    - latency: 11.045749ms
      message: 'load-balancer-api-internal: resolved host name ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:39:26Z"
    - latency: 3.336721ms
      message: 'load-balancer-api-internal: tcp connection to ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:38:26Z"
    - latency: 9.390114ms
      message: 'load-balancer-api-internal: resolved host name ac7acd06757d5437c98b24c9c43d2f67-b8c758b73e8d64ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:38:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T00:00:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-216-to-network-check-target-ip-10-0-132-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-216.ec2.internal
      uid: 62df0a1e-7086-4926-b7b7-59056a4ad204
    resourceVersion: "61079"
    uid: 9846a98d-768a-4b17-958b-2f404cc42123
  spec:
    sourcePod: network-check-source-869dcfcdcd-9rspc
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T00:07:26Z"
      message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.625298ms
      message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:42:26Z"
    - latency: 2.469908ms
      message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:41:26Z"
    - latency: 2.403211ms
      message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:40:26Z"
    - latency: 2.083651ms
      message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:39:26Z"
    - latency: 2.423423ms
      message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:38:26Z"
    - latency: 2.763116ms
      message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:37:26Z"
    - latency: 2.428663ms
      message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:36:26Z"
    - latency: 2.595414ms
      message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:35:26Z"
    - latency: 2.306748ms
      message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:34:26Z"
    - latency: 2.032349ms
      message: 'network-check-target-ip-10-0-132-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:33:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T00:00:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-216-to-network-check-target-ip-10-0-134-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-216.ec2.internal
      uid: 62df0a1e-7086-4926-b7b7-59056a4ad204
    resourceVersion: "61080"
    uid: 483d3987-ba1c-4eea-adb8-ac2f6024baa1
  spec:
    sourcePod: network-check-source-869dcfcdcd-9rspc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T00:07:26Z"
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.85996ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:42:26Z"
    - latency: 1.015761ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:41:26Z"
    - latency: 1.47561ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:40:26Z"
    - latency: 2.921314ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:39:26Z"
    - latency: 1.675785ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:38:26Z"
    - latency: 974.266µs
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:37:26Z"
    - latency: 1.0645ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:36:26Z"
    - latency: 1.632334ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:35:26Z"
    - latency: 937.596µs
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:34:26Z"
    - latency: 833.55µs
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:33:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T00:00:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-216-to-network-check-target-ip-10-0-142-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-216.ec2.internal
      uid: 62df0a1e-7086-4926-b7b7-59056a4ad204
    resourceVersion: "61081"
    uid: 75ce9c89-a538-4626-a101-8d9bce73bd9b
  spec:
    sourcePod: network-check-source-869dcfcdcd-9rspc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T00:07:26Z"
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.192269ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:42:26Z"
    - latency: 2.371335ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:41:26Z"
    - latency: 2.550494ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:40:26Z"
    - latency: 2.604686ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:39:26Z"
    - latency: 2.277946ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:38:26Z"
    - latency: 2.306887ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:37:26Z"
    - latency: 2.405821ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:36:26Z"
    - latency: 2.585532ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:35:26Z"
    - latency: 2.330841ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:34:26Z"
    - latency: 2.170681ms
      message: 'network-check-target-ip-10-0-142-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:33:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T00:00:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-216-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-216.ec2.internal
      uid: 62df0a1e-7086-4926-b7b7-59056a4ad204
    resourceVersion: "61082"
    uid: 8bb33810-f83d-4fa6-9a94-e00df4e2938a
  spec:
    sourcePod: network-check-source-869dcfcdcd-9rspc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T00:06:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.714µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:42:26Z"
    - latency: 1.955452ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:42:26Z"
    - latency: 1.16327ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:41:26Z"
    - latency: 2.393414ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:41:26Z"
    - latency: 872.038µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:40:26Z"
    - latency: 2.062577ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:40:26Z"
    - latency: 912.989µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:39:26Z"
    - latency: 2.946728ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:39:26Z"
    - latency: 910.607µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T00:38:26Z"
    - latency: 1.948966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T00:38:26Z"
kind: List
metadata:
  resourceVersion: ""