apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T22:36:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-45-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-45.ec2.internal
      uid: 59219a46-5d25-4e0e-be04-27fd326c883d
    resourceVersion: "54889"
    uid: 873fd442-2028-4203-aca3-ca6fdcd31ef0
  spec:
    sourcePod: network-check-source-869dcfcdcd-wslf7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T22:43:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 993.13µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:11:26Z"
    - latency: 989.265µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:10:26Z"
    - latency: 931.68µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:09:26Z"
    - latency: 945.813µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:08:26Z"
    - latency: 1.312786ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:07:26Z"
    - latency: 3.387291ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:06:26Z"
    - latency: 1.123895ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:05:26Z"
    - latency: 913.04µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:04:26Z"
    - latency: 1.228358ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:03:26Z"
    - latency: 1.139585ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:02:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T22:36:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-45-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-45.ec2.internal
      uid: 59219a46-5d25-4e0e-be04-27fd326c883d
    resourceVersion: "55809"
    uid: 50e14539-55e4-4f1c-8be2-856abdc52304
  spec:
    sourcePod: network-check-source-869dcfcdcd-wslf7
    targetEndpoint: a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T22:42:26Z"
      message: 'load-balancer-api-external: tcp connection to a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.919804ms
      message: 'load-balancer-api-external: tcp connection to a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:12:26Z"
    - latency: 7.524193ms
      message: 'load-balancer-api-external: resolved host name a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:12:26Z"
    - latency: 4.648679ms
      message: 'load-balancer-api-external: tcp connection to a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:11:26Z"
    - latency: 7.311001ms
      message: 'load-balancer-api-external: resolved host name a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:11:26Z"
    - latency: 5.162493ms
      message: 'load-balancer-api-external: tcp connection to a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:10:26Z"
    - latency: 8.148496ms
      message: 'load-balancer-api-external: resolved host name a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:10:26Z"
    - latency: 3.546508ms
      message: 'load-balancer-api-external: tcp connection to a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:09:26Z"
    - latency: 6.843643ms
      message: 'load-balancer-api-external: resolved host name a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:09:26Z"
    - latency: 4.141504ms
      message: 'load-balancer-api-external: tcp connection to a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:08:26Z"
    - latency: 6.994279ms
      message: 'load-balancer-api-external: resolved host name a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:08:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T22:36:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-45-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-45.ec2.internal
      uid: 59219a46-5d25-4e0e-be04-27fd326c883d
    resourceVersion: "55808"
    uid: 196c4ed7-ab36-4c1c-bf39-e8a914ef9c6f
  spec:
    sourcePod: network-check-source-869dcfcdcd-wslf7
    targetEndpoint: a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T22:42:26Z"
      message: 'load-balancer-api-internal: tcp connection to a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.865203ms
      message: 'load-balancer-api-internal: tcp connection to a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:12:26Z"
    - latency: 7.485838ms
      message: 'load-balancer-api-internal: resolved host name a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:12:26Z"
    - latency: 4.673717ms
      message: 'load-balancer-api-internal: tcp connection to a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:11:26Z"
    - latency: 7.281241ms
      message: 'load-balancer-api-internal: resolved host name a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:11:26Z"
    - latency: 5.190364ms
      message: 'load-balancer-api-internal: tcp connection to a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:10:26Z"
    - latency: 8.040808ms
      message: 'load-balancer-api-internal: resolved host name a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:10:26Z"
    - latency: 3.565975ms
      message: 'load-balancer-api-internal: tcp connection to a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:09:26Z"
    - latency: 6.79864ms
      message: 'load-balancer-api-internal: resolved host name a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:09:26Z"
    - latency: 3.693287ms
      message: 'load-balancer-api-internal: tcp connection to a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:08:26Z"
    - latency: 6.812888ms
      message: 'load-balancer-api-internal: resolved host name a35ffbdb4d19644e58b44fc349eebd96-c9049f9575b08c7a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:08:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T22:36:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-45-to-network-check-target-ip-10-0-130-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-45.ec2.internal
      uid: 59219a46-5d25-4e0e-be04-27fd326c883d
    resourceVersion: "54888"
    uid: 8550885d-3b52-4383-a08d-24e6f4d47dab
  spec:
    sourcePod: network-check-source-869dcfcdcd-wslf7
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T22:43:26Z"
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.260571ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:11:26Z"
    - latency: 2.331497ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:10:26Z"
    - latency: 2.156419ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:09:26Z"
    - latency: 2.21835ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:08:26Z"
    - latency: 2.3406ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:07:26Z"
    - latency: 3.246716ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:06:26Z"
    - latency: 2.363728ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:05:26Z"
    - latency: 2.193814ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:04:26Z"
    - latency: 2.392888ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:03:26Z"
    - latency: 2.28726ms
      message: 'network-check-target-ip-10-0-130-194: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:02:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T22:36:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-45-to-network-check-target-ip-10-0-132-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-45.ec2.internal
      uid: 59219a46-5d25-4e0e-be04-27fd326c883d
    resourceVersion: "54886"
    uid: f6e838a0-c3be-4f73-9d1b-af3fcaf65a53
  spec:
    sourcePod: network-check-source-869dcfcdcd-wslf7
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T22:43:26Z"
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.010814ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:11:26Z"
    - latency: 1.199081ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:10:26Z"
    - latency: 1.293858ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:09:26Z"
    - latency: 1.07566ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:08:26Z"
    - latency: 1.045271ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:07:26Z"
    - latency: 3.912889ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:06:26Z"
    - latency: 996.349µs
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:05:26Z"
    - latency: 912.746µs
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:04:26Z"
    - latency: 1.459534ms
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:03:26Z"
    - latency: 918.3µs
      message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:02:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T22:36:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-45-to-network-check-target-ip-10-0-139-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-45.ec2.internal
      uid: 59219a46-5d25-4e0e-be04-27fd326c883d
    resourceVersion: "54887"
    uid: 0030f710-368c-4705-ba28-25834d1df491
  spec:
    sourcePod: network-check-source-869dcfcdcd-wslf7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T22:43:26Z"
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.992972ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:11:26Z"
    - latency: 2.078548ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:10:26Z"
    - latency: 1.909922ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:09:26Z"
    - latency: 2.105793ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:08:26Z"
    - latency: 2.143606ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:07:26Z"
    - latency: 2.6229ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:06:26Z"
    - latency: 2.072132ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:05:26Z"
    - latency: 1.751966ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:04:26Z"
    - latency: 2.029353ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:03:26Z"
    - latency: 2.247395ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:02:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T22:36:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-45-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-45.ec2.internal
      uid: 59219a46-5d25-4e0e-be04-27fd326c883d
    resourceVersion: "55807"
    uid: 392b738a-230b-49f3-b166-2205e525959b
  spec:
    sourcePod: network-check-source-869dcfcdcd-wslf7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T22:42:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.069751ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:12:26Z"
    - latency: 2.220597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:12:26Z"
    - latency: 1.24484ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:11:26Z"
    - latency: 2.067413ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:11:26Z"
    - latency: 844.947µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:10:26Z"
    - latency: 1.687068ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:10:26Z"
    - latency: 1.077653ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:09:26Z"
    - latency: 1.994661ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:09:26Z"
    - latency: 954.245µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T23:08:26Z"
    - latency: 1.787355ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T23:08:26Z"
kind: List
metadata:
  resourceVersion: ""