apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T04:19:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-187-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-187.ec2.internal
      uid: a3ff6051-e375-4b35-93d9-298434d1b56c
    resourceVersion: "72000"
    uid: 3c71b081-f265-4664-85dc-67981dea9f8b
  spec:
    sourcePod: network-check-source-7d88cb55d8-wjm98
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T04:26:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.258378ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:08:17Z"
    - latency: 1.058798ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:07:17Z"
    - latency: 1.238131ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:06:17Z"
    - latency: 1.153792ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:05:17Z"
    - latency: 1.523268ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:04:17Z"
    - latency: 1.056756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:03:17Z"
    - latency: 1.039243ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:02:17Z"
    - latency: 1.129431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:01:17Z"
    - latency: 1.024145ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:00:17Z"
    - latency: 1.4312ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T04:59:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T04:19:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-187-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-187.ec2.internal
      uid: a3ff6051-e375-4b35-93d9-298434d1b56c
    resourceVersion: "71006"
    uid: aec08319-5cc7-4a81-a95b-6d97a000dfb0
  spec:
    sourcePod: network-check-source-7d88cb55d8-wjm98
    targetEndpoint: a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T04:25:17Z"
      message: 'load-balancer-api-external: tcp connection to a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.464019ms
      message: 'load-balancer-api-external: tcp connection to a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:07:17Z"
    - latency: 10.888215ms
      message: 'load-balancer-api-external: resolved host name a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:07:17Z"
    - latency: 4.19267ms
      message: 'load-balancer-api-external: tcp connection to a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:06:17Z"
    - latency: 7.02092ms
      message: 'load-balancer-api-external: resolved host name a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:06:17Z"
    - latency: 5.636599ms
      message: 'load-balancer-api-external: tcp connection to a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:05:17Z"
    - latency: 6.201717ms
      message: 'load-balancer-api-external: resolved host name a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:05:17Z"
    - latency: 5.282524ms
      message: 'load-balancer-api-external: tcp connection to a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:04:17Z"
    - latency: 6.984703ms
      message: 'load-balancer-api-external: resolved host name a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:04:17Z"
    - latency: 2.913974ms
      message: 'load-balancer-api-external: tcp connection to a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:03:17Z"
    - latency: 6.601025ms
      message: 'load-balancer-api-external: resolved host name a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:03:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T04:19:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-187-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-187.ec2.internal
      uid: a3ff6051-e375-4b35-93d9-298434d1b56c
    resourceVersion: "71007"
    uid: 822736f2-941d-4522-af57-49b5efc36811
  spec:
    sourcePod: network-check-source-7d88cb55d8-wjm98
    targetEndpoint: a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T04:25:17Z"
      message: 'load-balancer-api-internal: tcp connection to a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.151822ms
      message: 'load-balancer-api-internal: tcp connection to a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:07:17Z"
    - latency: 10.760883ms
      message: 'load-balancer-api-internal: resolved host name a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:07:17Z"
    - latency: 5.425498ms
      message: 'load-balancer-api-internal: tcp connection to a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:06:17Z"
    - latency: 6.985926ms
      message: 'load-balancer-api-internal: resolved host name a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:06:17Z"
    - latency: 5.655958ms
      message: 'load-balancer-api-internal: tcp connection to a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:05:17Z"
    - latency: 6.211604ms
      message: 'load-balancer-api-internal: resolved host name a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:05:17Z"
    - latency: 4.809985ms
      message: 'load-balancer-api-internal: tcp connection to a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:04:17Z"
    - latency: 7.018168ms
      message: 'load-balancer-api-internal: resolved host name a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:04:17Z"
    - latency: 3.281135ms
      message: 'load-balancer-api-internal: tcp connection to a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:03:17Z"
    - latency: 6.542026ms
      message: 'load-balancer-api-internal: resolved host name a076a7414da804cd4b4771472d0d38de-ea56671196d9168e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:03:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T04:19:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-187-to-network-check-target-ip-10-0-129-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-187.ec2.internal
      uid: a3ff6051-e375-4b35-93d9-298434d1b56c
    resourceVersion: "71998"
    uid: ac456bfd-7b08-421c-9611-7d67c0f50464
  spec:
    sourcePod: network-check-source-7d88cb55d8-wjm98
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T04:26:17Z"
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.623552ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:08:17Z"
    - latency: 1.205967ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:07:17Z"
    - latency: 1.481188ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:06:17Z"
    - latency: 1.234501ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:05:17Z"
    - latency: 991.572µs
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:04:17Z"
    - latency: 1.080826ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:03:17Z"
    - latency: 1.054146ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:02:17Z"
    - latency: 1.515447ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:01:17Z"
    - latency: 958.471µs
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:00:17Z"
    - latency: 1.325556ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T04:59:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T04:19:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-187-to-network-check-target-ip-10-0-133-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-187.ec2.internal
      uid: a3ff6051-e375-4b35-93d9-298434d1b56c
    resourceVersion: "71997"
    uid: c3303968-24ad-4249-ab14-0c4b9f040532
  spec:
    sourcePod: network-check-source-7d88cb55d8-wjm98
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T04:26:17Z"
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.22211ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:08:17Z"
    - latency: 2.015757ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:07:17Z"
    - latency: 2.126781ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:06:17Z"
    - latency: 2.200093ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:05:17Z"
    - latency: 2.304479ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:04:17Z"
    - latency: 2.108447ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:03:17Z"
    - latency: 2.252158ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:02:17Z"
    - latency: 2.884463ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:01:17Z"
    - latency: 2.327615ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:00:17Z"
    - latency: 2.282314ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T04:59:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T04:19:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-187-to-network-check-target-ip-10-0-139-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-187.ec2.internal
      uid: a3ff6051-e375-4b35-93d9-298434d1b56c
    resourceVersion: "71999"
    uid: 2c164297-1b47-4b1e-a9e9-239d93d332b1
  spec:
    sourcePod: network-check-source-7d88cb55d8-wjm98
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T04:26:17Z"
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.645128ms
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:08:17Z"
    - latency: 2.408491ms
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:07:17Z"
    - latency: 2.616647ms
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:06:17Z"
    - latency: 2.679908ms
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:05:17Z"
    - latency: 2.439494ms
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:04:17Z"
    - latency: 2.768063ms
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:03:17Z"
    - latency: 2.326232ms
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:02:17Z"
    - latency: 2.648985ms
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:01:17Z"
    - latency: 2.167575ms
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:00:17Z"
    - latency: 2.449565ms
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T04:59:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T04:19:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-187-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-187.ec2.internal
      uid: a3ff6051-e375-4b35-93d9-298434d1b56c
    resourceVersion: "71005"
    uid: 655a10fa-2898-424b-a880-4473af5ef75d
  spec:
    sourcePod: network-check-source-7d88cb55d8-wjm98
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T04:25:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 934.911µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:07:17Z"
    - latency: 2.012892ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:07:17Z"
    - latency: 882.898µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:06:17Z"
    - latency: 1.850032ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:06:17Z"
    - latency: 1.174716ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:05:17Z"
    - latency: 1.964289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:05:17Z"
    - latency: 887.929µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:04:17Z"
    - latency: 1.792708ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:04:17Z"
    - latency: 999.823µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T05:03:17Z"
    - latency: 2.060759ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T05:03:17Z"
kind: List
metadata:
  resourceVersion: ""