apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T01:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-179-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-179.us-east-2.compute.internal
      uid: 1db57de5-ec57-4fcb-8a64-9fff91471f98
    resourceVersion: "70420"
    uid: bca9a09c-f867-486c-9a09-5ce455d07045
  spec:
    sourcePod: network-check-source-6f78d59f99-jwv8k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T01:07:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.113578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:28:50Z"
    - latency: 1.364597ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:50Z"
    - latency: 1.257331ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:50Z"
    - latency: 880.877µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:50Z"
    - latency: 902.448µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:50Z"
    - latency: 867.478µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:23:50Z"
    - latency: 1.101392ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:22:50Z"
    - latency: 1.128253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:21:50Z"
    - latency: 1.202925ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:20:50Z"
    - latency: 1.00077ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T01:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-179-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-179.us-east-2.compute.internal
      uid: 1db57de5-ec57-4fcb-8a64-9fff91471f98
    resourceVersion: "73503"
    uid: 469821be-ecf9-4dda-8e10-baada6a5df75
  spec:
    sourcePod: network-check-source-6f78d59f99-jwv8k
    targetEndpoint: aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T01:06:50Z"
      message: 'load-balancer-api-external: tcp connection to aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.047863ms
      message: 'load-balancer-api-external: tcp connection to aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:30:50Z"
    - latency: 20.150703ms
      message: 'load-balancer-api-external: resolved host name aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:30:50Z"
    - latency: 5.449051ms
      message: 'load-balancer-api-external: tcp connection to aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:29:50Z"
    - latency: 7.503454ms
      message: 'load-balancer-api-external: resolved host name aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:29:50Z"
    - latency: 6.071309ms
      message: 'load-balancer-api-external: tcp connection to aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:28:50Z"
    - latency: 7.478857ms
      message: 'load-balancer-api-external: resolved host name aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:28:50Z"
    - latency: 5.445602ms
      message: 'load-balancer-api-external: tcp connection to aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:50Z"
    - latency: 6.829239ms
      message: 'load-balancer-api-external: resolved host name aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:27:50Z"
    - latency: 5.037764ms
      message: 'load-balancer-api-external: tcp connection to aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:50Z"
    - latency: 6.873662ms
      message: 'load-balancer-api-external: resolved host name aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:26:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T01:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-179-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-179.us-east-2.compute.internal
      uid: 1db57de5-ec57-4fcb-8a64-9fff91471f98
    resourceVersion: "73502"
    uid: ac3ab7ea-b564-49de-ad1a-570b349fe8df
  spec:
    sourcePod: network-check-source-6f78d59f99-jwv8k
    targetEndpoint: aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T01:06:50Z"
      message: 'load-balancer-api-internal: tcp connection to aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.06658ms
      message: 'load-balancer-api-internal: tcp connection to aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:30:50Z"
    - latency: 19.156359ms
      message: 'load-balancer-api-internal: resolved host name aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:30:50Z"
    - latency: 5.14181ms
      message: 'load-balancer-api-internal: tcp connection to aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:29:50Z"
    - latency: 7.546065ms
      message: 'load-balancer-api-internal: resolved host name aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:29:50Z"
    - latency: 6.176645ms
      message: 'load-balancer-api-internal: tcp connection to aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:28:50Z"
    - latency: 7.547441ms
      message: 'load-balancer-api-internal: resolved host name aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:28:50Z"
    - latency: 6.285781ms
      message: 'load-balancer-api-internal: tcp connection to aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:50Z"
    - latency: 6.783507ms
      message: 'load-balancer-api-internal: resolved host name aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:27:50Z"
    - latency: 5.481235ms
      message: 'load-balancer-api-internal: tcp connection to aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:50Z"
    - latency: 6.83088ms
      message: 'load-balancer-api-internal: resolved host name aeebcd43163e042e1b1c9c2fdd8caf85-bd512897f4cb424d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:26:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T01:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-179-to-network-check-target-ip-10-0-130-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-179.us-east-2.compute.internal
      uid: 1db57de5-ec57-4fcb-8a64-9fff91471f98
    resourceVersion: "70419"
    uid: b879662a-2f33-4b85-85f7-9c4b599fd40c
  spec:
    sourcePod: network-check-source-6f78d59f99-jwv8k
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T01:07:50Z"
      message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.53912ms
      message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:28:50Z"
    - latency: 2.272343ms
      message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:50Z"
    - latency: 1.810831ms
      message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:50Z"
    - latency: 2.190203ms
      message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:50Z"
    - latency: 2.908428ms
      message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:50Z"
    - latency: 2.082962ms
      message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:23:50Z"
    - latency: 2.403295ms
      message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:22:50Z"
    - latency: 2.396744ms
      message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:21:50Z"
    - latency: 2.309185ms
      message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:20:50Z"
    - latency: 2.241595ms
      message: 'network-check-target-ip-10-0-130-39: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T01:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-179-to-network-check-target-ip-10-0-132-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-179.us-east-2.compute.internal
      uid: 1db57de5-ec57-4fcb-8a64-9fff91471f98
    resourceVersion: "70417"
    uid: cc33c9c7-c293-4ae5-8852-d4e35a16054b
  spec:
    sourcePod: network-check-source-6f78d59f99-jwv8k
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T01:07:50Z"
      message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 856.476µs
      message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:28:50Z"
    - latency: 927.992µs
      message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:50Z"
    - latency: 855.994µs
      message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:50Z"
    - latency: 1.308401ms
      message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:50Z"
    - latency: 1.091632ms
      message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:50Z"
    - latency: 1.164412ms
      message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:23:50Z"
    - latency: 1.824275ms
      message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:22:50Z"
    - latency: 962.676µs
      message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:21:50Z"
    - latency: 915.268µs
      message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:20:50Z"
    - latency: 1.047208ms
      message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T01:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-179-to-network-check-target-ip-10-0-140-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-179.us-east-2.compute.internal
      uid: 1db57de5-ec57-4fcb-8a64-9fff91471f98
    resourceVersion: "70418"
    uid: 08be6fb7-5af3-4452-b0a1-c411aa0d396f
  spec:
    sourcePod: network-check-source-6f78d59f99-jwv8k
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T01:07:50Z"
      message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.204195ms
      message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:28:50Z"
    - latency: 2.373686ms
      message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:50Z"
    - latency: 2.210269ms
      message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:50Z"
    - latency: 1.77303ms
      message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:50Z"
    - latency: 2.168078ms
      message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:50Z"
    - latency: 2.18929ms
      message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:23:50Z"
    - latency: 2.152529ms
      message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:22:50Z"
    - latency: 2.14176ms
      message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:21:50Z"
    - latency: 1.934463ms
      message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:20:50Z"
    - latency: 1.830224ms
      message: 'network-check-target-ip-10-0-140-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T01:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-179-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-179.us-east-2.compute.internal
      uid: 1db57de5-ec57-4fcb-8a64-9fff91471f98
    resourceVersion: "73501"
    uid: cb8d5447-6ebf-4251-8eb6-74e21551d8cb
  spec:
    sourcePod: network-check-source-6f78d59f99-jwv8k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T01:06:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.467655ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:30:50Z"
    - latency: 12.043592ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:30:50Z"
    - latency: 1.072546ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:29:50Z"
    - latency: 1.672179ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:29:50Z"
    - latency: 997.965µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:28:50Z"
    - latency: 2.023197ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:28:50Z"
    - latency: 1.33987ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:50Z"
    - latency: 1.99932ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:27:50Z"
    - latency: 960.318µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:50Z"
    - latency: 1.81046ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:26:50Z"
kind: List
metadata:
  resourceVersion: ""