apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T21:32:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-253-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-253.ec2.internal
      uid: d22465e2-fa4f-4b5a-8bb8-1cca4db498c2
    resourceVersion: "67964"
    uid: fce7316d-bc66-46c5-ba1f-c6f7eaea77a7
  spec:
    sourcePod: network-check-source-6f78d59f99-m2hhx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T21:39:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 932.11µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:07:20Z"
    - latency: 1.360168ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:06:20Z"
    - latency: 1.385466ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:05:20Z"
    - latency: 1.293216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:04:20Z"
    - latency: 4.372363ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:03:20Z"
    - latency: 1.396228ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:02:20Z"
    - latency: 969.208µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:01:20Z"
    - latency: 1.587658ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:00:20Z"
    - latency: 980.67µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:59:20Z"
    - latency: 1.203664ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:58:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T21:32:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-253-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-253.ec2.internal
      uid: d22465e2-fa4f-4b5a-8bb8-1cca4db498c2
    resourceVersion: "68492"
    uid: 3653920e-5359-41e4-b013-f506a88d455c
  spec:
    sourcePod: network-check-source-6f78d59f99-m2hhx
    targetEndpoint: a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T21:38:20Z"
      message: 'load-balancer-api-external: tcp connection to a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.461603ms
      message: 'load-balancer-api-external: tcp connection to a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:08:20Z"
    - latency: 7.450514ms
      message: 'load-balancer-api-external: resolved host name a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:08:20Z"
    - latency: 17.794331ms
      message: 'load-balancer-api-external: tcp connection to a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:07:20Z"
    - latency: 7.22632ms
      message: 'load-balancer-api-external: resolved host name a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:07:20Z"
    - latency: 18.384187ms
      message: 'load-balancer-api-external: tcp connection to a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:06:20Z"
    - latency: 7.933795ms
      message: 'load-balancer-api-external: resolved host name a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:06:20Z"
    - latency: 17.155064ms
      message: 'load-balancer-api-external: tcp connection to a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:05:20Z"
    - latency: 7.092599ms
      message: 'load-balancer-api-external: resolved host name a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:05:20Z"
    - latency: 16.424538ms
      message: 'load-balancer-api-external: tcp connection to a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:04:20Z"
    - latency: 7.891664ms
      message: 'load-balancer-api-external: resolved host name a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:04:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T21:32:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-253-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-253.ec2.internal
      uid: d22465e2-fa4f-4b5a-8bb8-1cca4db498c2
    resourceVersion: "68491"
    uid: d00234c3-2d1a-45cd-ba1e-4f9328ba0f1a
  spec:
    sourcePod: network-check-source-6f78d59f99-m2hhx
    targetEndpoint: a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T21:38:20Z"
      message: 'load-balancer-api-internal: tcp connection to a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.882429ms
      message: 'load-balancer-api-internal: tcp connection to a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:08:20Z"
    - latency: 7.405033ms
      message: 'load-balancer-api-internal: resolved host name a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:08:20Z"
    - latency: 17.577808ms
      message: 'load-balancer-api-internal: tcp connection to a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:07:20Z"
    - latency: 7.23969ms
      message: 'load-balancer-api-internal: resolved host name a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:07:20Z"
    - latency: 18.385894ms
      message: 'load-balancer-api-internal: tcp connection to a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:06:20Z"
    - latency: 7.856993ms
      message: 'load-balancer-api-internal: resolved host name a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:06:20Z"
    - latency: 18.203284ms
      message: 'load-balancer-api-internal: tcp connection to a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:05:20Z"
    - latency: 7.039338ms
      message: 'load-balancer-api-internal: resolved host name a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:05:20Z"
    - latency: 17.500282ms
      message: 'load-balancer-api-internal: tcp connection to a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:04:20Z"
    - latency: 7.847556ms
      message: 'load-balancer-api-internal: resolved host name a49e8358272f945db9784b89257d4b71-991a22b5264f1a75.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:04:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T21:32:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-253-to-network-check-target-ip-10-0-131-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-253.ec2.internal
      uid: d22465e2-fa4f-4b5a-8bb8-1cca4db498c2
    resourceVersion: "67961"
    uid: b9586905-7b27-4e8e-a22f-89ee93ec5cc8
  spec:
    sourcePod: network-check-source-6f78d59f99-m2hhx
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T21:39:20Z"
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 877.151µs
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:07:20Z"
    - latency: 1.372425ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:06:20Z"
    - latency: 881.005µs
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:05:20Z"
    - latency: 908.864µs
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:04:20Z"
    - latency: 30.490499ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:03:20Z"
    - latency: 906.469µs
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:02:20Z"
    - latency: 1.832783ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:01:20Z"
    - latency: 2.034698ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:00:20Z"
    - latency: 1.086938ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:59:20Z"
    - latency: 1.051572ms
      message: 'network-check-target-ip-10-0-131-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:58:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T21:32:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-253-to-network-check-target-ip-10-0-137-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-253.ec2.internal
      uid: d22465e2-fa4f-4b5a-8bb8-1cca4db498c2
    resourceVersion: "67963"
    uid: f452f21e-b2bb-4279-898d-0dfc09cb71ad
  spec:
    sourcePod: network-check-source-6f78d59f99-m2hhx
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T21:39:20Z"
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.441107ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:07:20Z"
    - latency: 2.368255ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:06:20Z"
    - latency: 2.478281ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:05:20Z"
    - latency: 2.881902ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:04:20Z"
    - latency: 30.018069ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:03:20Z"
    - latency: 4.545473ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:02:20Z"
    - latency: 3.095569ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:01:20Z"
    - latency: 2.372528ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:00:20Z"
    - latency: 2.332745ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:59:20Z"
    - latency: 2.614136ms
      message: 'network-check-target-ip-10-0-137-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:58:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T21:32:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-253-to-network-check-target-ip-10-0-142-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-253.ec2.internal
      uid: d22465e2-fa4f-4b5a-8bb8-1cca4db498c2
    resourceVersion: "67962"
    uid: 53451432-fdfd-43f0-94ec-d477ba879dd4
  spec:
    sourcePod: network-check-source-6f78d59f99-m2hhx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T21:39:20Z"
      message: 'network-check-target-ip-10-0-142-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.42347ms
      message: 'network-check-target-ip-10-0-142-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:07:20Z"
    - latency: 2.252192ms
      message: 'network-check-target-ip-10-0-142-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:06:20Z"
    - latency: 2.08549ms
      message: 'network-check-target-ip-10-0-142-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:05:20Z"
    - latency: 2.800265ms
      message: 'network-check-target-ip-10-0-142-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:04:20Z"
    - latency: 29.787487ms
      message: 'network-check-target-ip-10-0-142-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:03:20Z"
    - latency: 2.434745ms
      message: 'network-check-target-ip-10-0-142-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:02:20Z"
    - latency: 2.631352ms
      message: 'network-check-target-ip-10-0-142-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:01:20Z"
    - latency: 2.887033ms
      message: 'network-check-target-ip-10-0-142-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:00:20Z"
    - latency: 2.408254ms
      message: 'network-check-target-ip-10-0-142-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:59:20Z"
    - latency: 2.409268ms
      message: 'network-check-target-ip-10-0-142-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T21:58:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T21:32:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-253-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-253.ec2.internal
      uid: d22465e2-fa4f-4b5a-8bb8-1cca4db498c2
    resourceVersion: "68490"
    uid: a337fa10-e35b-4c85-af64-dbb08b10aa28
  spec:
    sourcePod: network-check-source-6f78d59f99-m2hhx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T21:38:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.381884ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:08:20Z"
    - latency: 2.064248ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:08:20Z"
    - latency: 905.333µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:07:20Z"
    - latency: 1.982454ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:07:20Z"
    - latency: 1.327629ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:06:20Z"
    - latency: 1.845467ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:06:20Z"
    - latency: 823.273µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:05:20Z"
    - latency: 1.850282ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:05:20Z"
    - latency: 955.182µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T22:04:20Z"
    - latency: 3.087434ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T22:04:20Z"
kind: List
metadata:
  resourceVersion: ""