apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:00:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-99.ec2.internal
      uid: 028203ad-781b-49bc-bc4f-5cf73ba26d23
    resourceVersion: "37748"
    uid: 8fee2e20-0cfd-45f3-8ecf-b6680c857348
  spec:
    sourcePod: network-check-source-7cbc45fddc-j9zqc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:07:22Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.016171ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:49:22Z"
    - latency: 1.029777ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:48:22Z"
    - latency: 1.19965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:47:22Z"
    - latency: 1.661852ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:46:22Z"
    - latency: 1.736361ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:45:22Z"
    - latency: 968.78µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:44:22Z"
    - latency: 1.747124ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:43:22Z"
    - latency: 1.102075ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:42:22Z"
    - latency: 1.074659ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:41:22Z"
    - latency: 1.034721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:40:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:00:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-99.ec2.internal
      uid: 028203ad-781b-49bc-bc4f-5cf73ba26d23
    resourceVersion: "40540"
    uid: 4ae13999-d27b-4b23-9046-c711de4afd7d
  spec:
    sourcePod: network-check-source-7cbc45fddc-j9zqc
    targetEndpoint: a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:06:22Z"
      message: 'load-balancer-api-external: tcp connection to a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.054041ms
      message: 'load-balancer-api-external: tcp connection to a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:54:22Z"
    - latency: 9.312555ms
      message: 'load-balancer-api-external: resolved host name a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:54:22Z"
    - latency: 6.135336ms
      message: 'load-balancer-api-external: tcp connection to a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:53:22Z"
    - latency: 8.372967ms
      message: 'load-balancer-api-external: resolved host name a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:53:22Z"
    - latency: 5.259108ms
      message: 'load-balancer-api-external: tcp connection to a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:52:22Z"
    - latency: 9.251795ms
      message: 'load-balancer-api-external: resolved host name a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:52:22Z"
    - latency: 5.563288ms
      message: 'load-balancer-api-external: tcp connection to a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:51:22Z"
    - latency: 9.224025ms
      message: 'load-balancer-api-external: resolved host name a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:51:22Z"
    - latency: 5.18037ms
      message: 'load-balancer-api-external: tcp connection to a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:50:22Z"
    - latency: 9.140862ms
      message: 'load-balancer-api-external: resolved host name a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:50:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:00:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-99.ec2.internal
      uid: 028203ad-781b-49bc-bc4f-5cf73ba26d23
    resourceVersion: "40539"
    uid: dcd1aaca-e7c0-4b4d-a8c7-37b8bd20215c
  spec:
    sourcePod: network-check-source-7cbc45fddc-j9zqc
    targetEndpoint: a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:06:22Z"
      message: 'load-balancer-api-internal: tcp connection to a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.064239ms
      message: 'load-balancer-api-internal: tcp connection to a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:54:22Z"
    - latency: 9.224402ms
      message: 'load-balancer-api-internal: resolved host name a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:54:22Z"
    - latency: 6.762228ms
      message: 'load-balancer-api-internal: tcp connection to a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:53:22Z"
    - latency: 8.330277ms
      message: 'load-balancer-api-internal: resolved host name a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:53:22Z"
    - latency: 5.106327ms
      message: 'load-balancer-api-internal: tcp connection to a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:52:22Z"
    - latency: 9.314625ms
      message: 'load-balancer-api-internal: resolved host name a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:52:22Z"
    - latency: 5.590204ms
      message: 'load-balancer-api-internal: tcp connection to a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:51:22Z"
    - latency: 9.03071ms
      message: 'load-balancer-api-internal: resolved host name a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:51:22Z"
    - latency: 5.244568ms
      message: 'load-balancer-api-internal: tcp connection to a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:50:22Z"
    - latency: 9.074375ms
      message: 'load-balancer-api-internal: resolved host name a0c6e568dfb014da49ed9e3143417547-3c41f323b2951933.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:50:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:00:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-99-to-network-check-target-ip-10-0-132-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-99.ec2.internal
      uid: 028203ad-781b-49bc-bc4f-5cf73ba26d23
    resourceVersion: "37747"
    uid: 96952730-750d-48b5-933d-356ac17e7c21
  spec:
    sourcePod: network-check-source-7cbc45fddc-j9zqc
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:07:22Z"
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.075905ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:49:22Z"
    - latency: 1.656014ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:48:22Z"
    - latency: 847.138µs
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:47:22Z"
    - latency: 967.92µs
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:46:22Z"
    - latency: 1.627068ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:45:22Z"
    - latency: 772.445µs
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:44:22Z"
    - latency: 1.077722ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:43:22Z"
    - latency: 1.391157ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:42:22Z"
    - latency: 917.868µs
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:41:22Z"
    - latency: 1.074789ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:40:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:00:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-99-to-network-check-target-ip-10-0-133-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-99.ec2.internal
      uid: 028203ad-781b-49bc-bc4f-5cf73ba26d23
    resourceVersion: "37746"
    uid: fd128f77-6310-49d2-905c-d6c879dc39d9
  spec:
    sourcePod: network-check-source-7cbc45fddc-j9zqc
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:07:22Z"
      message: 'network-check-target-ip-10-0-133-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.149959ms
      message: 'network-check-target-ip-10-0-133-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:49:22Z"
    - latency: 2.001001ms
      message: 'network-check-target-ip-10-0-133-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:48:22Z"
    - latency: 2.262923ms
      message: 'network-check-target-ip-10-0-133-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:47:22Z"
    - latency: 2.212993ms
      message: 'network-check-target-ip-10-0-133-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:46:22Z"
    - latency: 2.398214ms
      message: 'network-check-target-ip-10-0-133-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:45:22Z"
    - latency: 2.093157ms
      message: 'network-check-target-ip-10-0-133-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:44:22Z"
    - latency: 2.766015ms
      message: 'network-check-target-ip-10-0-133-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:43:22Z"
    - latency: 2.319903ms
      message: 'network-check-target-ip-10-0-133-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:42:22Z"
    - latency: 1.99444ms
      message: 'network-check-target-ip-10-0-133-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:41:22Z"
    - latency: 2.294986ms
      message: 'network-check-target-ip-10-0-133-177: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:40:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:00:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-99-to-network-check-target-ip-10-0-143-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-99.ec2.internal
      uid: 028203ad-781b-49bc-bc4f-5cf73ba26d23
    resourceVersion: "37745"
    uid: 299970ff-7e43-43be-a123-ad1481692fb8
  spec:
    sourcePod: network-check-source-7cbc45fddc-j9zqc
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:07:22Z"
      message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.389852ms
      message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:49:22Z"
    - latency: 2.317112ms
      message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:48:22Z"
    - latency: 2.788046ms
      message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:47:22Z"
    - latency: 2.472025ms
      message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:46:22Z"
    - latency: 2.843906ms
      message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:45:22Z"
    - latency: 2.122715ms
      message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:44:22Z"
    - latency: 2.635314ms
      message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:43:22Z"
    - latency: 2.307764ms
      message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:42:22Z"
    - latency: 2.228343ms
      message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:41:22Z"
    - latency: 2.292957ms
      message: 'network-check-target-ip-10-0-143-5: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:40:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T17:00:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-99.ec2.internal
      uid: 028203ad-781b-49bc-bc4f-5cf73ba26d23
    resourceVersion: "40538"
    uid: 061ce051-f750-4408-aa8c-75e3ae407811
  spec:
    sourcePod: network-check-source-7cbc45fddc-j9zqc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T17:06:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.169µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:54:22Z"
    - latency: 2.329271ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:54:22Z"
    - latency: 1.267104ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:53:22Z"
    - latency: 1.827865ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:53:22Z"
    - latency: 933.099µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:52:22Z"
    - latency: 1.96256ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:52:22Z"
    - latency: 940.158µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:51:22Z"
    - latency: 1.848537ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:51:22Z"
    - latency: 856.434µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T17:50:22Z"
    - latency: 1.763193ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T17:50:22Z"
kind: List
metadata:
  resourceVersion: ""