apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:01:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-121-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-121.ec2.internal
      uid: 22d6deef-6e96-4409-81d0-dc7da2ebd0aa
    resourceVersion: "45270"
    uid: 99270021-d7e0-4e25-91ef-d95617f7857b
  spec:
    sourcePod: network-check-source-8894fc9bd-w82ds
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:08:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.109752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:36:23Z"
    - latency: 1.099172ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:35:23Z"
    - latency: 856.824µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:34:23Z"
    - latency: 1.281398ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:33:23Z"
    - latency: 960.291µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:32:23Z"
    - latency: 1.221995ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:31:23Z"
    - latency: 1.251876ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:30:23Z"
    - latency: 1.159635ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:29:23Z"
    - latency: 1.041733ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:28:23Z"
    - latency: 1.132764ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:27:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:01:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-121-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-121.ec2.internal
      uid: 22d6deef-6e96-4409-81d0-dc7da2ebd0aa
    resourceVersion: "45807"
    uid: 15218081-6165-4f3f-bd79-0226064dbe3d
  spec:
    sourcePod: network-check-source-8894fc9bd-w82ds
    targetEndpoint: af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:07:23Z"
      message: 'load-balancer-api-external: tcp connection to af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.552904ms
      message: 'load-balancer-api-external: tcp connection to af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:37:23Z"
    - latency: 6.81643ms
      message: 'load-balancer-api-external: resolved host name af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:37:23Z"
    - latency: 5.922796ms
      message: 'load-balancer-api-external: tcp connection to af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:36:23Z"
    - latency: 7.215047ms
      message: 'load-balancer-api-external: resolved host name af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:36:23Z"
    - latency: 5.408589ms
      message: 'load-balancer-api-external: tcp connection to af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:35:23Z"
    - latency: 7.015612ms
      message: 'load-balancer-api-external: resolved host name af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:35:23Z"
    - latency: 4.233038ms
      message: 'load-balancer-api-external: tcp connection to af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:34:23Z"
    - latency: 7.062585ms
      message: 'load-balancer-api-external: resolved host name af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:34:23Z"
    - latency: 4.829124ms
      message: 'load-balancer-api-external: tcp connection to af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:33:23Z"
    - latency: 6.849306ms
      message: 'load-balancer-api-external: resolved host name af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:33:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:01:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-121-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-121.ec2.internal
      uid: 22d6deef-6e96-4409-81d0-dc7da2ebd0aa
    resourceVersion: "45808"
    uid: 24f0ad8e-1f68-446a-9dcd-2dbfe69d109f
  spec:
    sourcePod: network-check-source-8894fc9bd-w82ds
    targetEndpoint: af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:07:23Z"
      message: 'load-balancer-api-internal: tcp connection to af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.548189ms
      message: 'load-balancer-api-internal: tcp connection to af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:37:23Z"
    - latency: 6.776618ms
      message: 'load-balancer-api-internal: resolved host name af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:37:23Z"
    - latency: 12.254926ms
      message: 'load-balancer-api-internal: tcp connection to af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:36:23Z"
    - latency: 7.26708ms
      message: 'load-balancer-api-internal: resolved host name af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:36:23Z"
    - latency: 10.605129ms
      message: 'load-balancer-api-internal: tcp connection to af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:35:23Z"
    - latency: 7.05048ms
      message: 'load-balancer-api-internal: resolved host name af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:35:23Z"
    - latency: 5.993582ms
      message: 'load-balancer-api-internal: tcp connection to af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:34:23Z"
    - latency: 7.11298ms
      message: 'load-balancer-api-internal: resolved host name af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:34:23Z"
    - latency: 4.792305ms
      message: 'load-balancer-api-internal: tcp connection to af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:33:23Z"
    - latency: 6.886736ms
      message: 'load-balancer-api-internal: resolved host name af8162a87a2ac4e8c9d11777733a0cc3-dfad512a69b7234f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:33:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:01:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-121-to-network-check-target-ip-10-0-129-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-121.ec2.internal
      uid: 22d6deef-6e96-4409-81d0-dc7da2ebd0aa
    resourceVersion: "45268"
    uid: 09e9b76b-1300-4e4d-8355-e35ddc018268
  spec:
    sourcePod: network-check-source-8894fc9bd-w82ds
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:08:23Z"
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.028379ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:36:23Z"
    - latency: 2.073873ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:35:23Z"
    - latency: 1.698762ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:34:23Z"
    - latency: 1.942663ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:33:23Z"
    - latency: 1.934208ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:32:23Z"
    - latency: 1.905792ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:31:23Z"
    - latency: 1.87269ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:30:23Z"
    - latency: 1.981741ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:29:23Z"
    - latency: 1.69687ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:28:23Z"
    - latency: 1.746433ms
      message: 'network-check-target-ip-10-0-129-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:27:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:01:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-121-to-network-check-target-ip-10-0-130-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-121.ec2.internal
      uid: 22d6deef-6e96-4409-81d0-dc7da2ebd0aa
    resourceVersion: "45267"
    uid: d6b6548f-08e2-422c-bce6-b76362b68d17
  spec:
    sourcePod: network-check-source-8894fc9bd-w82ds
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:08:23Z"
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 933.704µs
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:36:23Z"
    - latency: 1.389392ms
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:35:23Z"
    - latency: 1.173462ms
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:34:23Z"
    - latency: 814.25µs
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:33:23Z"
    - latency: 1.47514ms
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:32:23Z"
    - latency: 1.040148ms
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:31:23Z"
    - latency: 848.327µs
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:30:23Z"
    - latency: 793.767µs
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:29:23Z"
    - latency: 831.501µs
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:28:23Z"
    - latency: 908.775µs
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:27:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:01:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-121-to-network-check-target-ip-10-0-134-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-121.ec2.internal
      uid: 22d6deef-6e96-4409-81d0-dc7da2ebd0aa
    resourceVersion: "45269"
    uid: 57dd45a7-af20-4629-963f-22f076d39708
  spec:
    sourcePod: network-check-source-8894fc9bd-w82ds
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:08:23Z"
      message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.372527ms
      message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:36:23Z"
    - latency: 2.321069ms
      message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:35:23Z"
    - latency: 2.285405ms
      message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:34:23Z"
    - latency: 2.334017ms
      message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:33:23Z"
    - latency: 2.21167ms
      message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:32:23Z"
    - latency: 2.002197ms
      message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:31:23Z"
    - latency: 2.332613ms
      message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:30:23Z"
    - latency: 2.045863ms
      message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:29:23Z"
    - latency: 2.151818ms
      message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:28:23Z"
    - latency: 2.208826ms
      message: 'network-check-target-ip-10-0-134-40: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:27:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:01:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-121-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-121.ec2.internal
      uid: 22d6deef-6e96-4409-81d0-dc7da2ebd0aa
    resourceVersion: "45806"
    uid: beddcf18-662d-41ed-a78d-fcac17dd32b6
  spec:
    sourcePod: network-check-source-8894fc9bd-w82ds
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:07:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.180305ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:37:23Z"
    - latency: 1.752653ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:37:23Z"
    - latency: 1.107408ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:36:23Z"
    - latency: 1.705443ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:36:23Z"
    - latency: 898.853µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:35:23Z"
    - latency: 1.793627ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:35:23Z"
    - latency: 905.693µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:34:23Z"
    - latency: 1.67444ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:34:23Z"
    - latency: 803.049µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:33:23Z"
    - latency: 1.644562ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:33:23Z"
kind: List
metadata:
  resourceVersion: ""