apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:27:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: d3197460-9fb4-40a7-8e94-fd34d9f57053
    resourceVersion: "54331"
    uid: 5ec473ad-fe54-4fff-90fb-968da8b03bc4
  spec:
    sourcePod: network-check-source-989f8b8dc-85qbn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:34:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.340465ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:02:34Z"
    - latency: 983.224µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:01:34Z"
    - latency: 1.188662ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:00:34Z"
    - latency: 998.046µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:59:34Z"
    - latency: 972.597µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:34Z"
    - latency: 1.082495ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:34Z"
    - latency: 977.541µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:56:34Z"
    - latency: 979.719µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:55:34Z"
    - latency: 1.367775ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:54:34Z"
    - latency: 869.563µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:53:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:27:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: d3197460-9fb4-40a7-8e94-fd34d9f57053
    resourceVersion: "54982"
    uid: aa414896-be75-49c1-8b4f-0b9137b9a489
  spec:
    sourcePod: network-check-source-989f8b8dc-85qbn
    targetEndpoint: ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:33:34Z"
      message: 'load-balancer-api-external: tcp connection to ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.21347ms
      message: 'load-balancer-api-external: tcp connection to ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:03:34Z"
    - latency: 7.260151ms
      message: 'load-balancer-api-external: resolved host name ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:03:34Z"
    - latency: 4.243693ms
      message: 'load-balancer-api-external: tcp connection to ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:02:34Z"
    - latency: 7.895394ms
      message: 'load-balancer-api-external: resolved host name ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:02:34Z"
    - latency: 5.731696ms
      message: 'load-balancer-api-external: tcp connection to ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:01:34Z"
    - latency: 10.684953ms
      message: 'load-balancer-api-external: resolved host name ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:01:34Z"
    - latency: 4.660499ms
      message: 'load-balancer-api-external: tcp connection to ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:00:34Z"
    - latency: 6.978926ms
      message: 'load-balancer-api-external: resolved host name ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:00:34Z"
    - latency: 8.551198ms
      message: 'load-balancer-api-external: tcp connection to ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:59:34Z"
    - latency: 6.421753ms
      message: 'load-balancer-api-external: resolved host name ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:59:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:27:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: d3197460-9fb4-40a7-8e94-fd34d9f57053
    resourceVersion: "54983"
    uid: cf9bd432-15b9-44a3-af5b-f0134a777a82
  spec:
    sourcePod: network-check-source-989f8b8dc-85qbn
    targetEndpoint: ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:33:34Z"
      message: 'load-balancer-api-internal: tcp connection to ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.040634ms
      message: 'load-balancer-api-internal: tcp connection to ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:03:34Z"
    - latency: 7.330185ms
      message: 'load-balancer-api-internal: resolved host name ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:03:34Z"
    - latency: 5.622512ms
      message: 'load-balancer-api-internal: tcp connection to ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:02:34Z"
    - latency: 7.983925ms
      message: 'load-balancer-api-internal: resolved host name ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:02:34Z"
    - latency: 4.905159ms
      message: 'load-balancer-api-internal: tcp connection to ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:01:34Z"
    - latency: 10.889002ms
      message: 'load-balancer-api-internal: resolved host name ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:01:34Z"
    - latency: 3.987961ms
      message: 'load-balancer-api-internal: tcp connection to ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:00:34Z"
    - latency: 7.080406ms
      message: 'load-balancer-api-internal: resolved host name ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:00:34Z"
    - latency: 8.536072ms
      message: 'load-balancer-api-internal: tcp connection to ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:59:34Z"
    - latency: 6.489259ms
      message: 'load-balancer-api-internal: resolved host name ae6edcc0532d64a8abfe11cab0cfc7bb-3495c8d0cefe2f51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:59:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:27:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-ip-10-0-128-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: d3197460-9fb4-40a7-8e94-fd34d9f57053
    resourceVersion: "54329"
    uid: f8871e17-02df-42fd-b50d-14afe3a6b144
  spec:
    sourcePod: network-check-source-989f8b8dc-85qbn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:34:34Z"
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.267552ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:02:34Z"
    - latency: 2.104731ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:01:34Z"
    - latency: 1.922377ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:00:34Z"
    - latency: 2.13813ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:59:34Z"
    - latency: 1.723662ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:34Z"
    - latency: 2.007657ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:34Z"
    - latency: 1.789227ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:56:34Z"
    - latency: 1.730665ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:55:34Z"
    - latency: 1.942647ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:54:34Z"
    - latency: 1.847525ms
      message: 'network-check-target-ip-10-0-128-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:53:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:27:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-ip-10-0-139-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: d3197460-9fb4-40a7-8e94-fd34d9f57053
    resourceVersion: "54328"
    uid: 63f159b4-25eb-4f09-9885-12dc65f9acbf
  spec:
    sourcePod: network-check-source-989f8b8dc-85qbn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:34:34Z"
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.32596ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:02:34Z"
    - latency: 1.007833ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:01:34Z"
    - latency: 1.249244ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:00:34Z"
    - latency: 1.036257ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:59:34Z"
    - latency: 915.443µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:34Z"
    - latency: 919.999µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:34Z"
    - latency: 801.373µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:56:34Z"
    - latency: 1.095078ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:55:34Z"
    - latency: 829.035µs
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:54:34Z"
    - latency: 1.787165ms
      message: 'network-check-target-ip-10-0-139-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:53:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:27:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-ip-10-0-141-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: d3197460-9fb4-40a7-8e94-fd34d9f57053
    resourceVersion: "54330"
    uid: 974cac91-92e0-457e-a4e8-f72e77642446
  spec:
    sourcePod: network-check-source-989f8b8dc-85qbn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:34:34Z"
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.444453ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:02:34Z"
    - latency: 2.15855ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:01:34Z"
    - latency: 2.560492ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:00:34Z"
    - latency: 2.412515ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:59:34Z"
    - latency: 2.364222ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:34Z"
    - latency: 2.465611ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:34Z"
    - latency: 2.355928ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:56:34Z"
    - latency: 2.00718ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:55:34Z"
    - latency: 2.245991ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:54:34Z"
    - latency: 2.515144ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:53:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:27:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-48-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-48.ec2.internal
      uid: d3197460-9fb4-40a7-8e94-fd34d9f57053
    resourceVersion: "54981"
    uid: ea61b56a-6bf4-4bcb-8721-d79224be94fb
  spec:
    sourcePod: network-check-source-989f8b8dc-85qbn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:33:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 820.717µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:03:34Z"
    - latency: 1.816567ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:03:34Z"
    - latency: 1.194472ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:02:34Z"
    - latency: 2.239063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:02:34Z"
    - latency: 855.746µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:01:34Z"
    - latency: 1.727126ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:01:34Z"
    - latency: 837.201µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:00:34Z"
    - latency: 1.985273ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:00:34Z"
    - latency: 754.006µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:59:34Z"
    - latency: 1.964774ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:59:34Z"
kind: List
metadata:
  resourceVersion: ""