apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:17:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-84-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-84.us-east-2.compute.internal
      uid: 52895cc2-7062-45ac-8a23-15415505828c
    resourceVersion: "123280"
    uid: dbef525c-1310-46b6-83c1-5219d9576e4a
  spec:
    sourcePod: network-check-source-6f78d59f99-bvcb4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:24:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.793869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:06:47Z"
    - latency: 1.004419ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:05:47Z"
    - latency: 1.371104ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:04:47Z"
    - latency: 804.6µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:03:47Z"
    - latency: 957.521µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:02:47Z"
    - latency: 1.127857ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:47Z"
    - latency: 1.047761ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:00:47Z"
    - latency: 1.379108ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:47Z"
    - latency: 2.152258ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:47Z"
    - latency: 1.215649ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:17:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-84-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-84.us-east-2.compute.internal
      uid: 52895cc2-7062-45ac-8a23-15415505828c
    resourceVersion: "122400"
    uid: 9e5902f6-a14a-4cbe-9689-1d2f29f7ba1b
  spec:
    sourcePod: network-check-source-6f78d59f99-bvcb4
    targetEndpoint: a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:23:47Z"
      message: 'load-balancer-api-external: tcp connection to a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.633272ms
      message: 'load-balancer-api-external: tcp connection to a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:05:47Z"
    - latency: 8.155781ms
      message: 'load-balancer-api-external: resolved host name a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:05:47Z"
    - latency: 6.708432ms
      message: 'load-balancer-api-external: tcp connection to a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:04:47Z"
    - latency: 8.401234ms
      message: 'load-balancer-api-external: resolved host name a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:04:47Z"
    - latency: 5.591315ms
      message: 'load-balancer-api-external: tcp connection to a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:03:47Z"
    - latency: 9.223468ms
      message: 'load-balancer-api-external: resolved host name a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:03:47Z"
    - latency: 5.797895ms
      message: 'load-balancer-api-external: tcp connection to a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:02:47Z"
    - latency: 7.850239ms
      message: 'load-balancer-api-external: resolved host name a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:02:47Z"
    - latency: 5.25009ms
      message: 'load-balancer-api-external: tcp connection to a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:47Z"
    - latency: 7.13313ms
      message: 'load-balancer-api-external: resolved host name a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:01:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:17:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-84-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-84.us-east-2.compute.internal
      uid: 52895cc2-7062-45ac-8a23-15415505828c
    resourceVersion: "122403"
    uid: 19bae527-0762-4a7a-bf70-c9acf40173af
  spec:
    sourcePod: network-check-source-6f78d59f99-bvcb4
    targetEndpoint: a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:23:47Z"
      message: 'load-balancer-api-internal: tcp connection to a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 21.098817ms
      message: 'load-balancer-api-internal: tcp connection to a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:05:47Z"
    - latency: 8.103662ms
      message: 'load-balancer-api-internal: resolved host name a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:05:47Z"
    - latency: 5.909529ms
      message: 'load-balancer-api-internal: tcp connection to a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:04:47Z"
    - latency: 8.480614ms
      message: 'load-balancer-api-internal: resolved host name a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:04:47Z"
    - latency: 6.004996ms
      message: 'load-balancer-api-internal: tcp connection to a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:03:47Z"
    - latency: 9.287821ms
      message: 'load-balancer-api-internal: resolved host name a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:03:47Z"
    - latency: 6.498796ms
      message: 'load-balancer-api-internal: tcp connection to a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:02:47Z"
    - latency: 7.936184ms
      message: 'load-balancer-api-internal: resolved host name a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:02:47Z"
    - latency: 5.058697ms
      message: 'load-balancer-api-internal: tcp connection to a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:47Z"
    - latency: 7.225029ms
      message: 'load-balancer-api-internal: resolved host name a614d4777785644178ec5525ab73963d-10cce16cdb1eb965.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:01:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:17:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-84-to-network-check-target-ip-10-0-137-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-84.us-east-2.compute.internal
      uid: 52895cc2-7062-45ac-8a23-15415505828c
    resourceVersion: "123277"
    uid: 61f57a53-aa58-43f0-97ae-6bd25caf41af
  spec:
    sourcePod: network-check-source-6f78d59f99-bvcb4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:24:47Z"
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.015791ms
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:06:47Z"
    - latency: 933.501µs
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:05:47Z"
    - latency: 852.346µs
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:04:47Z"
    - latency: 1.072704ms
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:03:47Z"
    - latency: 1.222679ms
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:02:47Z"
    - latency: 869.111µs
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:47Z"
    - latency: 1.574428ms
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:00:47Z"
    - latency: 1.128996ms
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:47Z"
    - latency: 2.774315ms
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:47Z"
    - latency: 951.161µs
      message: 'network-check-target-ip-10-0-137-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:17:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-84-to-network-check-target-ip-10-0-138-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-84.us-east-2.compute.internal
      uid: 52895cc2-7062-45ac-8a23-15415505828c
    resourceVersion: "123278"
    uid: cbb71d98-1b0a-498a-9c76-884241bf4659
  spec:
    sourcePod: network-check-source-6f78d59f99-bvcb4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:24:47Z"
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.412439ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:06:47Z"
    - latency: 2.1812ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:05:47Z"
    - latency: 2.061234ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:04:47Z"
    - latency: 2.427092ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:03:47Z"
    - latency: 2.065401ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:02:47Z"
    - latency: 2.229533ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:47Z"
    - latency: 2.216588ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:00:47Z"
    - latency: 2.557698ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:47Z"
    - latency: 6.482406ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:47Z"
    - latency: 2.424371ms
      message: 'network-check-target-ip-10-0-138-233: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:17:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-84-to-network-check-target-ip-10-0-140-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-84.us-east-2.compute.internal
      uid: 52895cc2-7062-45ac-8a23-15415505828c
    resourceVersion: "123279"
    uid: 667895fe-cca7-44e5-b44e-93e349d670e0
  spec:
    sourcePod: network-check-source-6f78d59f99-bvcb4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:24:47Z"
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.156376ms
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:06:47Z"
    - latency: 2.124273ms
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:05:47Z"
    - latency: 2.061161ms
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:04:47Z"
    - latency: 2.064782ms
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:03:47Z"
    - latency: 2.022887ms
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:02:47Z"
    - latency: 1.933371ms
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:47Z"
    - latency: 2.030993ms
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:00:47Z"
    - latency: 2.069233ms
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:47Z"
    - latency: 1.769123ms
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:47Z"
    - latency: 2.157947ms
      message: 'network-check-target-ip-10-0-140-127: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:17:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-84-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-84.us-east-2.compute.internal
      uid: 52895cc2-7062-45ac-8a23-15415505828c
    resourceVersion: "122399"
    uid: 42535494-f0d7-43d0-8b05-32dd7bb6d734
  spec:
    sourcePod: network-check-source-6f78d59f99-bvcb4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:23:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.034258ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:05:47Z"
    - latency: 1.709074ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:05:47Z"
    - latency: 971.8µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:04:47Z"
    - latency: 1.831917ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:04:47Z"
    - latency: 968.488µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:03:47Z"
    - latency: 2.397415ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:03:47Z"
    - latency: 807.343µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:02:47Z"
    - latency: 2.229264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:02:47Z"
    - latency: 968.478µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:47Z"
    - latency: 1.892279ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:01:47Z"
kind: List
metadata:
  resourceVersion: ""