apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:20:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 1161204d-57da-478d-8d22-02f7dee0a453
    resourceVersion: "68223"
    uid: 85bce997-2fef-4f97-abd5-a6106fb9db65
  spec:
    sourcePod: network-check-source-6f8b768455-rhlvr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:27:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 865.05µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:20Z"
    - latency: 997.521µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:20Z"
    - latency: 895.43µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:20Z"
    - latency: 1.753349ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:20Z"
    - latency: 1.054883ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:20Z"
    - latency: 1.386977ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:20Z"
    - latency: 845.27µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:20Z"
    - latency: 1.009802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:20Z"
    - latency: 1.07947ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:20Z"
    - latency: 1.625666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:46:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:20:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 1161204d-57da-478d-8d22-02f7dee0a453
    resourceVersion: "69198"
    uid: f0558eff-6e15-4a9f-a886-69f62cff4b44
  spec:
    sourcePod: network-check-source-6f8b768455-rhlvr
    targetEndpoint: a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:26:20Z"
      message: 'load-balancer-api-external: tcp connection to a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.586455ms
      message: 'load-balancer-api-external: tcp connection to a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:20Z"
    - latency: 7.825557ms
      message: 'load-balancer-api-external: resolved host name a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:56:20Z"
    - latency: 4.129979ms
      message: 'load-balancer-api-external: tcp connection to a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:20Z"
    - latency: 8.796109ms
      message: 'load-balancer-api-external: resolved host name a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:55:20Z"
    - latency: 4.15407ms
      message: 'load-balancer-api-external: tcp connection to a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:20Z"
    - latency: 8.075548ms
      message: 'load-balancer-api-external: resolved host name a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:54:20Z"
    - latency: 4.355685ms
      message: 'load-balancer-api-external: tcp connection to a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:20Z"
    - latency: 8.661832ms
      message: 'load-balancer-api-external: resolved host name a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:53:20Z"
    - latency: 4.027709ms
      message: 'load-balancer-api-external: tcp connection to a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:20Z"
    - latency: 7.920298ms
      message: 'load-balancer-api-external: resolved host name a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:52:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:20:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 1161204d-57da-478d-8d22-02f7dee0a453
    resourceVersion: "69197"
    uid: 58b29ebf-5309-46bf-893f-a7b4231bf181
  spec:
    sourcePod: network-check-source-6f8b768455-rhlvr
    targetEndpoint: a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:26:20Z"
      message: 'load-balancer-api-internal: tcp connection to a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.540222ms
      message: 'load-balancer-api-internal: tcp connection to a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:20Z"
    - latency: 7.922881ms
      message: 'load-balancer-api-internal: resolved host name a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:56:20Z"
    - latency: 4.195894ms
      message: 'load-balancer-api-internal: tcp connection to a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:20Z"
    - latency: 8.933208ms
      message: 'load-balancer-api-internal: resolved host name a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:55:20Z"
    - latency: 4.119124ms
      message: 'load-balancer-api-internal: tcp connection to a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:20Z"
    - latency: 8.161838ms
      message: 'load-balancer-api-internal: resolved host name a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:54:20Z"
    - latency: 4.349307ms
      message: 'load-balancer-api-internal: tcp connection to a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:20Z"
    - latency: 8.784641ms
      message: 'load-balancer-api-internal: resolved host name a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:53:20Z"
    - latency: 3.991398ms
      message: 'load-balancer-api-internal: tcp connection to a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:20Z"
    - latency: 8.005271ms
      message: 'load-balancer-api-internal: resolved host name a7cf5293f59054e8294013843daa1226-a0b1d805bee936ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:52:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:20:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-network-check-target-ip-10-0-128-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 1161204d-57da-478d-8d22-02f7dee0a453
    resourceVersion: "68222"
    uid: 5b033055-d46b-42ed-8104-108fcbbb0d6d
  spec:
    sourcePod: network-check-source-6f8b768455-rhlvr
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:27:20Z"
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.332981ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:20Z"
    - latency: 2.401978ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:20Z"
    - latency: 2.269139ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:20Z"
    - latency: 3.363309ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:20Z"
    - latency: 2.093857ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:20Z"
    - latency: 2.572268ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:20Z"
    - latency: 2.547044ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:20Z"
    - latency: 2.715631ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:20Z"
    - latency: 2.369572ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:20Z"
    - latency: 2.681315ms
      message: 'network-check-target-ip-10-0-128-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:46:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:20:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-network-check-target-ip-10-0-138-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 1161204d-57da-478d-8d22-02f7dee0a453
    resourceVersion: "68221"
    uid: 16ee3c72-de36-41b6-a9dd-f14e033d3db2
  spec:
    sourcePod: network-check-source-6f8b768455-rhlvr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:27:20Z"
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.327835ms
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:20Z"
    - latency: 2.271056ms
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:20Z"
    - latency: 2.351738ms
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:20Z"
    - latency: 2.37952ms
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:20Z"
    - latency: 2.457092ms
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:20Z"
    - latency: 2.945207ms
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:20Z"
    - latency: 2.107829ms
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:20Z"
    - latency: 2.348295ms
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:20Z"
    - latency: 2.291098ms
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:20Z"
    - latency: 2.544415ms
      message: 'network-check-target-ip-10-0-138-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:46:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:20:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-network-check-target-ip-10-0-143-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 1161204d-57da-478d-8d22-02f7dee0a453
    resourceVersion: "68220"
    uid: dd9443ea-72c3-47d8-aba6-ca9f985cb965
  spec:
    sourcePod: network-check-source-6f8b768455-rhlvr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:27:20Z"
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 979.809µs
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:20Z"
    - latency: 1.154051ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:20Z"
    - latency: 795.173µs
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:20Z"
    - latency: 880.755µs
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:20Z"
    - latency: 1.004888ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:20Z"
    - latency: 1.568103ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:20Z"
    - latency: 1.22092ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:20Z"
    - latency: 1.027004ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:20Z"
    - latency: 924.842µs
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:20Z"
    - latency: 1.451384ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:46:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:20:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-92-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-92.ec2.internal
      uid: 1161204d-57da-478d-8d22-02f7dee0a453
    resourceVersion: "69196"
    uid: 9328622a-2e98-49f6-a613-4137dbfe640f
  spec:
    sourcePod: network-check-source-6f8b768455-rhlvr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:26:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.302529ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:20Z"
    - latency: 1.877795ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:56:20Z"
    - latency: 887.504µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:20Z"
    - latency: 1.821953ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:55:20Z"
    - latency: 879.539µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:20Z"
    - latency: 1.662705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:54:20Z"
    - latency: 1.019155ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:20Z"
    - latency: 1.662576ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:53:20Z"
    - latency: 1.476282ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:20Z"
    - latency: 1.888125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:52:20Z"
kind: List
metadata:
  resourceVersion: ""