apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T14:16:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-36-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-36.ec2.internal
      uid: 1aa2c2cd-058e-4c62-89b3-d464482fd4de
    resourceVersion: "54223"
    uid: 45156118-6df4-4509-bea3-37e228bafb7f
  spec:
    sourcePod: network-check-source-989f8b8dc-htwv5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T14:23:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.298385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:51:14Z"
    - latency: 1.0039ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:50:14Z"
    - latency: 1.125964ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:49:14Z"
    - latency: 1.348104ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:48:14Z"
    - latency: 1.317674ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:47:14Z"
    - latency: 1.237592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:46:14Z"
    - latency: 1.185592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:45:14Z"
    - latency: 1.124655ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:44:14Z"
    - latency: 930.482µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:43:14Z"
    - latency: 1.43962ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:42:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T14:16:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-36-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-36.ec2.internal
      uid: 1aa2c2cd-058e-4c62-89b3-d464482fd4de
    resourceVersion: "55285"
    uid: 3874364f-9364-4aa6-a359-26e597147146
  spec:
    sourcePod: network-check-source-989f8b8dc-htwv5
    targetEndpoint: a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T14:22:14Z"
      message: 'load-balancer-api-external: tcp connection to a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.239917ms
      message: 'load-balancer-api-external: tcp connection to a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:52:14Z"
    - latency: 7.672125ms
      message: 'load-balancer-api-external: resolved host name a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:52:14Z"
    - latency: 4.864285ms
      message: 'load-balancer-api-external: tcp connection to a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:51:14Z"
    - latency: 8.141207ms
      message: 'load-balancer-api-external: resolved host name a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:51:14Z"
    - latency: 3.78364ms
      message: 'load-balancer-api-external: tcp connection to a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:50:14Z"
    - latency: 10.457613ms
      message: 'load-balancer-api-external: resolved host name a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:50:14Z"
    - latency: 4.754118ms
      message: 'load-balancer-api-external: tcp connection to a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:49:14Z"
    - latency: 7.794711ms
      message: 'load-balancer-api-external: resolved host name a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:49:14Z"
    - latency: 4.225206ms
      message: 'load-balancer-api-external: tcp connection to a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:48:14Z"
    - latency: 8.850332ms
      message: 'load-balancer-api-external: resolved host name a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:48:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T14:16:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-36-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-36.ec2.internal
      uid: 1aa2c2cd-058e-4c62-89b3-d464482fd4de
    resourceVersion: "55284"
    uid: 16889111-f285-44d6-ad17-ffa77665d703
  spec:
    sourcePod: network-check-source-989f8b8dc-htwv5
    targetEndpoint: a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T14:22:14Z"
      message: 'load-balancer-api-internal: tcp connection to a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.235919ms
      message: 'load-balancer-api-internal: tcp connection to a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:52:14Z"
    - latency: 7.769359ms
      message: 'load-balancer-api-internal: resolved host name a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:52:14Z"
    - latency: 4.78477ms
      message: 'load-balancer-api-internal: tcp connection to a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:51:14Z"
    - latency: 8.26052ms
      message: 'load-balancer-api-internal: resolved host name a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:51:14Z"
    - latency: 3.728761ms
      message: 'load-balancer-api-internal: tcp connection to a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:50:14Z"
    - latency: 10.758862ms
      message: 'load-balancer-api-internal: resolved host name a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:50:14Z"
    - latency: 4.739023ms
      message: 'load-balancer-api-internal: tcp connection to a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:49:14Z"
    - latency: 7.827308ms
      message: 'load-balancer-api-internal: resolved host name a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:49:14Z"
    - latency: 5.854351ms
      message: 'load-balancer-api-internal: tcp connection to a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:48:14Z"
    - latency: 8.920394ms
      message: 'load-balancer-api-internal: resolved host name a4101e34b15874c229081e52c82309b5-c32321eec67d0274.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:48:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T14:16:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-36-to-network-check-target-ip-10-0-133-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-36.ec2.internal
      uid: 1aa2c2cd-058e-4c62-89b3-d464482fd4de
    resourceVersion: "54221"
    uid: 3152e905-d53f-4ae7-a4c1-b737de02ca44
  spec:
    sourcePod: network-check-source-989f8b8dc-htwv5
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T14:23:14Z"
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.8859ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:51:14Z"
    - latency: 2.177998ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:50:14Z"
    - latency: 2.405138ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:49:14Z"
    - latency: 2.506465ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:48:14Z"
    - latency: 2.538628ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:47:14Z"
    - latency: 2.203134ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:46:14Z"
    - latency: 2.881294ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:45:14Z"
    - latency: 1.900809ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:44:14Z"
    - latency: 2.07788ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:43:14Z"
    - latency: 2.354547ms
      message: 'network-check-target-ip-10-0-133-223: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:42:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T14:16:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-36-to-network-check-target-ip-10-0-137-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-36.ec2.internal
      uid: 1aa2c2cd-058e-4c62-89b3-d464482fd4de
    resourceVersion: "54220"
    uid: 38251ba9-91b8-4973-b280-7ca154727ee4
  spec:
    sourcePod: network-check-source-989f8b8dc-htwv5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T14:23:14Z"
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.288µs
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:51:14Z"
    - latency: 1.734734ms
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:50:14Z"
    - latency: 1.359884ms
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:49:14Z"
    - latency: 924.471µs
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:48:14Z"
    - latency: 1.39918ms
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:47:14Z"
    - latency: 1.083207ms
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:46:14Z"
    - latency: 987.193µs
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:45:14Z"
    - latency: 961.647µs
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:44:14Z"
    - latency: 927.231µs
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:43:14Z"
    - latency: 910.059µs
      message: 'network-check-target-ip-10-0-137-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:42:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T14:16:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-36-to-network-check-target-ip-10-0-141-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-36.ec2.internal
      uid: 1aa2c2cd-058e-4c62-89b3-d464482fd4de
    resourceVersion: "54222"
    uid: 1302ce8f-7bb1-4a35-ae2c-57644f3c8496
  spec:
    sourcePod: network-check-source-989f8b8dc-htwv5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T14:23:14Z"
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.318883ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:51:14Z"
    - latency: 2.471558ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:50:14Z"
    - latency: 2.362071ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:49:14Z"
    - latency: 2.55497ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:48:14Z"
    - latency: 2.234244ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:47:14Z"
    - latency: 2.201884ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:46:14Z"
    - latency: 2.674509ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:45:14Z"
    - latency: 2.445456ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:44:14Z"
    - latency: 2.101031ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:43:14Z"
    - latency: 2.732874ms
      message: 'network-check-target-ip-10-0-141-67: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:42:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T14:16:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-36-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-36.ec2.internal
      uid: 1aa2c2cd-058e-4c62-89b3-d464482fd4de
    resourceVersion: "55283"
    uid: ff357393-707b-41cf-8f25-b736d71c6491
  spec:
    sourcePod: network-check-source-989f8b8dc-htwv5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T14:22:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.788909ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:52:14Z"
    - latency: 1.825885ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:52:14Z"
    - latency: 962.334µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:51:14Z"
    - latency: 1.748858ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:51:14Z"
    - latency: 877.809µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:50:14Z"
    - latency: 2.053865ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:50:14Z"
    - latency: 925.076µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:49:14Z"
    - latency: 1.737867ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:49:14Z"
    - latency: 1.058294ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T14:48:14Z"
    - latency: 2.593354ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T14:48:14Z"
kind: List
metadata:
  resourceVersion: ""