apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:04:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-233-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-233.ec2.internal
      uid: 623769d4-e9d2-40ca-b88b-b6254e6f92be
    resourceVersion: "54135"
    uid: ae2610d1-4fe2-4fa9-8d7e-a2afb32dd1a3
  spec:
    sourcePod: network-check-source-989f8b8dc-rpzmw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:11:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.33392ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:39:10Z"
    - latency: 1.106068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:38:10Z"
    - latency: 780.146µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:37:10Z"
    - latency: 1.058873ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:36:10Z"
    - latency: 1.398671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:35:10Z"
    - latency: 1.207674ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:34:10Z"
    - latency: 1.165403ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:33:10Z"
    - latency: 1.121837ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:32:10Z"
    - latency: 1.068826ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:31:10Z"
    - latency: 864.424µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:30:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:04:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-233-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-233.ec2.internal
      uid: 623769d4-e9d2-40ca-b88b-b6254e6f92be
    resourceVersion: "55157"
    uid: 0656872f-83f6-4d4e-8a2d-33a95d49c78c
  spec:
    sourcePod: network-check-source-989f8b8dc-rpzmw
    targetEndpoint: ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:10:10Z"
      message: 'load-balancer-api-external: tcp connection to ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.979041ms
      message: 'load-balancer-api-external: tcp connection to ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:40:10Z"
    - latency: 8.439481ms
      message: 'load-balancer-api-external: resolved host name ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:40:10Z"
    - latency: 4.716925ms
      message: 'load-balancer-api-external: tcp connection to ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:39:10Z"
    - latency: 8.707275ms
      message: 'load-balancer-api-external: resolved host name ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:39:10Z"
    - latency: 3.853211ms
      message: 'load-balancer-api-external: tcp connection to ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:38:10Z"
    - latency: 10.352632ms
      message: 'load-balancer-api-external: resolved host name ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:38:10Z"
    - latency: 4.444415ms
      message: 'load-balancer-api-external: tcp connection to ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:37:10Z"
    - latency: 12.312867ms
      message: 'load-balancer-api-external: resolved host name ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:37:10Z"
    - latency: 5.770294ms
      message: 'load-balancer-api-external: tcp connection to ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:36:10Z"
    - latency: 7.966602ms
      message: 'load-balancer-api-external: resolved host name ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:36:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:04:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-233-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-233.ec2.internal
      uid: 623769d4-e9d2-40ca-b88b-b6254e6f92be
    resourceVersion: "55156"
    uid: cc66bf4f-2af6-4831-b7f9-6620f09203f6
  spec:
    sourcePod: network-check-source-989f8b8dc-rpzmw
    targetEndpoint: ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:10:10Z"
      message: 'load-balancer-api-internal: tcp connection to ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.81035ms
      message: 'load-balancer-api-internal: tcp connection to ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:40:10Z"
    - latency: 8.462409ms
      message: 'load-balancer-api-internal: resolved host name ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:40:10Z"
    - latency: 4.572864ms
      message: 'load-balancer-api-internal: tcp connection to ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:39:10Z"
    - latency: 8.605298ms
      message: 'load-balancer-api-internal: resolved host name ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:39:10Z"
    - latency: 3.853295ms
      message: 'load-balancer-api-internal: tcp connection to ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:38:10Z"
    - latency: 10.32127ms
      message: 'load-balancer-api-internal: resolved host name ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:38:10Z"
    - latency: 4.276953ms
      message: 'load-balancer-api-internal: tcp connection to ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:37:10Z"
    - latency: 12.189644ms
      message: 'load-balancer-api-internal: resolved host name ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:37:10Z"
    - latency: 5.459149ms
      message: 'load-balancer-api-internal: tcp connection to ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:36:10Z"
    - latency: 8.047486ms
      message: 'load-balancer-api-internal: resolved host name ae96a7a7ba1be49f188e01fec672ecf9-72769ed73517fd19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:36:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:04:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-233-to-network-check-target-ip-10-0-138-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-233.ec2.internal
      uid: 623769d4-e9d2-40ca-b88b-b6254e6f92be
    resourceVersion: "54132"
    uid: 10a4f374-926a-4928-b94d-989e6b6addae
  spec:
    sourcePod: network-check-source-989f8b8dc-rpzmw
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:11:10Z"
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.521778ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:39:10Z"
    - latency: 1.537081ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:38:10Z"
    - latency: 963.711µs
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:37:10Z"
    - latency: 1.042236ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:36:10Z"
    - latency: 1.74042ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:35:10Z"
    - latency: 919.533µs
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:34:10Z"
    - latency: 967.328µs
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:33:10Z"
    - latency: 1.23592ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:32:10Z"
    - latency: 1.32106ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:31:10Z"
    - latency: 1.117699ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:30:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:04:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-233-to-network-check-target-ip-10-0-141-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-233.ec2.internal
      uid: 623769d4-e9d2-40ca-b88b-b6254e6f92be
    resourceVersion: "54133"
    uid: 52a28eaa-6b39-4f1f-9de5-9fde62451260
  spec:
    sourcePod: network-check-source-989f8b8dc-rpzmw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:11:10Z"
      message: 'network-check-target-ip-10-0-141-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.215039ms
      message: 'network-check-target-ip-10-0-141-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:39:10Z"
    - latency: 2.381742ms
      message: 'network-check-target-ip-10-0-141-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:38:10Z"
    - latency: 1.857184ms
      message: 'network-check-target-ip-10-0-141-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:37:10Z"
    - latency: 2.133806ms
      message: 'network-check-target-ip-10-0-141-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:36:10Z"
    - latency: 2.408261ms
      message: 'network-check-target-ip-10-0-141-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:35:10Z"
    - latency: 2.142096ms
      message: 'network-check-target-ip-10-0-141-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:34:10Z"
    - latency: 2.404116ms
      message: 'network-check-target-ip-10-0-141-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:33:10Z"
    - latency: 2.437917ms
      message: 'network-check-target-ip-10-0-141-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:32:10Z"
    - latency: 2.115736ms
      message: 'network-check-target-ip-10-0-141-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:31:10Z"
    - latency: 2.381417ms
      message: 'network-check-target-ip-10-0-141-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:30:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:04:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-233-to-network-check-target-ip-10-0-142-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-233.ec2.internal
      uid: 623769d4-e9d2-40ca-b88b-b6254e6f92be
    resourceVersion: "54134"
    uid: c2f42d0a-5c25-4906-8ae4-f708297d367f
  spec:
    sourcePod: network-check-source-989f8b8dc-rpzmw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:11:10Z"
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.989066ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:39:10Z"
    - latency: 2.176298ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:38:10Z"
    - latency: 1.969476ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:37:10Z"
    - latency: 1.919209ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:36:10Z"
    - latency: 2.071943ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:35:10Z"
    - latency: 1.77935ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:34:10Z"
    - latency: 2.112841ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:33:10Z"
    - latency: 2.113067ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:32:10Z"
    - latency: 2.014399ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:31:10Z"
    - latency: 1.825765ms
      message: 'network-check-target-ip-10-0-142-14: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:30:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T15:04:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-233-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-233.ec2.internal
      uid: 623769d4-e9d2-40ca-b88b-b6254e6f92be
    resourceVersion: "55155"
    uid: 6ff31229-9d4d-4481-b89e-2b99df396d72
  spec:
    sourcePod: network-check-source-989f8b8dc-rpzmw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:10:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.076779ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:40:10Z"
    - latency: 1.74085ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:40:10Z"
    - latency: 1.106482ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:39:10Z"
    - latency: 1.808537ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:39:10Z"
    - latency: 877.315µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:38:10Z"
    - latency: 1.761986ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:38:10Z"
    - latency: 878.68µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:37:10Z"
    - latency: 1.708645ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:37:10Z"
    - latency: 895.83µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:36:10Z"
    - latency: 1.895065ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:36:10Z"
kind: List
metadata:
  resourceVersion: ""