apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T04:21:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-181-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-181.ec2.internal
      uid: 64e1b9b1-9cf2-4251-bca7-417108519a43
    resourceVersion: "52983"
    uid: 0a1f638b-4028-4faa-b318-dfb46165bc54
  spec:
    sourcePod: network-check-source-989f8b8dc-l5bxr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T04:28:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 863.053µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:56:55Z"
    - latency: 1.458938ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:55:55Z"
    - latency: 1.076592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:54:55Z"
    - latency: 912.747µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:53:55Z"
    - latency: 1.180834ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:52:55Z"
    - latency: 1.123589ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:51:55Z"
    - latency: 1.150543ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:50:55Z"
    - latency: 1.224546ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:49:55Z"
    - latency: 1.127657ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:48:55Z"
    - latency: 898.868µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:47:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T04:21:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-181-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-181.ec2.internal
      uid: 64e1b9b1-9cf2-4251-bca7-417108519a43
    resourceVersion: "54040"
    uid: 739bc0d4-4f76-44f3-ad88-5caf89c2d2ac
  spec:
    sourcePod: network-check-source-989f8b8dc-l5bxr
    targetEndpoint: ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T04:27:55Z"
      message: 'load-balancer-api-external: tcp connection to ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.7342ms
      message: 'load-balancer-api-external: tcp connection to ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:57:55Z"
    - latency: 7.041475ms
      message: 'load-balancer-api-external: resolved host name ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:57:55Z"
    - latency: 4.393449ms
      message: 'load-balancer-api-external: tcp connection to ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:56:55Z"
    - latency: 10.788882ms
      message: 'load-balancer-api-external: resolved host name ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:56:55Z"
    - latency: 6.676419ms
      message: 'load-balancer-api-external: tcp connection to ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:55:55Z"
    - latency: 7.783485ms
      message: 'load-balancer-api-external: resolved host name ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:55:55Z"
    - latency: 5.404844ms
      message: 'load-balancer-api-external: tcp connection to ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:54:55Z"
    - latency: 8.481606ms
      message: 'load-balancer-api-external: resolved host name ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:54:55Z"
    - latency: 4.899962ms
      message: 'load-balancer-api-external: tcp connection to ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:53:55Z"
    - latency: 7.430033ms
      message: 'load-balancer-api-external: resolved host name ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:53:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T04:21:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-181-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-181.ec2.internal
      uid: 64e1b9b1-9cf2-4251-bca7-417108519a43
    resourceVersion: "54041"
    uid: 1a1aa38e-9abb-4af2-8882-2773cf83925a
  spec:
    sourcePod: network-check-source-989f8b8dc-l5bxr
    targetEndpoint: ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T04:27:55Z"
      message: 'load-balancer-api-internal: tcp connection to ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.981271ms
      message: 'load-balancer-api-internal: tcp connection to ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:57:55Z"
    - latency: 7.06442ms
      message: 'load-balancer-api-internal: resolved host name ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:57:55Z"
    - latency: 4.383297ms
      message: 'load-balancer-api-internal: tcp connection to ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:56:55Z"
    - latency: 10.908753ms
      message: 'load-balancer-api-internal: resolved host name ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:56:55Z"
    - latency: 3.728345ms
      message: 'load-balancer-api-internal: tcp connection to ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:55:55Z"
    - latency: 7.865541ms
      message: 'load-balancer-api-internal: resolved host name ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:55:55Z"
    - latency: 5.390209ms
      message: 'load-balancer-api-internal: tcp connection to ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:54:55Z"
    - latency: 8.524172ms
      message: 'load-balancer-api-internal: resolved host name ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:54:55Z"
    - latency: 4.915538ms
      message: 'load-balancer-api-internal: tcp connection to ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:53:55Z"
    - latency: 7.318085ms
      message: 'load-balancer-api-internal: resolved host name ab54f56ed12144c399be198414139dd5-75af5a5c9c37abb3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:53:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T04:21:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-181-to-network-check-target-ip-10-0-133-10
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-181.ec2.internal
      uid: 64e1b9b1-9cf2-4251-bca7-417108519a43
    resourceVersion: "52982"
    uid: 3b45f40a-b74b-4321-a0ca-7013c5ffdb64
  spec:
    sourcePod: network-check-source-989f8b8dc-l5bxr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T04:28:55Z"
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.056251ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:56:55Z"
    - latency: 1.624243ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:55:55Z"
    - latency: 1.916319ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:54:55Z"
    - latency: 2.055654ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:53:55Z"
    - latency: 1.723912ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:52:55Z"
    - latency: 1.98314ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:51:55Z"
    - latency: 2.008699ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:50:55Z"
    - latency: 2.047113ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:49:55Z"
    - latency: 1.937389ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:48:55Z"
    - latency: 1.88603ms
      message: 'network-check-target-ip-10-0-133-10: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:47:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T04:21:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-181-to-network-check-target-ip-10-0-142-181
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-181.ec2.internal
      uid: 64e1b9b1-9cf2-4251-bca7-417108519a43
    resourceVersion: "52980"
    uid: 11ac52d4-b517-41e7-9afd-a7a1c59ab9ca
  spec:
    sourcePod: network-check-source-989f8b8dc-l5bxr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T04:28:55Z"
      message: 'network-check-target-ip-10-0-142-181: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.663801ms
      message: 'network-check-target-ip-10-0-142-181: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:56:55Z"
    - latency: 1.600617ms
      message: 'network-check-target-ip-10-0-142-181: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:55:55Z"
    - latency: 921.502µs
      message: 'network-check-target-ip-10-0-142-181: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:54:55Z"
    - latency: 1.141374ms
      message: 'network-check-target-ip-10-0-142-181: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:53:55Z"
    - latency: 980.806µs
      message: 'network-check-target-ip-10-0-142-181: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:52:55Z"
    - latency: 993.617µs
      message: 'network-check-target-ip-10-0-142-181: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:51:55Z"
    - latency: 1.157159ms
      message: 'network-check-target-ip-10-0-142-181: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:50:55Z"
    - latency: 1.021863ms
      message: 'network-check-target-ip-10-0-142-181: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:49:55Z"
    - latency: 1.220269ms
      message: 'network-check-target-ip-10-0-142-181: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:48:55Z"
    - latency: 1.123054ms
      message: 'network-check-target-ip-10-0-142-181: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:47:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T04:21:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-181-to-network-check-target-ip-10-0-143-106
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-181.ec2.internal
      uid: 64e1b9b1-9cf2-4251-bca7-417108519a43
    resourceVersion: "52981"
    uid: 9b5ccccf-d1aa-42f2-95c7-3981e8b19c19
  spec:
    sourcePod: network-check-source-989f8b8dc-l5bxr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T04:28:55Z"
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.175171ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:56:55Z"
    - latency: 2.051655ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:55:55Z"
    - latency: 2.327057ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:54:55Z"
    - latency: 2.334436ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:53:55Z"
    - latency: 2.141676ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:52:55Z"
    - latency: 2.173431ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:51:55Z"
    - latency: 2.352573ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:50:55Z"
    - latency: 2.099215ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:49:55Z"
    - latency: 2.375461ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:48:55Z"
    - latency: 2.223094ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:47:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T04:21:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-181-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-181.ec2.internal
      uid: 64e1b9b1-9cf2-4251-bca7-417108519a43
    resourceVersion: "54039"
    uid: 20814aeb-0b78-4a39-863e-980e3006acb3
  spec:
    sourcePod: network-check-source-989f8b8dc-l5bxr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T04:27:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 887.773µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:57:55Z"
    - latency: 1.818185ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:57:55Z"
    - latency: 1.352941ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:56:55Z"
    - latency: 2.844697ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:56:55Z"
    - latency: 1.059942ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:55:55Z"
    - latency: 1.808766ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:55:55Z"
    - latency: 934.504µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:54:55Z"
    - latency: 2.539119ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:54:55Z"
    - latency: 920.997µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T04:53:55Z"
    - latency: 1.726002ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T04:53:55Z"
kind: List
metadata:
  resourceVersion: ""