apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:36:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-78-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-78.ec2.internal
      uid: 08362994-07c5-4d0a-aa72-280bff8c2b5e
    resourceVersion: "58006"
    uid: 75e7a24b-0cfb-47d5-9f66-f6409279993d
  spec:
    sourcePod: network-check-source-685456655f-swk74
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:43: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.012471ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:04:08Z"
    - latency: 1.153525ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:03:08Z"
    - latency: 1.614255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:02:08Z"
    - latency: 1.375509ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:01:08Z"
    - latency: 1.302694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:00:08Z"
    - latency: 1.190359ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:59:08Z"
    - latency: 1.138244ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:58:08Z"
    - latency: 926.553µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:57:08Z"
    - latency: 1.400774ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:56:08Z"
    - latency: 1.266246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:55:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:36:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-78-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-78.ec2.internal
      uid: 08362994-07c5-4d0a-aa72-280bff8c2b5e
    resourceVersion: "59474"
    uid: 5b2487e1-ffd7-423e-8744-d6a339f57d0d
  spec:
    sourcePod: network-check-source-685456655f-swk74
    targetEndpoint: ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:42:08Z"
      message: 'load-balancer-api-external: tcp connection to ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.194222ms
      message: 'load-balancer-api-external: tcp connection to ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:06:08Z"
    - latency: 8.904153ms
      message: 'load-balancer-api-external: resolved host name ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:06:08Z"
    - latency: 4.79021ms
      message: 'load-balancer-api-external: tcp connection to ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:05:08Z"
    - latency: 7.459114ms
      message: 'load-balancer-api-external: resolved host name ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:05:08Z"
    - latency: 4.928814ms
      message: 'load-balancer-api-external: tcp connection to ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:04:08Z"
    - latency: 8.837047ms
      message: 'load-balancer-api-external: resolved host name ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:04:08Z"
    - latency: 4.210813ms
      message: 'load-balancer-api-external: tcp connection to ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:03:08Z"
    - latency: 8.705625ms
      message: 'load-balancer-api-external: resolved host name ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:03:08Z"
    - latency: 3.659505ms
      message: 'load-balancer-api-external: tcp connection to ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:02:08Z"
    - latency: 9.324582ms
      message: 'load-balancer-api-external: resolved host name ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:36:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-78-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-78.ec2.internal
      uid: 08362994-07c5-4d0a-aa72-280bff8c2b5e
    resourceVersion: "59473"
    uid: 56733ba2-39eb-4fce-82b8-b4eb31e5529b
  spec:
    sourcePod: network-check-source-685456655f-swk74
    targetEndpoint: ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:42:08Z"
      message: 'load-balancer-api-internal: tcp connection to ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.166568ms
      message: 'load-balancer-api-internal: tcp connection to ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:06:08Z"
    - latency: 8.966761ms
      message: 'load-balancer-api-internal: resolved host name ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:06:08Z"
    - latency: 4.830316ms
      message: 'load-balancer-api-internal: tcp connection to ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:05:08Z"
    - latency: 7.410025ms
      message: 'load-balancer-api-internal: resolved host name ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:05:08Z"
    - latency: 5.130137ms
      message: 'load-balancer-api-internal: tcp connection to ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:04:08Z"
    - latency: 8.972472ms
      message: 'load-balancer-api-internal: resolved host name ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:04:08Z"
    - latency: 4.200007ms
      message: 'load-balancer-api-internal: tcp connection to ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:03:08Z"
    - latency: 8.764749ms
      message: 'load-balancer-api-internal: resolved host name ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:03:08Z"
    - latency: 3.654026ms
      message: 'load-balancer-api-internal: tcp connection to ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:02:08Z"
    - latency: 9.356825ms
      message: 'load-balancer-api-internal: resolved host name ab647317e50694da1a7e150a52cffdf4-e555cb509d2254ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:36:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-78-to-network-check-target-ip-10-0-134-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-78.ec2.internal
      uid: 08362994-07c5-4d0a-aa72-280bff8c2b5e
    resourceVersion: "58003"
    uid: 732f6a28-b387-4657-a951-8db68df40895
  spec:
    sourcePod: network-check-source-685456655f-swk74
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:43:08Z"
      message: 'network-check-target-ip-10-0-134-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 999.788µs
      message: 'network-check-target-ip-10-0-134-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:04:08Z"
    - latency: 1.65485ms
      message: 'network-check-target-ip-10-0-134-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:03:08Z"
    - latency: 1.864498ms
      message: 'network-check-target-ip-10-0-134-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:02:08Z"
    - latency: 856.857µs
      message: 'network-check-target-ip-10-0-134-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:01:08Z"
    - latency: 1.141717ms
      message: 'network-check-target-ip-10-0-134-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:00:08Z"
    - latency: 1.048608ms
      message: 'network-check-target-ip-10-0-134-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:59:08Z"
    - latency: 1.058937ms
      message: 'network-check-target-ip-10-0-134-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:58:08Z"
    - latency: 1.039036ms
      message: 'network-check-target-ip-10-0-134-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:57:08Z"
    - latency: 1.103139ms
      message: 'network-check-target-ip-10-0-134-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:56:08Z"
    - latency: 1.061062ms
      message: 'network-check-target-ip-10-0-134-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:55:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:36:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-78-to-network-check-target-ip-10-0-135-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-78.ec2.internal
      uid: 08362994-07c5-4d0a-aa72-280bff8c2b5e
    resourceVersion: "58005"
    uid: 9035ac3a-d0db-4ad4-b876-b7b367a9d59b
  spec:
    sourcePod: network-check-source-685456655f-swk74
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:43:08Z"
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.745766ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:04:08Z"
    - latency: 2.634365ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:03:08Z"
    - latency: 2.63922ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:02:08Z"
    - latency: 2.428733ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:01:08Z"
    - latency: 2.51699ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:00:08Z"
    - latency: 2.203938ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:59:08Z"
    - latency: 3.123354ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:58:08Z"
    - latency: 2.275165ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:57:08Z"
    - latency: 3.116081ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:56:08Z"
    - latency: 2.483096ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:55:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:36:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-78-to-network-check-target-ip-10-0-143-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-78.ec2.internal
      uid: 08362994-07c5-4d0a-aa72-280bff8c2b5e
    resourceVersion: "58004"
    uid: f8798d8a-e898-430a-9ff7-bf1a312d0c94
  spec:
    sourcePod: network-check-source-685456655f-swk74
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:43:08Z"
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.109267ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:04:08Z"
    - latency: 2.389969ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:03:08Z"
    - latency: 2.410596ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:02:08Z"
    - latency: 2.060004ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:01:08Z"
    - latency: 2.539505ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:00:08Z"
    - latency: 2.671557ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:59:08Z"
    - latency: 2.112026ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:58:08Z"
    - latency: 2.005355ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:57:08Z"
    - latency: 2.611355ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:56:08Z"
    - latency: 2.398315ms
      message: 'network-check-target-ip-10-0-143-61: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T15:55:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T15:36:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-78-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-78.ec2.internal
      uid: 08362994-07c5-4d0a-aa72-280bff8c2b5e
    resourceVersion: "59472"
    uid: c4769b67-7c49-44c4-8ffa-5ea9a2e57bef
  spec:
    sourcePod: network-check-source-685456655f-swk74
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T15:42:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.057269ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:06:08Z"
    - latency: 1.906902ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:06:08Z"
    - latency: 1.171587ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:05:08Z"
    - latency: 2.172381ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:05:08Z"
    - latency: 797.162µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:04:08Z"
    - latency: 2.020618ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:04:08Z"
    - latency: 1.026721ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:03:08Z"
    - latency: 1.791529ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:03:08Z"
    - latency: 907.019µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T16:02:08Z"
    - latency: 2.517504ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T16:02:08Z"
kind: List
metadata:
  resourceVersion: ""