apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T16:34:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-146.ec2.internal
      uid: 3824a798-2659-412a-a402-96bb3e7012a0
    resourceVersion: "54225"
    uid: d1df764d-afd7-4d4a-913e-f96efdf14e1b
  spec:
    sourcePod: network-check-source-685456655f-crw2t
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T16:41:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.127632ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:02:27Z"
    - latency: 923.676µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:01:27Z"
    - latency: 1.128857ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:00:27Z"
    - latency: 843.726µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:59:27Z"
    - latency: 1.321008ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:58:27Z"
    - latency: 1.303347ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:57:27Z"
    - latency: 823.322µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:56:27Z"
    - latency: 909.704µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:55:27Z"
    - latency: 952.182µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:54:27Z"
    - latency: 1.118501ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:53:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T16:34:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-146.ec2.internal
      uid: 3824a798-2659-412a-a402-96bb3e7012a0
    resourceVersion: "55999"
    uid: 384a5bc2-daf2-475c-b1e4-90aa127860a5
  spec:
    sourcePod: network-check-source-685456655f-crw2t
    targetEndpoint: a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T16:40:27Z"
      message: 'load-balancer-api-external: tcp connection to a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.897929ms
      message: 'load-balancer-api-external: tcp connection to a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:04:27Z"
    - latency: 8.536979ms
      message: 'load-balancer-api-external: resolved host name a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:04:27Z"
    - latency: 13.469482ms
      message: 'load-balancer-api-external: tcp connection to a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:03:27Z"
    - latency: 8.613754ms
      message: 'load-balancer-api-external: resolved host name a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:03:27Z"
    - latency: 4.282134ms
      message: 'load-balancer-api-external: tcp connection to a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:02:27Z"
    - latency: 7.547478ms
      message: 'load-balancer-api-external: resolved host name a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:02:27Z"
    - latency: 5.458851ms
      message: 'load-balancer-api-external: tcp connection to a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:01:27Z"
    - latency: 7.289539ms
      message: 'load-balancer-api-external: resolved host name a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:01:27Z"
    - latency: 4.968038ms
      message: 'load-balancer-api-external: tcp connection to a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:00:27Z"
    - latency: 7.862929ms
      message: 'load-balancer-api-external: resolved host name a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:00:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T16:34:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-146.ec2.internal
      uid: 3824a798-2659-412a-a402-96bb3e7012a0
    resourceVersion: "56000"
    uid: 4e317c95-a087-445b-bd70-de612ec90043
  spec:
    sourcePod: network-check-source-685456655f-crw2t
    targetEndpoint: a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T16:40:27Z"
      message: 'load-balancer-api-internal: tcp connection to a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.271724ms
      message: 'load-balancer-api-internal: tcp connection to a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:04:27Z"
    - latency: 8.571938ms
      message: 'load-balancer-api-internal: resolved host name a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:04:27Z"
    - latency: 5.212664ms
      message: 'load-balancer-api-internal: tcp connection to a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:03:27Z"
    - latency: 8.585204ms
      message: 'load-balancer-api-internal: resolved host name a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:03:27Z"
    - latency: 4.253717ms
      message: 'load-balancer-api-internal: tcp connection to a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:02:27Z"
    - latency: 7.487471ms
      message: 'load-balancer-api-internal: resolved host name a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:02:27Z"
    - latency: 5.446857ms
      message: 'load-balancer-api-internal: tcp connection to a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:01:27Z"
    - latency: 7.396618ms
      message: 'load-balancer-api-internal: resolved host name a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:01:27Z"
    - latency: 4.959013ms
      message: 'load-balancer-api-internal: tcp connection to a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:00:27Z"
    - latency: 7.897618ms
      message: 'load-balancer-api-internal: resolved host name a8511bca289d744028ee53a211faa952-99008688c713f9dc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:00:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T16:34:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-146-to-network-check-target-ip-10-0-129-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-146.ec2.internal
      uid: 3824a798-2659-412a-a402-96bb3e7012a0
    resourceVersion: "54222"
    uid: 91e02ec9-d3e3-4461-bb5c-bfc052ecc0a6
  spec:
    sourcePod: network-check-source-685456655f-crw2t
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T16:41:27Z"
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.425637ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:02:27Z"
    - latency: 1.007584ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:01:27Z"
    - latency: 856.663µs
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:00:27Z"
    - latency: 1.080677ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:59:27Z"
    - latency: 1.035234ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:58:27Z"
    - latency: 1.060501ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:57:27Z"
    - latency: 908.219µs
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:56:27Z"
    - latency: 1.139622ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:55:27Z"
    - latency: 1.587227ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:54:27Z"
    - latency: 1.03243ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:53:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T16:34:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-146-to-network-check-target-ip-10-0-131-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-146.ec2.internal
      uid: 3824a798-2659-412a-a402-96bb3e7012a0
    resourceVersion: "54223"
    uid: df1ddc87-7094-49c4-8bf4-e80fdc3279b8
  spec:
    sourcePod: network-check-source-685456655f-crw2t
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T16:41:27Z"
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.277005ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:02:27Z"
    - latency: 1.960104ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:01:27Z"
    - latency: 2.180975ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:00:27Z"
    - latency: 2.421232ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:59:27Z"
    - latency: 2.097653ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:58:27Z"
    - latency: 1.914138ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:57:27Z"
    - latency: 1.83942ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:56:27Z"
    - latency: 2.678313ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:55:27Z"
    - latency: 2.108711ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:54:27Z"
    - latency: 2.01395ms
      message: 'network-check-target-ip-10-0-131-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:53:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T16:34:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-146-to-network-check-target-ip-10-0-139-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-146.ec2.internal
      uid: 3824a798-2659-412a-a402-96bb3e7012a0
    resourceVersion: "54224"
    uid: 256df3fc-87d4-42dc-97eb-affcf0f783ba
  spec:
    sourcePod: network-check-source-685456655f-crw2t
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T16:41:27Z"
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.339908ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:02:27Z"
    - latency: 2.03533ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:01:27Z"
    - latency: 2.00751ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:00:27Z"
    - latency: 2.497869ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:59:27Z"
    - latency: 2.987498ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:58:27Z"
    - latency: 2.261409ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:57:27Z"
    - latency: 2.410655ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:56:27Z"
    - latency: 2.732529ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:55:27Z"
    - latency: 2.528522ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:54:27Z"
    - latency: 2.100397ms
      message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:53:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T16:34:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-146.ec2.internal
      uid: 3824a798-2659-412a-a402-96bb3e7012a0
    resourceVersion: "55998"
    uid: 72815d65-29c2-4fbe-bb58-5eb0d81b209f
  spec:
    sourcePod: network-check-source-685456655f-crw2t
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T16:40:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.097542ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:04:27Z"
    - latency: 1.782149ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:04:27Z"
    - latency: 1.498186ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:03:27Z"
    - latency: 1.81928ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:03:27Z"
    - latency: 907.454µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:02:27Z"
    - latency: 2.355159ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:02:27Z"
    - latency: 869.238µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:01:27Z"
    - latency: 1.76201ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:01:27Z"
    - latency: 1.065316ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T17:00:27Z"
    - latency: 1.667829ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T17:00:27Z"
kind: List
metadata:
  resourceVersion: ""