apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T14:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-81-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-81.ec2.internal
      uid: 1013ea17-5337-48cf-a9ad-4c08caf432bf
    resourceVersion: "59963"
    uid: 2711c212-b236-4e03-b1e5-120b8fff6eec
  spec:
    sourcePod: network-check-source-7bc5b6bf85-td64b
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T15:02: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.014696ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:37:26Z"
    - latency: 1.212876ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:36:26Z"
    - latency: 1.249248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:35:26Z"
    - latency: 855.099µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:34:26Z"
    - latency: 1.576503ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:33:26Z"
    - latency: 1.365904ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:32:26Z"
    - latency: 1.07618ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:31:26Z"
    - latency: 1.292805ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:30:26Z"
    - latency: 1.440466ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:29:26Z"
    - latency: 1.121208ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T14:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-81-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-81.ec2.internal
      uid: 1013ea17-5337-48cf-a9ad-4c08caf432bf
    resourceVersion: "65822"
    uid: 649fcc68-0fb1-4ab7-9ade-0ed87c254585
  spec:
    sourcePod: network-check-source-7bc5b6bf85-td64b
    targetEndpoint: af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T15:01:26Z"
      message: 'load-balancer-api-external: tcp connection to af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.578825ms
      message: 'load-balancer-api-external: tcp connection to af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:43:26Z"
    - latency: 8.403497ms
      message: 'load-balancer-api-external: resolved host name af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:43:26Z"
    - latency: 4.267702ms
      message: 'load-balancer-api-external: tcp connection to af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:42:26Z"
    - latency: 7.053365ms
      message: 'load-balancer-api-external: resolved host name af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:42:26Z"
    - latency: 5.72003ms
      message: 'load-balancer-api-external: tcp connection to af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:41:26Z"
    - latency: 7.826171ms
      message: 'load-balancer-api-external: resolved host name af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:41:26Z"
    - latency: 5.262402ms
      message: 'load-balancer-api-external: tcp connection to af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:40:26Z"
    - latency: 9.975328ms
      message: 'load-balancer-api-external: resolved host name af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:40:26Z"
    - latency: 5.080331ms
      message: 'load-balancer-api-external: tcp connection to af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:39:26Z"
    - latency: 8.24846ms
      message: 'load-balancer-api-external: resolved host name af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:39:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T14:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-81-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-81.ec2.internal
      uid: 1013ea17-5337-48cf-a9ad-4c08caf432bf
    resourceVersion: "65823"
    uid: 612e6a0b-6959-4e74-b80e-7697f3cf3daf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-td64b
    targetEndpoint: af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T15:01:26Z"
      message: 'load-balancer-api-internal: tcp connection to af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.552109ms
      message: 'load-balancer-api-internal: tcp connection to af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:43:26Z"
    - latency: 8.439837ms
      message: 'load-balancer-api-internal: resolved host name af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:43:26Z"
    - latency: 4.301751ms
      message: 'load-balancer-api-internal: tcp connection to af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:42:26Z"
    - latency: 7.063727ms
      message: 'load-balancer-api-internal: resolved host name af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:42:26Z"
    - latency: 5.741772ms
      message: 'load-balancer-api-internal: tcp connection to af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:41:26Z"
    - latency: 7.273763ms
      message: 'load-balancer-api-internal: resolved host name af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:41:26Z"
    - latency: 5.448621ms
      message: 'load-balancer-api-internal: tcp connection to af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:40:26Z"
    - latency: 10.064718ms
      message: 'load-balancer-api-internal: resolved host name af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:40:26Z"
    - latency: 5.135314ms
      message: 'load-balancer-api-internal: tcp connection to af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:39:26Z"
    - latency: 8.215233ms
      message: 'load-balancer-api-internal: resolved host name af7eb6f73a300492cb6eb78cc00f1833-f86aa1f2a12e7b22.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:39:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T14:55:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-81-to-network-check-target-ip-10-0-138-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-81.ec2.internal
      uid: 1013ea17-5337-48cf-a9ad-4c08caf432bf
    resourceVersion: "59959"
    uid: adf74f94-b66a-47da-9e43-9407d96970a2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-td64b
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T15:02:26Z"
      message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 971.838µs
      message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:37:26Z"
    - latency: 885.142µs
      message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:36:26Z"
    - latency: 944.059µs
      message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:35:26Z"
    - latency: 863.221µs
      message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:34:26Z"
    - latency: 904.3µs
      message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:33:26Z"
    - latency: 1.575664ms
      message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:32:26Z"
    - latency: 944.677µs
      message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:31:26Z"
    - latency: 927.611µs
      message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:30:26Z"
    - latency: 1.637541ms
      message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:29:26Z"
    - latency: 870.593µs
      message: 'network-check-target-ip-10-0-138-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T14:55:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-81-to-network-check-target-ip-10-0-139-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-81.ec2.internal
      uid: 1013ea17-5337-48cf-a9ad-4c08caf432bf
    resourceVersion: "59960"
    uid: 71cb29d1-1933-4350-9195-40808cac8c53
  spec:
    sourcePod: network-check-source-7bc5b6bf85-td64b
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T15:02:26Z"
      message: 'network-check-target-ip-10-0-139-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.945296ms
      message: 'network-check-target-ip-10-0-139-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:37:26Z"
    - latency: 2.118156ms
      message: 'network-check-target-ip-10-0-139-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:36:26Z"
    - latency: 2.000795ms
      message: 'network-check-target-ip-10-0-139-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:35:26Z"
    - latency: 2.061045ms
      message: 'network-check-target-ip-10-0-139-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:34:26Z"
    - latency: 2.272088ms
      message: 'network-check-target-ip-10-0-139-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:33:26Z"
    - latency: 2.298666ms
      message: 'network-check-target-ip-10-0-139-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:32:26Z"
    - latency: 2.135785ms
      message: 'network-check-target-ip-10-0-139-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:31:26Z"
    - latency: 2.135596ms
      message: 'network-check-target-ip-10-0-139-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:30:26Z"
    - latency: 2.09671ms
      message: 'network-check-target-ip-10-0-139-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:29:26Z"
    - latency: 2.104822ms
      message: 'network-check-target-ip-10-0-139-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T14:55:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-81-to-network-check-target-ip-10-0-143-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-81.ec2.internal
      uid: 1013ea17-5337-48cf-a9ad-4c08caf432bf
    resourceVersion: "59961"
    uid: ff0bb15b-ac4f-44bd-8c08-209e56f25803
  spec:
    sourcePod: network-check-source-7bc5b6bf85-td64b
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T15:02:26Z"
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.186118ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:37:26Z"
    - latency: 2.222878ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:36:26Z"
    - latency: 2.081524ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:35:26Z"
    - latency: 1.96327ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:34:26Z"
    - latency: 1.939935ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:33:26Z"
    - latency: 2.267499ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:32:26Z"
    - latency: 2.380787ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:31:26Z"
    - latency: 2.282046ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:30:26Z"
    - latency: 2.316174ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:29:26Z"
    - latency: 2.425421ms
      message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:28:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T14:55:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-81-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-81.ec2.internal
      uid: 1013ea17-5337-48cf-a9ad-4c08caf432bf
    resourceVersion: "65821"
    uid: 793f873f-680b-4df6-af26-809720d1e24b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-td64b
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T15:01:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 877.374µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:43:26Z"
    - latency: 1.756837ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:43:26Z"
    - latency: 835.588µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:42:26Z"
    - latency: 1.92303ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:42:26Z"
    - latency: 925.498µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:41:26Z"
    - latency: 2.067136ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:41:26Z"
    - latency: 762.019µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:40:26Z"
    - latency: 1.803999ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:40:26Z"
    - latency: 1.226243ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T15:39:26Z"
    - latency: 2.060625ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T15:39:26Z"
kind: List
metadata:
  resourceVersion: ""