apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T18:02:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-141-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-141.ec2.internal
      uid: d7a00832-0f34-4cb4-b41c-d08850438083
    resourceVersion: "43212"
    uid: ef09830f-c952-469c-9df1-546d4dd3d2c6
  spec:
    sourcePod: network-check-source-7f44b6dd87-cptst
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T18:09:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.251µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:30:01Z"
    - latency: 1.299029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:29:01Z"
    - latency: 883.341µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:28:01Z"
    - latency: 1.154205ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:27:01Z"
    - latency: 892.218µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:26:01Z"
    - latency: 1.038516ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:25:01Z"
    - latency: 1.006702ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:24:01Z"
    - latency: 1.045234ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:23:01Z"
    - latency: 981.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:22:01Z"
    - latency: 1.007192ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:21:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T18:02:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-141-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-141.ec2.internal
      uid: d7a00832-0f34-4cb4-b41c-d08850438083
    resourceVersion: "45790"
    uid: 2c1adbf2-b958-4795-aa1b-85cf544f7b03
  spec:
    sourcePod: network-check-source-7f44b6dd87-cptst
    targetEndpoint: a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T18:08:01Z"
      message: 'load-balancer-api-external: tcp connection to a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 11.476234ms
      message: 'load-balancer-api-external: tcp connection to a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:32:01Z"
    - latency: 7.960334ms
      message: 'load-balancer-api-external: resolved host name a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:32:01Z"
    - latency: 4.343102ms
      message: 'load-balancer-api-external: tcp connection to a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:31:01Z"
    - latency: 8.124105ms
      message: 'load-balancer-api-external: resolved host name a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:31:01Z"
    - latency: 5.195902ms
      message: 'load-balancer-api-external: tcp connection to a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:30:01Z"
    - latency: 8.423155ms
      message: 'load-balancer-api-external: resolved host name a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:30:01Z"
    - latency: 4.438783ms
      message: 'load-balancer-api-external: tcp connection to a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:29:01Z"
    - latency: 8.046859ms
      message: 'load-balancer-api-external: resolved host name a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:29:01Z"
    - latency: 4.453078ms
      message: 'load-balancer-api-external: tcp connection to a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:28:01Z"
    - latency: 9.583359ms
      message: 'load-balancer-api-external: resolved host name a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:28:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T18:02:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-141-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-141.ec2.internal
      uid: d7a00832-0f34-4cb4-b41c-d08850438083
    resourceVersion: "45789"
    uid: 47ced183-5c90-4043-9fce-959686bd3192
  spec:
    sourcePod: network-check-source-7f44b6dd87-cptst
    targetEndpoint: a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T18:08:01Z"
      message: 'load-balancer-api-internal: tcp connection to a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.97418ms
      message: 'load-balancer-api-internal: tcp connection to a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:32:01Z"
    - latency: 7.925834ms
      message: 'load-balancer-api-internal: resolved host name a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:32:01Z"
    - latency: 5.155514ms
      message: 'load-balancer-api-internal: tcp connection to a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:31:01Z"
    - latency: 8.038276ms
      message: 'load-balancer-api-internal: resolved host name a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:31:01Z"
    - latency: 5.192588ms
      message: 'load-balancer-api-internal: tcp connection to a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:30:01Z"
    - latency: 8.467966ms
      message: 'load-balancer-api-internal: resolved host name a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:30:01Z"
    - latency: 4.576916ms
      message: 'load-balancer-api-internal: tcp connection to a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:29:01Z"
    - latency: 7.997255ms
      message: 'load-balancer-api-internal: resolved host name a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:29:01Z"
    - latency: 4.424977ms
      message: 'load-balancer-api-internal: tcp connection to a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:28:01Z"
    - latency: 9.479162ms
      message: 'load-balancer-api-internal: resolved host name a5c368b697c1f4c9786173e6b428fcaf-db481f3718e37bec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:28:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T18:02:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-141-to-network-check-target-ip-10-0-137-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-141.ec2.internal
      uid: d7a00832-0f34-4cb4-b41c-d08850438083
    resourceVersion: "43211"
    uid: f4618947-bb4f-4a1e-a588-1881d17d69b8
  spec:
    sourcePod: network-check-source-7f44b6dd87-cptst
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T18:09:01Z"
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.055306ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:30:01Z"
    - latency: 2.287545ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:29:01Z"
    - latency: 2.096084ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:28:01Z"
    - latency: 2.578532ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:27:01Z"
    - latency: 2.13301ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:26:01Z"
    - latency: 2.265118ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:25:01Z"
    - latency: 2.193598ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:24:01Z"
    - latency: 2.169392ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:23:01Z"
    - latency: 2.533071ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:22:01Z"
    - latency: 2.439883ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:21:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T18:02:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-141-to-network-check-target-ip-10-0-139-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-141.ec2.internal
      uid: d7a00832-0f34-4cb4-b41c-d08850438083
    resourceVersion: "43209"
    uid: 20293bfa-7a62-4fef-8619-81a7c8fc9b53
  spec:
    sourcePod: network-check-source-7f44b6dd87-cptst
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T18:09:01Z"
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 898.527µs
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:30:01Z"
    - latency: 1.335616ms
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:29:01Z"
    - latency: 928.141µs
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:28:01Z"
    - latency: 1.328477ms
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:27:01Z"
    - latency: 873.455µs
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:26:01Z"
    - latency: 692.393µs
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:25:01Z"
    - latency: 788.386µs
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:24:01Z"
    - latency: 874.345µs
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:23:01Z"
    - latency: 771.615µs
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:22:01Z"
    - latency: 998.028µs
      message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:21:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T18:02:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-141-to-network-check-target-ip-10-0-141-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-141.ec2.internal
      uid: d7a00832-0f34-4cb4-b41c-d08850438083
    resourceVersion: "43210"
    uid: 0df506a1-0803-4235-b15f-3d4c9877ec2e
  spec:
    sourcePod: network-check-source-7f44b6dd87-cptst
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T18:09:01Z"
      message: 'network-check-target-ip-10-0-141-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.452007ms
      message: 'network-check-target-ip-10-0-141-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:30:01Z"
    - latency: 2.264953ms
      message: 'network-check-target-ip-10-0-141-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:29:01Z"
    - latency: 2.489831ms
      message: 'network-check-target-ip-10-0-141-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:28:01Z"
    - latency: 2.463724ms
      message: 'network-check-target-ip-10-0-141-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:27:01Z"
    - latency: 2.318214ms
      message: 'network-check-target-ip-10-0-141-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:26:01Z"
    - latency: 2.154014ms
      message: 'network-check-target-ip-10-0-141-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:25:01Z"
    - latency: 2.393996ms
      message: 'network-check-target-ip-10-0-141-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:24:01Z"
    - latency: 1.966145ms
      message: 'network-check-target-ip-10-0-141-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:23:01Z"
    - latency: 2.166046ms
      message: 'network-check-target-ip-10-0-141-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:22:01Z"
    - latency: 2.356261ms
      message: 'network-check-target-ip-10-0-141-157: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:21:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-27T18:02:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-141-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-141.ec2.internal
      uid: d7a00832-0f34-4cb4-b41c-d08850438083
    resourceVersion: "45787"
    uid: 29dcf720-b7f2-441a-9369-49449abad8aa
  spec:
    sourcePod: network-check-source-7f44b6dd87-cptst
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-27T18:08:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 838.776µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:32:01Z"
    - latency: 1.776415ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:32:01Z"
    - latency: 818.766µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:31:01Z"
    - latency: 1.453788ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:31:01Z"
    - latency: 1.137071ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:30:01Z"
    - latency: 1.788538ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:30:01Z"
    - latency: 713.94µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:29:01Z"
    - latency: 1.624536ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:29:01Z"
    - latency: 650.392µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-27T18:28:01Z"
    - latency: 2.002872ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-27T18:28:01Z"
kind: List
metadata:
  resourceVersion: ""