apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T11:29:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-183-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-183.ec2.internal
      uid: b30b77fe-dca6-4f14-94b6-f4f5bfe35911
    resourceVersion: "64110"
    uid: 9c9f01cf-c751-459f-a9a0-cb3b1cd328d2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vljg8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T11:36:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 941.49µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:11:31Z"
    - latency: 1.379188ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:10:31Z"
    - latency: 732.137µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:09:31Z"
    - latency: 943.682µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:08:31Z"
    - latency: 1.060654ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:07:31Z"
    - latency: 1.443053ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:06:31Z"
    - latency: 1.684769ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:05:31Z"
    - latency: 1.052048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:04:31Z"
    - latency: 1.224873ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:03:31Z"
    - latency: 1.119694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:02:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T11:29:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-183-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-183.ec2.internal
      uid: b30b77fe-dca6-4f14-94b6-f4f5bfe35911
    resourceVersion: "64112"
    uid: d1eabc4d-e7ff-44f4-b7ce-0c4d2b5b4cf5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vljg8
    targetEndpoint: a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T11:35:32Z"
      message: 'load-balancer-api-external: tcp connection to a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 11.941541ms
      message: 'load-balancer-api-external: tcp connection to a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:11:31Z"
    - latency: 7.693549ms
      message: 'load-balancer-api-external: resolved host name a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:11:31Z"
    - latency: 4.915822ms
      message: 'load-balancer-api-external: tcp connection to a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:10:31Z"
    - latency: 8.104895ms
      message: 'load-balancer-api-external: resolved host name a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:10:31Z"
    - latency: 3.753696ms
      message: 'load-balancer-api-external: tcp connection to a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:09:31Z"
    - latency: 7.864028ms
      message: 'load-balancer-api-external: resolved host name a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:09:31Z"
    - latency: 4.859364ms
      message: 'load-balancer-api-external: tcp connection to a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:08:32Z"
    - latency: 12.719172ms
      message: 'load-balancer-api-external: resolved host name a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:08:31Z"
    - latency: 4.439189ms
      message: 'load-balancer-api-external: tcp connection to a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:07:31Z"
    - latency: 5.993127ms
      message: 'load-balancer-api-external: resolved host name a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:07:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T11:29:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-183-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-183.ec2.internal
      uid: b30b77fe-dca6-4f14-94b6-f4f5bfe35911
    resourceVersion: "64111"
    uid: 01e033e9-d573-46a4-a03c-3ec13887d431
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vljg8
    targetEndpoint: a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T11:35:32Z"
      message: 'load-balancer-api-internal: tcp connection to a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.221097ms
      message: 'load-balancer-api-internal: tcp connection to a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:11:31Z"
    - latency: 7.635503ms
      message: 'load-balancer-api-internal: resolved host name a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:11:31Z"
    - latency: 4.001074ms
      message: 'load-balancer-api-internal: tcp connection to a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:10:31Z"
    - latency: 8.067741ms
      message: 'load-balancer-api-internal: resolved host name a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:10:31Z"
    - latency: 3.721789ms
      message: 'load-balancer-api-internal: tcp connection to a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:09:31Z"
    - latency: 7.838197ms
      message: 'load-balancer-api-internal: resolved host name a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:09:31Z"
    - latency: 4.257806ms
      message: 'load-balancer-api-internal: tcp connection to a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:08:32Z"
    - latency: 12.663967ms
      message: 'load-balancer-api-internal: resolved host name a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:08:31Z"
    - latency: 4.819362ms
      message: 'load-balancer-api-internal: tcp connection to a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:07:31Z"
    - latency: 5.961803ms
      message: 'load-balancer-api-internal: resolved host name a52d93dbfb36c4cba9acdd8c96d0cc38-957244163631670f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:07:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T11:29:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-183-to-network-check-target-ip-10-0-128-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-183.ec2.internal
      uid: b30b77fe-dca6-4f14-94b6-f4f5bfe35911
    resourceVersion: "64109"
    uid: 6b1c1fce-d58d-44ab-b3d4-ce6e05c3f707
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vljg8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T11:36:31Z"
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.178499ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:11:31Z"
    - latency: 2.231379ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:10:31Z"
    - latency: 2.194993ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:09:31Z"
    - latency: 2.288565ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:08:31Z"
    - latency: 2.139261ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:07:31Z"
    - latency: 2.514806ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:06:31Z"
    - latency: 2.359501ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:05:31Z"
    - latency: 2.339239ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:04:31Z"
    - latency: 2.405344ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:03:31Z"
    - latency: 2.543849ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:02:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T11:29:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-183-to-network-check-target-ip-10-0-129-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-183.ec2.internal
      uid: b30b77fe-dca6-4f14-94b6-f4f5bfe35911
    resourceVersion: "64107"
    uid: d9827138-5f95-4ea8-b5e9-c0b6f7f77bea
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vljg8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T11:36:31Z"
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.870664ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:11:31Z"
    - latency: 1.859464ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:10:31Z"
    - latency: 1.69688ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:09:31Z"
    - latency: 1.909829ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:08:31Z"
    - latency: 1.848003ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:07:31Z"
    - latency: 2.070382ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:06:31Z"
    - latency: 1.760452ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:05:31Z"
    - latency: 1.818277ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:04:31Z"
    - latency: 1.690683ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:03:31Z"
    - latency: 1.853453ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:02:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T11:29:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-183-to-network-check-target-ip-10-0-140-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-183.ec2.internal
      uid: b30b77fe-dca6-4f14-94b6-f4f5bfe35911
    resourceVersion: "64106"
    uid: 16196a62-b7cb-4c7d-b464-7c16fcb31ffc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vljg8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T11:36:31Z"
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 934.276µs
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:11:31Z"
    - latency: 1.691675ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:10:31Z"
    - latency: 640.679µs
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:09:31Z"
    - latency: 1.079631ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:08:31Z"
    - latency: 1.054195ms
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:07:31Z"
    - latency: 916.078µs
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:06:31Z"
    - latency: 945.318µs
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:05:31Z"
    - latency: 890.45µs
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:04:31Z"
    - latency: 858.911µs
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:03:31Z"
    - latency: 872.095µs
      message: 'network-check-target-ip-10-0-140-183: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:02:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T11:29:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-183-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-183.ec2.internal
      uid: b30b77fe-dca6-4f14-94b6-f4f5bfe35911
    resourceVersion: "64108"
    uid: 5336c04c-00c9-4f86-a73a-3385a929ff7c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vljg8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T11:35:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 805.175µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:11:31Z"
    - latency: 1.854919ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:11:31Z"
    - latency: 1.038441ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:10:31Z"
    - latency: 2.002395ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:10:31Z"
    - latency: 921.442µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:09:31Z"
    - latency: 2.120982ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:09:31Z"
    - latency: 851.181µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:08:31Z"
    - latency: 1.699453ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:08:31Z"
    - latency: 1.092757ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T12:07:31Z"
    - latency: 1.602115ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T12:07:31Z"
kind: List
metadata:
  resourceVersion: ""