apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:48:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-198-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-198.ec2.internal
      uid: f58b7d57-a75e-42ac-ae64-449cedb2b86c
    resourceVersion: "48380"
    uid: 668a97b8-f608-4f65-86ea-0df7956456af
  spec:
    sourcePod: network-check-source-989f8b8dc-45nzs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:55:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.030284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:16:34Z"
    - latency: 936.883µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:15:34Z"
    - latency: 1.18149ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:14:34Z"
    - latency: 892.2µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:13:34Z"
    - latency: 932.9µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:12:34Z"
    - latency: 1.182648ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:11:34Z"
    - latency: 1.077509ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:10:34Z"
    - latency: 1.11124ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:09:34Z"
    - latency: 826.965µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:08:34Z"
    - latency: 950.232µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:07:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:48:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-198-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-198.ec2.internal
      uid: f58b7d57-a75e-42ac-ae64-449cedb2b86c
    resourceVersion: "50932"
    uid: 1533281f-906b-4b86-aa49-9f5b9cf00565
  spec:
    sourcePod: network-check-source-989f8b8dc-45nzs
    targetEndpoint: a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:54:34Z"
      message: 'load-balancer-api-external: tcp connection to a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.801208ms
      message: 'load-balancer-api-external: tcp connection to a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:18:34Z"
    - latency: 8.952133ms
      message: 'load-balancer-api-external: resolved host name a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:18:34Z"
    - latency: 4.170638ms
      message: 'load-balancer-api-external: tcp connection to a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:17:34Z"
    - latency: 8.115266ms
      message: 'load-balancer-api-external: resolved host name a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:17:34Z"
    - latency: 4.527212ms
      message: 'load-balancer-api-external: tcp connection to a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:16:34Z"
    - latency: 8.454677ms
      message: 'load-balancer-api-external: resolved host name a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:16:34Z"
    - latency: 4.536219ms
      message: 'load-balancer-api-external: tcp connection to a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:15:34Z"
    - latency: 9.014457ms
      message: 'load-balancer-api-external: resolved host name a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:15:34Z"
    - latency: 5.159165ms
      message: 'load-balancer-api-external: tcp connection to a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:14:34Z"
    - latency: 8.103188ms
      message: 'load-balancer-api-external: resolved host name a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:14:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:48:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-198-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-198.ec2.internal
      uid: f58b7d57-a75e-42ac-ae64-449cedb2b86c
    resourceVersion: "50931"
    uid: 775a0dd1-e991-4de1-876e-d39da42007ab
  spec:
    sourcePod: network-check-source-989f8b8dc-45nzs
    targetEndpoint: a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:54:34Z"
      message: 'load-balancer-api-internal: tcp connection to a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.856486ms
      message: 'load-balancer-api-internal: tcp connection to a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:18:34Z"
    - latency: 8.893422ms
      message: 'load-balancer-api-internal: resolved host name a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:18:34Z"
    - latency: 4.16286ms
      message: 'load-balancer-api-internal: tcp connection to a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:17:34Z"
    - latency: 8.040198ms
      message: 'load-balancer-api-internal: resolved host name a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:17:34Z"
    - latency: 5.414234ms
      message: 'load-balancer-api-internal: tcp connection to a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:16:34Z"
    - latency: 8.343989ms
      message: 'load-balancer-api-internal: resolved host name a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:16:34Z"
    - latency: 4.597868ms
      message: 'load-balancer-api-internal: tcp connection to a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:15:34Z"
    - latency: 8.914716ms
      message: 'load-balancer-api-internal: resolved host name a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:15:34Z"
    - latency: 4.351048ms
      message: 'load-balancer-api-internal: tcp connection to a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:14:34Z"
    - latency: 7.998668ms
      message: 'load-balancer-api-internal: resolved host name a8a608945b3314ffebad5db8b85d057b-ad30b3962d0e08e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:14:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:48:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-198-to-network-check-target-ip-10-0-129-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-198.ec2.internal
      uid: f58b7d57-a75e-42ac-ae64-449cedb2b86c
    resourceVersion: "48377"
    uid: a1f01300-7aa5-46ba-8b7d-35836b712461
  spec:
    sourcePod: network-check-source-989f8b8dc-45nzs
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:55:34Z"
      message: 'network-check-target-ip-10-0-129-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.298083ms
      message: 'network-check-target-ip-10-0-129-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:16:34Z"
    - latency: 916.016µs
      message: 'network-check-target-ip-10-0-129-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:15:34Z"
    - latency: 833.504µs
      message: 'network-check-target-ip-10-0-129-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:14:34Z"
    - latency: 906.867µs
      message: 'network-check-target-ip-10-0-129-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:13:34Z"
    - latency: 886.099µs
      message: 'network-check-target-ip-10-0-129-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:12:34Z"
    - latency: 920.287µs
      message: 'network-check-target-ip-10-0-129-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:11:34Z"
    - latency: 778.255µs
      message: 'network-check-target-ip-10-0-129-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:10:34Z"
    - latency: 930.933µs
      message: 'network-check-target-ip-10-0-129-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:09:34Z"
    - latency: 1.302464ms
      message: 'network-check-target-ip-10-0-129-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:08:34Z"
    - latency: 875.01µs
      message: 'network-check-target-ip-10-0-129-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:07:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:48:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-198-to-network-check-target-ip-10-0-131-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-198.ec2.internal
      uid: f58b7d57-a75e-42ac-ae64-449cedb2b86c
    resourceVersion: "48379"
    uid: 384524b2-2524-481b-b3c0-3cee2084bd1c
  spec:
    sourcePod: network-check-source-989f8b8dc-45nzs
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:55:34Z"
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.043932ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:16:34Z"
    - latency: 2.17991ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:15:34Z"
    - latency: 1.789085ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:14:34Z"
    - latency: 2.138588ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:13:34Z"
    - latency: 2.061808ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:12:34Z"
    - latency: 2.122093ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:11:34Z"
    - latency: 1.826244ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:10:34Z"
    - latency: 2.050477ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:09:34Z"
    - latency: 1.907749ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:08:34Z"
    - latency: 2.001849ms
      message: 'network-check-target-ip-10-0-131-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:07:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:48:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-198-to-network-check-target-ip-10-0-133-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-198.ec2.internal
      uid: f58b7d57-a75e-42ac-ae64-449cedb2b86c
    resourceVersion: "48378"
    uid: 007d569e-578c-40a1-b718-02fde3054160
  spec:
    sourcePod: network-check-source-989f8b8dc-45nzs
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:55:34Z"
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.286735ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:16:34Z"
    - latency: 2.266252ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:15:34Z"
    - latency: 1.840944ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:14:34Z"
    - latency: 2.421762ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:13:34Z"
    - latency: 2.391228ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:12:34Z"
    - latency: 2.19205ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:11:34Z"
    - latency: 2.801697ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:10:34Z"
    - latency: 2.327104ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:09:34Z"
    - latency: 1.884981ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:08:34Z"
    - latency: 2.178383ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:07:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T19:48:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-198-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-198.ec2.internal
      uid: f58b7d57-a75e-42ac-ae64-449cedb2b86c
    resourceVersion: "50930"
    uid: c682febc-3215-4eec-8d25-49b3bb2bcada
  spec:
    sourcePod: network-check-source-989f8b8dc-45nzs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T19:54:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 753.579µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:18:34Z"
    - latency: 1.850937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:18:34Z"
    - latency: 1.428181ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:17:34Z"
    - latency: 1.657348ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:17:34Z"
    - latency: 1.080335ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:16:34Z"
    - latency: 1.736586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:16:34Z"
    - latency: 873.865µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:15:34Z"
    - latency: 2.017804ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:15:34Z"
    - latency: 891.535µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:14:34Z"
    - latency: 1.680186ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:14:34Z"
kind: List
metadata:
  resourceVersion: ""