apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:09:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-89-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-89.ec2.internal
      uid: b53783ea-29a5-4ef2-a1e3-660def13acab
    resourceVersion: "33379"
    uid: 555e89d9-56d0-48c4-97c2-ee414e0001e1
  spec:
    sourcePod: network-check-source-7f44b6dd87-xgtzm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:17:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.394269ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:52:00Z"
    - latency: 987.329µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:51:00Z"
    - latency: 794.861µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:50:00Z"
    - latency: 1.070062ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:49:00Z"
    - latency: 1.034307ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:48:00Z"
    - latency: 1.172869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:47:00Z"
    - latency: 1.096591ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:46:00Z"
    - latency: 1.158867ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:45:00Z"
    - latency: 1.409327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:44:00Z"
    - latency: 1.034595ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:43:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:09:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-89-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-89.ec2.internal
      uid: b53783ea-29a5-4ef2-a1e3-660def13acab
    resourceVersion: "33381"
    uid: c729a033-de05-479e-b99a-11e58368d7cf
  spec:
    sourcePod: network-check-source-7f44b6dd87-xgtzm
    targetEndpoint: a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:16:00Z"
      message: 'load-balancer-api-external: tcp connection to a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.108973ms
      message: 'load-balancer-api-external: tcp connection to a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:52:00Z"
    - latency: 6.188407ms
      message: 'load-balancer-api-external: resolved host name a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:52:00Z"
    - latency: 4.44233ms
      message: 'load-balancer-api-external: tcp connection to a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:51:00Z"
    - latency: 6.158353ms
      message: 'load-balancer-api-external: resolved host name a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:51:00Z"
    - latency: 6.207015ms
      message: 'load-balancer-api-external: tcp connection to a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:50:00Z"
    - latency: 7.07485ms
      message: 'load-balancer-api-external: resolved host name a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:50:00Z"
    - latency: 5.020947ms
      message: 'load-balancer-api-external: tcp connection to a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:49:00Z"
    - latency: 6.037641ms
      message: 'load-balancer-api-external: resolved host name a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:49:00Z"
    - latency: 5.031311ms
      message: 'load-balancer-api-external: tcp connection to a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:48:00Z"
    - latency: 8.491678ms
      message: 'load-balancer-api-external: resolved host name a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:48:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:09:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-89-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-89.ec2.internal
      uid: b53783ea-29a5-4ef2-a1e3-660def13acab
    resourceVersion: "33380"
    uid: 14876398-4df0-4fce-b415-7a382d5e939d
  spec:
    sourcePod: network-check-source-7f44b6dd87-xgtzm
    targetEndpoint: a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:16:00Z"
      message: 'load-balancer-api-internal: tcp connection to a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.099251ms
      message: 'load-balancer-api-internal: tcp connection to a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:52:00Z"
    - latency: 6.238043ms
      message: 'load-balancer-api-internal: resolved host name a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:52:00Z"
    - latency: 4.494005ms
      message: 'load-balancer-api-internal: tcp connection to a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:51:00Z"
    - latency: 6.125196ms
      message: 'load-balancer-api-internal: resolved host name a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:51:00Z"
    - latency: 6.446839ms
      message: 'load-balancer-api-internal: tcp connection to a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:50:00Z"
    - latency: 7.013096ms
      message: 'load-balancer-api-internal: resolved host name a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:50:00Z"
    - latency: 4.108231ms
      message: 'load-balancer-api-internal: tcp connection to a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:49:00Z"
    - latency: 6.070013ms
      message: 'load-balancer-api-internal: resolved host name a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:49:00Z"
    - latency: 5.005125ms
      message: 'load-balancer-api-internal: tcp connection to a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:48:00Z"
    - latency: 8.460061ms
      message: 'load-balancer-api-internal: resolved host name a384bc7ba92aa464d8278e9e4e81c3ca-6c0ad3115e14a8e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:48:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:09:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-89-to-network-check-target-ip-10-0-129-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-89.ec2.internal
      uid: b53783ea-29a5-4ef2-a1e3-660def13acab
    resourceVersion: "33375"
    uid: 67974b4f-4f48-4be5-996c-4458d91af378
  spec:
    sourcePod: network-check-source-7f44b6dd87-xgtzm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:17:00Z"
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.450748ms
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:52:00Z"
    - latency: 952.475µs
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:51:00Z"
    - latency: 718.138µs
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:50:00Z"
    - latency: 906.821µs
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:49:00Z"
    - latency: 974.945µs
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:48:00Z"
    - latency: 1.356672ms
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:47:00Z"
    - latency: 855.06µs
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:46:00Z"
    - latency: 1.336207ms
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:45:00Z"
    - latency: 874.597µs
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:44:00Z"
    - latency: 812.678µs
      message: 'network-check-target-ip-10-0-129-89: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:43:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:09:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-89-to-network-check-target-ip-10-0-131-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-89.ec2.internal
      uid: b53783ea-29a5-4ef2-a1e3-660def13acab
    resourceVersion: "33377"
    uid: 567b6664-4ec9-4aa8-83f4-c87ff5dad8b0
  spec:
    sourcePod: network-check-source-7f44b6dd87-xgtzm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:17:00Z"
      message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.251486ms
      message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:52:00Z"
    - latency: 1.801131ms
      message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:51:00Z"
    - latency: 2.052493ms
      message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:50:00Z"
    - latency: 2.042727ms
      message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:49:00Z"
    - latency: 1.922445ms
      message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:48:00Z"
    - latency: 1.852274ms
      message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:47:00Z"
    - latency: 2.447586ms
      message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:46:00Z"
    - latency: 2.163043ms
      message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:45:00Z"
    - latency: 1.865107ms
      message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:44:00Z"
    - latency: 2.142642ms
      message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:43:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:09:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-89-to-network-check-target-ip-10-0-137-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-89.ec2.internal
      uid: b53783ea-29a5-4ef2-a1e3-660def13acab
    resourceVersion: "33376"
    uid: 4238d260-6c65-42bd-9985-01f1f2522eca
  spec:
    sourcePod: network-check-source-7f44b6dd87-xgtzm
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:17:00Z"
      message: 'network-check-target-ip-10-0-137-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.962297ms
      message: 'network-check-target-ip-10-0-137-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:52:00Z"
    - latency: 1.939262ms
      message: 'network-check-target-ip-10-0-137-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:51:00Z"
    - latency: 2.094306ms
      message: 'network-check-target-ip-10-0-137-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:50:00Z"
    - latency: 2.269931ms
      message: 'network-check-target-ip-10-0-137-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:49:00Z"
    - latency: 2.159916ms
      message: 'network-check-target-ip-10-0-137-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:48:00Z"
    - latency: 1.74179ms
      message: 'network-check-target-ip-10-0-137-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:47:00Z"
    - latency: 2.4948ms
      message: 'network-check-target-ip-10-0-137-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:46:00Z"
    - latency: 2.210001ms
      message: 'network-check-target-ip-10-0-137-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:45:00Z"
    - latency: 1.970322ms
      message: 'network-check-target-ip-10-0-137-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:44:00Z"
    - latency: 1.877236ms
      message: 'network-check-target-ip-10-0-137-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:43:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T16:09:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-89-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-89.ec2.internal
      uid: b53783ea-29a5-4ef2-a1e3-660def13acab
    resourceVersion: "33378"
    uid: b02434be-6563-4485-a2db-c9062ed2b17d
  spec:
    sourcePod: network-check-source-7f44b6dd87-xgtzm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T16:16:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.002631ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:52:00Z"
    - latency: 1.843986ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:52:00Z"
    - latency: 791.944µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:51:00Z"
    - latency: 1.897119ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:51:00Z"
    - latency: 968.037µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:50:00Z"
    - latency: 1.697256ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:50:00Z"
    - latency: 860.063µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:49:00Z"
    - latency: 1.599359ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:49:00Z"
    - latency: 1.026206ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T16:48:00Z"
    - latency: 1.899351ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T16:48:00Z"
kind: List
metadata:
  resourceVersion: ""