apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.us-west-2.compute.internal
      uid: afe0b8c4-d821-4c86-8f13-e43570dd96f5
    resourceVersion: "32778"
    uid: 18295b6e-0947-43a2-9c1f-de41acbc1dda
  spec:
    sourcePod: network-check-source-6f78d59f99-8248m
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:47:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.241µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:36:00Z"
    - latency: 1.216068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:35:00Z"
    - latency: 929.022µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:00Z"
    - latency: 773.143µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:33:00Z"
    - latency: 1.053396ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:32:00Z"
    - latency: 989.686µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:31:00Z"
    - latency: 1.049731ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:30:00Z"
    - latency: 1.15543ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:29:00Z"
    - latency: 1.590274ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:28:00Z"
    - latency: 1.030968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:27:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.us-west-2.compute.internal
      uid: afe0b8c4-d821-4c86-8f13-e43570dd96f5
    resourceVersion: "36147"
    uid: 16181e88-6866-401a-b8e8-6e1ed6e4613e
  spec:
    sourcePod: network-check-source-6f78d59f99-8248m
    targetEndpoint: a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:00Z"
      message: 'load-balancer-api-external: tcp connection to a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.511726ms
      message: 'load-balancer-api-external: tcp connection to a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:40:00Z"
    - latency: 7.326212ms
      message: 'load-balancer-api-external: resolved host name a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:40:00Z"
    - latency: 52.02896ms
      message: 'load-balancer-api-external: tcp connection to a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:39:00Z"
    - latency: 8.356368ms
      message: 'load-balancer-api-external: resolved host name a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:39:00Z"
    - latency: 51.845378ms
      message: 'load-balancer-api-external: tcp connection to a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:00Z"
    - latency: 10.387358ms
      message: 'load-balancer-api-external: resolved host name a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:38:00Z"
    - latency: 54.63564ms
      message: 'load-balancer-api-external: tcp connection to a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:37:00Z"
    - latency: 6.444666ms
      message: 'load-balancer-api-external: resolved host name a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:37:00Z"
    - latency: 55.82143ms
      message: 'load-balancer-api-external: tcp connection to a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:36:00Z"
    - latency: 8.826951ms
      message: 'load-balancer-api-external: resolved host name a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:36:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.us-west-2.compute.internal
      uid: afe0b8c4-d821-4c86-8f13-e43570dd96f5
    resourceVersion: "36148"
    uid: 977ca9e9-8f3b-403b-a5ef-6dcc8eb49808
  spec:
    sourcePod: network-check-source-6f78d59f99-8248m
    targetEndpoint: a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:00Z"
      message: 'load-balancer-api-internal: tcp connection to a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 66.917997ms
      message: 'load-balancer-api-internal: tcp connection to a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:40:00Z"
    - latency: 7.405364ms
      message: 'load-balancer-api-internal: resolved host name a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:40:00Z"
    - latency: 55.570604ms
      message: 'load-balancer-api-internal: tcp connection to a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:39:00Z"
    - latency: 8.455678ms
      message: 'load-balancer-api-internal: resolved host name a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:39:00Z"
    - latency: 51.814198ms
      message: 'load-balancer-api-internal: tcp connection to a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:00Z"
    - latency: 10.466067ms
      message: 'load-balancer-api-internal: resolved host name a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:38:00Z"
    - latency: 54.672818ms
      message: 'load-balancer-api-internal: tcp connection to a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:37:00Z"
    - latency: 6.507835ms
      message: 'load-balancer-api-internal: resolved host name a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:37:00Z"
    - latency: 51.552369ms
      message: 'load-balancer-api-internal: tcp connection to a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:36:00Z"
    - latency: 8.888489ms
      message: 'load-balancer-api-internal: resolved host name a97600e569e5c4a9eafb16c9ff6ff0f2-36f3c3322d66c93d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:36:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-network-check-target-ip-10-0-129-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.us-west-2.compute.internal
      uid: afe0b8c4-d821-4c86-8f13-e43570dd96f5
    resourceVersion: "32775"
    uid: f90a2891-6628-4172-a18a-23b24c01c72a
  spec:
    sourcePod: network-check-source-6f78d59f99-8248m
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:47:00Z"
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 909.757µs
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:36:00Z"
    - latency: 1.311659ms
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:35:00Z"
    - latency: 919.517µs
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:00Z"
    - latency: 814.045µs
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:33:00Z"
    - latency: 836.732µs
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:32:00Z"
    - latency: 893.821µs
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:31:00Z"
    - latency: 933.528µs
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:30:00Z"
    - latency: 897.637µs
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:29:00Z"
    - latency: 824.088µs
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:28:00Z"
    - latency: 909.183µs
      message: 'network-check-target-ip-10-0-129-207: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:27:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-network-check-target-ip-10-0-134-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.us-west-2.compute.internal
      uid: afe0b8c4-d821-4c86-8f13-e43570dd96f5
    resourceVersion: "32776"
    uid: 33b9e796-7ecf-48e3-8354-957c03894486
  spec:
    sourcePod: network-check-source-6f78d59f99-8248m
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:47:00Z"
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.992735ms
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:36:00Z"
    - latency: 1.786968ms
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:35:00Z"
    - latency: 1.859532ms
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:00Z"
    - latency: 1.830591ms
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:33:00Z"
    - latency: 1.989971ms
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:32:00Z"
    - latency: 1.840375ms
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:31:00Z"
    - latency: 1.970973ms
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:30:00Z"
    - latency: 1.967855ms
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:29:00Z"
    - latency: 1.651697ms
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:28:00Z"
    - latency: 1.67734ms
      message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:27:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-network-check-target-ip-10-0-135-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.us-west-2.compute.internal
      uid: afe0b8c4-d821-4c86-8f13-e43570dd96f5
    resourceVersion: "32777"
    uid: 4f983a76-52bc-4c55-8422-02917ed96625
  spec:
    sourcePod: network-check-source-6f78d59f99-8248m
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:47:00Z"
      message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.618753ms
      message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:36:00Z"
    - latency: 2.619471ms
      message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:35:00Z"
    - latency: 2.532704ms
      message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:34:00Z"
    - latency: 2.0461ms
      message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:33:00Z"
    - latency: 2.003721ms
      message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:32:00Z"
    - latency: 2.826139ms
      message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:31:00Z"
    - latency: 2.41898ms
      message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:30:00Z"
    - latency: 2.483944ms
      message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:29:00Z"
    - latency: 2.160278ms
      message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:28:00Z"
    - latency: 2.459667ms
      message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:27:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:40:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-207-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-207.us-west-2.compute.internal
      uid: afe0b8c4-d821-4c86-8f13-e43570dd96f5
    resourceVersion: "36146"
    uid: a3d13f45-0f9e-4ba2-9eee-7c7cdcdedf0d
  spec:
    sourcePod: network-check-source-6f78d59f99-8248m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.773µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:40:00Z"
    - latency: 1.764182ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:40:00Z"
    - latency: 932.67µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:39:00Z"
    - latency: 1.919148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:39:00Z"
    - latency: 948.475µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:38:00Z"
    - latency: 1.740415ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:38:00Z"
    - latency: 980.27µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:37:00Z"
    - latency: 1.801606ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:37:00Z"
    - latency: 1.28613ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:36:00Z"
    - latency: 1.883408ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:36:00Z"
kind: List
metadata:
  resourceVersion: ""