apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:42:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-52-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-52.ec2.internal
      uid: 0ab14dd6-435b-4def-a4ef-97955eb810a9
    resourceVersion: "19440"
    uid: 99c53da6-f204-46b7-8852-af51cab85937
  spec:
    sourcePod: network-check-source-989f8b8dc-hsdkl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:49:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.502µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:26Z"
    - latency: 1.05383ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:26Z"
    - latency: 964.732µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:01:26Z"
    - latency: 1.497451ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:00:26Z"
    - latency: 1.010797ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:59:26Z"
    - latency: 1.153313ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:58:26Z"
    - latency: 903.463µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:26Z"
    - latency: 1.618202ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:56:26Z"
    - latency: 1.198545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:55:26Z"
    - latency: 950.965µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:54:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:42:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-52-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-52.ec2.internal
      uid: 0ab14dd6-435b-4def-a4ef-97955eb810a9
    resourceVersion: "20615"
    uid: 61a516ce-9cfe-47a2-9a97-e75e99fae311
  spec:
    sourcePod: network-check-source-989f8b8dc-hsdkl
    targetEndpoint: a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:48:26Z"
      message: 'load-balancer-api-external: tcp connection to a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.063933ms
      message: 'load-balancer-api-external: tcp connection to a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:26Z"
    - latency: 10.115724ms
      message: 'load-balancer-api-external: resolved host name a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:06:26Z"
    - latency: 5.581769ms
      message: 'load-balancer-api-external: tcp connection to a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:26Z"
    - latency: 8.468967ms
      message: 'load-balancer-api-external: resolved host name a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:05:26Z"
    - latency: 5.158191ms
      message: 'load-balancer-api-external: tcp connection to a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:26Z"
    - latency: 8.134892ms
      message: 'load-balancer-api-external: resolved host name a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:04:26Z"
    - latency: 9.283934ms
      message: 'load-balancer-api-external: tcp connection to a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:26Z"
    - latency: 14.947989ms
      message: 'load-balancer-api-external: resolved host name a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:03:26Z"
    - latency: 5.312608ms
      message: 'load-balancer-api-external: tcp connection to a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:26Z"
    - latency: 7.092931ms
      message: 'load-balancer-api-external: resolved host name a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:02:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:42:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-52-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-52.ec2.internal
      uid: 0ab14dd6-435b-4def-a4ef-97955eb810a9
    resourceVersion: "20614"
    uid: 1d4ad938-c70f-4015-9d76-2e3057b65179
  spec:
    sourcePod: network-check-source-989f8b8dc-hsdkl
    targetEndpoint: a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:48:26Z"
      message: 'load-balancer-api-internal: tcp connection to a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.028563ms
      message: 'load-balancer-api-internal: tcp connection to a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:26Z"
    - latency: 10.192474ms
      message: 'load-balancer-api-internal: resolved host name a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:06:26Z"
    - latency: 5.767166ms
      message: 'load-balancer-api-internal: tcp connection to a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:26Z"
    - latency: 8.501944ms
      message: 'load-balancer-api-internal: resolved host name a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:05:26Z"
    - latency: 5.121254ms
      message: 'load-balancer-api-internal: tcp connection to a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:26Z"
    - latency: 8.203504ms
      message: 'load-balancer-api-internal: resolved host name a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:04:26Z"
    - latency: 9.200613ms
      message: 'load-balancer-api-internal: tcp connection to a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:26Z"
    - latency: 15.00887ms
      message: 'load-balancer-api-internal: resolved host name a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:03:26Z"
    - latency: 5.319054ms
      message: 'load-balancer-api-internal: tcp connection to a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:26Z"
    - latency: 7.034736ms
      message: 'load-balancer-api-internal: resolved host name a0519c034dd204a25a7166b3ee847b17-6527a6f792f5f7c7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:02:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:42:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-52-to-network-check-target-ip-10-0-128-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-52.ec2.internal
      uid: 0ab14dd6-435b-4def-a4ef-97955eb810a9
    resourceVersion: "19437"
    uid: ccabdc78-b555-48a1-871b-aa7204efa3b6
  spec:
    sourcePod: network-check-source-989f8b8dc-hsdkl
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:49:26Z"
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 871.399µs
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:26Z"
    - latency: 790.599µs
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:26Z"
    - latency: 788.286µs
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:01:26Z"
    - latency: 1.708006ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:00:26Z"
    - latency: 1.241319ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:59:26Z"
    - latency: 779.93µs
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:58:26Z"
    - latency: 775.067µs
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:26Z"
    - latency: 943.507µs
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:56:26Z"
    - latency: 829.162µs
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:55:26Z"
    - latency: 1.174394ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:54:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:42:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-52-to-network-check-target-ip-10-0-130-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-52.ec2.internal
      uid: 0ab14dd6-435b-4def-a4ef-97955eb810a9
    resourceVersion: "19439"
    uid: d6d0b672-fe0a-4162-b788-e6345a42c484
  spec:
    sourcePod: network-check-source-989f8b8dc-hsdkl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:49:26Z"
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.772392ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:26Z"
    - latency: 1.972502ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:26Z"
    - latency: 1.971855ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:01:26Z"
    - latency: 1.800146ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:00:26Z"
    - latency: 1.805895ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:59:26Z"
    - latency: 2.013871ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:58:26Z"
    - latency: 1.658699ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:26Z"
    - latency: 1.750475ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:56:26Z"
    - latency: 1.773951ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:55:26Z"
    - latency: 1.721807ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:54:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:42:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-52-to-network-check-target-ip-10-0-140-181
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-52.ec2.internal
      uid: 0ab14dd6-435b-4def-a4ef-97955eb810a9
    resourceVersion: "19438"
    uid: efe97485-aba9-4dd9-a27f-34318c822c7a
  spec:
    sourcePod: network-check-source-989f8b8dc-hsdkl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:49:26Z"
      message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.84456ms
      message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:26Z"
    - latency: 2.009009ms
      message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:26Z"
    - latency: 2.052926ms
      message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:01:26Z"
    - latency: 1.865457ms
      message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:00:26Z"
    - latency: 1.93101ms
      message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:59:26Z"
    - latency: 2.015138ms
      message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:58:26Z"
    - latency: 1.886707ms
      message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:26Z"
    - latency: 1.959417ms
      message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:56:26Z"
    - latency: 2.077703ms
      message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:55:26Z"
    - latency: 1.914795ms
      message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:54:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:42:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-52-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-52.ec2.internal
      uid: 0ab14dd6-435b-4def-a4ef-97955eb810a9
    resourceVersion: "20613"
    uid: 3e1dd9f1-5541-46cb-9ec2-39ef8595aad1
  spec:
    sourcePod: network-check-source-989f8b8dc-hsdkl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:48:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 926.762µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:26Z"
    - latency: 1.917157ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:06:26Z"
    - latency: 1.606648ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:26Z"
    - latency: 1.697453ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:05:26Z"
    - latency: 962.634µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:26Z"
    - latency: 1.607944ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:04:26Z"
    - latency: 1.093676ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:26Z"
    - latency: 1.670901ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:03:26Z"
    - latency: 740.251µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:26Z"
    - latency: 1.550892ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:02:26Z"
kind: List
metadata:
  resourceVersion: ""