apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T21:09:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-187-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-187.ec2.internal
      uid: 85b1c08e-e832-4506-800c-45b3e4152e9c
    resourceVersion: "65702"
    uid: 643f08b6-15ef-4e55-9572-73a91dfc5f00
  spec:
    sourcePod: network-check-source-7cbc45fddc-m7zbc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T21:16:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.124505ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:44:52Z"
    - latency: 1.207245ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:43:52Z"
    - latency: 994.915µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:42:52Z"
    - latency: 1.213469ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:41:52Z"
    - latency: 1.38627ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:40:52Z"
    - latency: 1.442477ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:39:52Z"
    - latency: 1.005312ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:38:52Z"
    - latency: 1.192291ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:37:52Z"
    - latency: 979.124µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:36:52Z"
    - latency: 1.137806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:35:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T21:09:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-187-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-187.ec2.internal
      uid: 85b1c08e-e832-4506-800c-45b3e4152e9c
    resourceVersion: "66807"
    uid: b871a0cf-a7bf-4839-a255-56827a2a9a12
  spec:
    sourcePod: network-check-source-7cbc45fddc-m7zbc
    targetEndpoint: a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T21:15:52Z"
      message: 'load-balancer-api-external: tcp connection to a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.981044ms
      message: 'load-balancer-api-external: tcp connection to a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:45:52Z"
    - latency: 6.670831ms
      message: 'load-balancer-api-external: resolved host name a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:45:52Z"
    - latency: 11.102347ms
      message: 'load-balancer-api-external: tcp connection to a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:44:52Z"
    - latency: 6.936744ms
      message: 'load-balancer-api-external: resolved host name a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:44:52Z"
    - latency: 5.96154ms
      message: 'load-balancer-api-external: tcp connection to a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:43:52Z"
    - latency: 6.516991ms
      message: 'load-balancer-api-external: resolved host name a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:43:52Z"
    - latency: 3.673915ms
      message: 'load-balancer-api-external: tcp connection to a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:42:52Z"
    - latency: 7.266382ms
      message: 'load-balancer-api-external: resolved host name a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:42:52Z"
    - latency: 3.842192ms
      message: 'load-balancer-api-external: tcp connection to a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:41:52Z"
    - latency: 6.582685ms
      message: 'load-balancer-api-external: resolved host name a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:41:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T21:09:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-187-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-187.ec2.internal
      uid: 85b1c08e-e832-4506-800c-45b3e4152e9c
    resourceVersion: "66808"
    uid: ed634490-027f-45f1-ba9b-09502f792816
  spec:
    sourcePod: network-check-source-7cbc45fddc-m7zbc
    targetEndpoint: a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T21:15:52Z"
      message: 'load-balancer-api-internal: tcp connection to a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.997526ms
      message: 'load-balancer-api-internal: tcp connection to a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:45:52Z"
    - latency: 6.65337ms
      message: 'load-balancer-api-internal: resolved host name a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:45:52Z"
    - latency: 4.525955ms
      message: 'load-balancer-api-internal: tcp connection to a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:44:52Z"
    - latency: 6.893946ms
      message: 'load-balancer-api-internal: resolved host name a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:44:52Z"
    - latency: 5.519638ms
      message: 'load-balancer-api-internal: tcp connection to a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:43:52Z"
    - latency: 6.48705ms
      message: 'load-balancer-api-internal: resolved host name a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:43:52Z"
    - latency: 3.278718ms
      message: 'load-balancer-api-internal: tcp connection to a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:42:52Z"
    - latency: 7.236654ms
      message: 'load-balancer-api-internal: resolved host name a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:42:52Z"
    - latency: 5.628869ms
      message: 'load-balancer-api-internal: tcp connection to a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:41:52Z"
    - latency: 6.533692ms
      message: 'load-balancer-api-internal: resolved host name a09043fc62cbf4739bb1111fa9d2d344-ac78f8b995c8d1a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:41:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T21:09:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-187-to-network-check-target-ip-10-0-130-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-187.ec2.internal
      uid: 85b1c08e-e832-4506-800c-45b3e4152e9c
    resourceVersion: "65701"
    uid: b201421b-850a-4201-9815-6efc91546a0b
  spec:
    sourcePod: network-check-source-7cbc45fddc-m7zbc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T21:16:52Z"
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.798208ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:44:52Z"
    - latency: 2.006634ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:43:52Z"
    - latency: 2.007524ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:42:52Z"
    - latency: 1.896414ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:41:52Z"
    - latency: 2.042729ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:40:52Z"
    - latency: 2.069483ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:39:52Z"
    - latency: 1.930235ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:38:52Z"
    - latency: 2.154691ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:37:52Z"
    - latency: 2.079866ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:36:52Z"
    - latency: 1.795927ms
      message: 'network-check-target-ip-10-0-130-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:35:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T21:09:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-187-to-network-check-target-ip-10-0-132-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-187.ec2.internal
      uid: 85b1c08e-e832-4506-800c-45b3e4152e9c
    resourceVersion: "65699"
    uid: 0638064b-923b-41c1-8ba0-744f7e7c0b6c
  spec:
    sourcePod: network-check-source-7cbc45fddc-m7zbc
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T21:16:52Z"
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.33µs
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:44:52Z"
    - latency: 898.766µs
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:43:52Z"
    - latency: 1.101476ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:42:52Z"
    - latency: 1.038646ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:41:52Z"
    - latency: 1.174691ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:40:52Z"
    - latency: 1.143483ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:39:52Z"
    - latency: 1.051926ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:38:52Z"
    - latency: 907.64µs
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:37:52Z"
    - latency: 1.035141ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:36:52Z"
    - latency: 1.162817ms
      message: 'network-check-target-ip-10-0-132-187: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:35:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T21:09:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-187-to-network-check-target-ip-10-0-132-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-187.ec2.internal
      uid: 85b1c08e-e832-4506-800c-45b3e4152e9c
    resourceVersion: "65700"
    uid: 988d2831-d44e-43d6-97d0-fc8d18fd35ae
  spec:
    sourcePod: network-check-source-7cbc45fddc-m7zbc
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T21:16:52Z"
      message: 'network-check-target-ip-10-0-132-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.192247ms
      message: 'network-check-target-ip-10-0-132-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:44:52Z"
    - latency: 2.306776ms
      message: 'network-check-target-ip-10-0-132-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:43:52Z"
    - latency: 2.329353ms
      message: 'network-check-target-ip-10-0-132-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:42:52Z"
    - latency: 2.574523ms
      message: 'network-check-target-ip-10-0-132-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:41:52Z"
    - latency: 2.40432ms
      message: 'network-check-target-ip-10-0-132-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:40:52Z"
    - latency: 2.390478ms
      message: 'network-check-target-ip-10-0-132-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:39:52Z"
    - latency: 1.95622ms
      message: 'network-check-target-ip-10-0-132-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:38:52Z"
    - latency: 2.565418ms
      message: 'network-check-target-ip-10-0-132-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:37:52Z"
    - latency: 2.509634ms
      message: 'network-check-target-ip-10-0-132-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:36:52Z"
    - latency: 2.360182ms
      message: 'network-check-target-ip-10-0-132-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:35:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T21:09:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-187-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-187.ec2.internal
      uid: 85b1c08e-e832-4506-800c-45b3e4152e9c
    resourceVersion: "66806"
    uid: 6ef517ef-0be9-4ebc-aa04-31b7087894cf
  spec:
    sourcePod: network-check-source-7cbc45fddc-m7zbc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T21:15:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.085305ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:45:52Z"
    - latency: 2.155443ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:45:52Z"
    - latency: 1.021362ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:44:52Z"
    - latency: 1.721163ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:44:52Z"
    - latency: 912.422µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:43:52Z"
    - latency: 1.867867ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:43:52Z"
    - latency: 881.595µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:42:52Z"
    - latency: 1.824429ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:42:52Z"
    - latency: 1.170374ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T21:41:52Z"
    - latency: 1.886191ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T21:41:52Z"
kind: List
metadata:
  resourceVersion: ""