apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:14:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-191-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-191.ec2.internal
      uid: 87ac565a-44bb-4fea-9fa3-499db9dfc911
    resourceVersion: "68473"
    uid: 75ff0b6a-4dbe-4487-bd06-9759d1738fec
  spec:
    sourcePod: network-check-source-6f8b768455-dg8qh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:21: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.109249ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:49:26Z"
    - latency: 967.441µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:48:26Z"
    - latency: 1.193006ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:47:26Z"
    - latency: 1.062615ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:46:26Z"
    - latency: 1.282157ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:45:26Z"
    - latency: 966.155µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:44:26Z"
    - latency: 820.978µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:43:26Z"
    - latency: 1.316603ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:42:26Z"
    - latency: 991.29µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:41:26Z"
    - latency: 1.095168ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:40:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:14:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-191-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-191.ec2.internal
      uid: 87ac565a-44bb-4fea-9fa3-499db9dfc911
    resourceVersion: "69249"
    uid: f6c85603-79e7-447d-b213-4d1eaf8486bf
  spec:
    sourcePod: network-check-source-6f8b768455-dg8qh
    targetEndpoint: ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:20:26Z"
      message: 'load-balancer-api-external: tcp connection to ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.542827ms
      message: 'load-balancer-api-external: tcp connection to ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:50:26Z"
    - latency: 10.216091ms
      message: 'load-balancer-api-external: resolved host name ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:50:26Z"
    - latency: 5.175545ms
      message: 'load-balancer-api-external: tcp connection to ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:49:26Z"
    - latency: 8.979603ms
      message: 'load-balancer-api-external: resolved host name ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:49:26Z"
    - latency: 3.686973ms
      message: 'load-balancer-api-external: tcp connection to ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:48:26Z"
    - latency: 9.665198ms
      message: 'load-balancer-api-external: resolved host name ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:48:26Z"
    - latency: 4.503353ms
      message: 'load-balancer-api-external: tcp connection to ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:47:26Z"
    - latency: 8.279892ms
      message: 'load-balancer-api-external: resolved host name ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:47:26Z"
    - latency: 4.835873ms
      message: 'load-balancer-api-external: tcp connection to ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:46:26Z"
    - latency: 7.584765ms
      message: 'load-balancer-api-external: resolved host name ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:46:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:14:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-191-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-191.ec2.internal
      uid: 87ac565a-44bb-4fea-9fa3-499db9dfc911
    resourceVersion: "69250"
    uid: 7992a714-baf3-4c41-a93c-cead51f9ef05
  spec:
    sourcePod: network-check-source-6f8b768455-dg8qh
    targetEndpoint: ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:20:26Z"
      message: 'load-balancer-api-internal: tcp connection to ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.530769ms
      message: 'load-balancer-api-internal: tcp connection to ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:50:26Z"
    - latency: 10.154156ms
      message: 'load-balancer-api-internal: resolved host name ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:50:26Z"
    - latency: 5.183565ms
      message: 'load-balancer-api-internal: tcp connection to ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:49:26Z"
    - latency: 8.9123ms
      message: 'load-balancer-api-internal: resolved host name ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:49:26Z"
    - latency: 3.700728ms
      message: 'load-balancer-api-internal: tcp connection to ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:48:26Z"
    - latency: 9.631414ms
      message: 'load-balancer-api-internal: resolved host name ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:48:26Z"
    - latency: 4.511362ms
      message: 'load-balancer-api-internal: tcp connection to ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:47:26Z"
    - latency: 8.327535ms
      message: 'load-balancer-api-internal: resolved host name ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:47:26Z"
    - latency: 4.563192ms
      message: 'load-balancer-api-internal: tcp connection to ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:46:26Z"
    - latency: 7.636517ms
      message: 'load-balancer-api-internal: resolved host name ac21a0665ad1b41d4aed6fda5aa4c95a-ee6f9a0f287202af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:46:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:14:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-191-to-network-check-target-ip-10-0-129-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-191.ec2.internal
      uid: 87ac565a-44bb-4fea-9fa3-499db9dfc911
    resourceVersion: "68472"
    uid: 77bbcbcd-842b-4894-bfda-b723c6db64cc
  spec:
    sourcePod: network-check-source-6f8b768455-dg8qh
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:21:26Z"
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.103179ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:49:26Z"
    - latency: 1.907655ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:48:26Z"
    - latency: 1.947109ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:47:26Z"
    - latency: 2.001727ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:46:26Z"
    - latency: 2.290498ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:45:26Z"
    - latency: 2.362813ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:44:26Z"
    - latency: 2.069513ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:43:26Z"
    - latency: 2.391745ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:42:26Z"
    - latency: 2.052703ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:41:26Z"
    - latency: 2.04085ms
      message: 'network-check-target-ip-10-0-129-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:40:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:14:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-191-to-network-check-target-ip-10-0-139-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-191.ec2.internal
      uid: 87ac565a-44bb-4fea-9fa3-499db9dfc911
    resourceVersion: "68471"
    uid: 1aee3190-8dc4-436e-a4cd-5adbd75cd3a9
  spec:
    sourcePod: network-check-source-6f8b768455-dg8qh
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:21:26Z"
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.613963ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:49:26Z"
    - latency: 1.904094ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:48:26Z"
    - latency: 2.040164ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:47:26Z"
    - latency: 1.966452ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:46:26Z"
    - latency: 1.862208ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:45:26Z"
    - latency: 1.922457ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:44:26Z"
    - latency: 1.503492ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:43:26Z"
    - latency: 2.227899ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:42:26Z"
    - latency: 1.740126ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:41:26Z"
    - latency: 2.026521ms
      message: 'network-check-target-ip-10-0-139-184: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:40:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:14:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-191-to-network-check-target-ip-10-0-143-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-191.ec2.internal
      uid: 87ac565a-44bb-4fea-9fa3-499db9dfc911
    resourceVersion: "68470"
    uid: 1b11d64b-3d04-45b1-bbed-b97aa8343082
  spec:
    sourcePod: network-check-source-6f8b768455-dg8qh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:21:26Z"
      message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 856.789µs
      message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:49:26Z"
    - latency: 1.194618ms
      message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:48:26Z"
    - latency: 837.559µs
      message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:47:26Z"
    - latency: 880.565µs
      message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:46:26Z"
    - latency: 1.157717ms
      message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:45:26Z"
    - latency: 1.138827ms
      message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:44:26Z"
    - latency: 973.774µs
      message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:43:26Z"
    - latency: 967.109µs
      message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:42:26Z"
    - latency: 982.274µs
      message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:41:26Z"
    - latency: 812.598µs
      message: 'network-check-target-ip-10-0-143-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:40:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:14:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-191-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-191.ec2.internal
      uid: 87ac565a-44bb-4fea-9fa3-499db9dfc911
    resourceVersion: "69248"
    uid: cb804655-7a4b-4ca2-9bc9-f36fc29f04ec
  spec:
    sourcePod: network-check-source-6f8b768455-dg8qh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:20:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 846.906µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:50:26Z"
    - latency: 1.688011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:50:26Z"
    - latency: 818.756µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:49:26Z"
    - latency: 2.108686ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:49:26Z"
    - latency: 948.889µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:48:26Z"
    - latency: 1.944559ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:48:26Z"
    - latency: 978.335µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:47:26Z"
    - latency: 1.784471ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:47:26Z"
    - latency: 1.224534ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:46:26Z"
    - latency: 1.692182ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:46:26Z"
kind: List
metadata:
  resourceVersion: ""