apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:39:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-122-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-122.ec2.internal
      uid: 80f881d6-f16f-4ec5-ae44-c2797547f299
    resourceVersion: "53491"
    uid: a30b3e33-660f-4563-b903-c94533bdc1ce
  spec:
    sourcePod: network-check-source-685456655f-7798s
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:46:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.216412ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:07:08Z"
    - latency: 913.729µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:06:08Z"
    - latency: 779.869µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:05:08Z"
    - latency: 1.156914ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:04:08Z"
    - latency: 790.696µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:03:08Z"
    - latency: 1.123328ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:02:08Z"
    - latency: 1.233552ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:01:08Z"
    - latency: 1.156598ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:00:08Z"
    - latency: 1.681483ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:59:08Z"
    - latency: 1.148242ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:58:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:39:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-122-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-122.ec2.internal
      uid: 80f881d6-f16f-4ec5-ae44-c2797547f299
    resourceVersion: "55307"
    uid: d7cb92c2-b516-49f0-8c41-902d8086e081
  spec:
    sourcePod: network-check-source-685456655f-7798s
    targetEndpoint: aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:45:08Z"
      message: 'load-balancer-api-external: tcp connection to aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.388094ms
      message: 'load-balancer-api-external: tcp connection to aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:09:08Z"
    - latency: 9.250363ms
      message: 'load-balancer-api-external: resolved host name aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:09:08Z"
    - latency: 4.302345ms
      message: 'load-balancer-api-external: tcp connection to aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:08:08Z"
    - latency: 8.383184ms
      message: 'load-balancer-api-external: resolved host name aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:08:08Z"
    - latency: 3.813567ms
      message: 'load-balancer-api-external: tcp connection to aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:07:08Z"
    - latency: 8.69965ms
      message: 'load-balancer-api-external: resolved host name aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:07:08Z"
    - latency: 5.052235ms
      message: 'load-balancer-api-external: tcp connection to aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:06:08Z"
    - latency: 7.585709ms
      message: 'load-balancer-api-external: resolved host name aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:06:08Z"
    - latency: 5.771233ms
      message: 'load-balancer-api-external: tcp connection to aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:05:08Z"
    - latency: 8.59753ms
      message: 'load-balancer-api-external: resolved host name aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:05:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:39:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-122-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-122.ec2.internal
      uid: 80f881d6-f16f-4ec5-ae44-c2797547f299
    resourceVersion: "55308"
    uid: 4573c9ca-1037-4261-bc79-6ea8bb305dda
  spec:
    sourcePod: network-check-source-685456655f-7798s
    targetEndpoint: aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:45:08Z"
      message: 'load-balancer-api-internal: tcp connection to aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.935141ms
      message: 'load-balancer-api-internal: tcp connection to aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:09:08Z"
    - latency: 9.200477ms
      message: 'load-balancer-api-internal: resolved host name aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:09:08Z"
    - latency: 4.355589ms
      message: 'load-balancer-api-internal: tcp connection to aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:08:08Z"
    - latency: 8.298234ms
      message: 'load-balancer-api-internal: resolved host name aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:08:08Z"
    - latency: 4.430061ms
      message: 'load-balancer-api-internal: tcp connection to aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:07:08Z"
    - latency: 8.646032ms
      message: 'load-balancer-api-internal: resolved host name aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:07:08Z"
    - latency: 5.070321ms
      message: 'load-balancer-api-internal: tcp connection to aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:06:08Z"
    - latency: 7.481344ms
      message: 'load-balancer-api-internal: resolved host name aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:06:08Z"
    - latency: 5.035621ms
      message: 'load-balancer-api-internal: tcp connection to aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:05:08Z"
    - latency: 8.538474ms
      message: 'load-balancer-api-internal: resolved host name aac336dbd1d994840a2ae34992a104e5-586bf6be933faf65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:05:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:39:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-122-to-network-check-target-ip-10-0-129-122
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-122.ec2.internal
      uid: 80f881d6-f16f-4ec5-ae44-c2797547f299
    resourceVersion: "53488"
    uid: 15a65ec1-581c-40ce-8aa5-c7d3d5ef6444
  spec:
    sourcePod: network-check-source-685456655f-7798s
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:46:08Z"
      message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 841.339µs
      message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:07:08Z"
    - latency: 1.086619ms
      message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:06:08Z"
    - latency: 1.211391ms
      message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:05:08Z"
    - latency: 1.444365ms
      message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:04:08Z"
    - latency: 974.112µs
      message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:03:08Z"
    - latency: 1.255634ms
      message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:02:08Z"
    - latency: 988.283µs
      message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:01:08Z"
    - latency: 1.480289ms
      message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:00:08Z"
    - latency: 979.858µs
      message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:59:08Z"
    - latency: 1.092555ms
      message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:58:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:39:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-122-to-network-check-target-ip-10-0-140-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-122.ec2.internal
      uid: 80f881d6-f16f-4ec5-ae44-c2797547f299
    resourceVersion: "53490"
    uid: 58133a7b-0263-454c-b95f-c02bae012c6b
  spec:
    sourcePod: network-check-source-685456655f-7798s
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:46:08Z"
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.73534ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:07:08Z"
    - latency: 1.509327ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:06:08Z"
    - latency: 1.8785ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:05:08Z"
    - latency: 2.003771ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:04:08Z"
    - latency: 2.107608ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:03:08Z"
    - latency: 2.503066ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:02:08Z"
    - latency: 2.532793ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:01:08Z"
    - latency: 2.201872ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:00:08Z"
    - latency: 2.211668ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:59:08Z"
    - latency: 2.17963ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:58:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:39:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-122-to-network-check-target-ip-10-0-141-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-122.ec2.internal
      uid: 80f881d6-f16f-4ec5-ae44-c2797547f299
    resourceVersion: "53489"
    uid: 3cd2f216-3316-4555-9b51-5742735b21c4
  spec:
    sourcePod: network-check-source-685456655f-7798s
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:46:08Z"
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.301981ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:07:08Z"
    - latency: 2.115901ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:06:08Z"
    - latency: 2.163156ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:05:08Z"
    - latency: 2.556311ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:04:08Z"
    - latency: 2.297781ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:03:08Z"
    - latency: 2.555646ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:02:08Z"
    - latency: 2.24695ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:01:08Z"
    - latency: 2.360378ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:00:08Z"
    - latency: 2.25236ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:59:08Z"
    - latency: 2.664637ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T17:58:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T17:39:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-122-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-122.ec2.internal
      uid: 80f881d6-f16f-4ec5-ae44-c2797547f299
    resourceVersion: "55306"
    uid: 8a1f3c2c-cfaa-4431-9a43-38806d1f99b3
  spec:
    sourcePod: network-check-source-685456655f-7798s
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T17:45:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.235362ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:09:08Z"
    - latency: 2.031093ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:09:08Z"
    - latency: 879.364µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:08:08Z"
    - latency: 1.726017ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:08:08Z"
    - latency: 911.738µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:07:08Z"
    - latency: 1.79007ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:07:08Z"
    - latency: 835.746µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:06:08Z"
    - latency: 1.627395ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:06:08Z"
    - latency: 1.069992ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T18:05:08Z"
    - latency: 1.850511ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T18:05:08Z"
kind: List
metadata:
  resourceVersion: ""