apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T20:16:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-118-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-118.ec2.internal
      uid: 2d64c6bb-a532-4e40-a5b4-fc87398c50d4
    resourceVersion: "36463"
    uid: 1627dfb3-4bad-4abe-8232-40d91810fc41
  spec:
    sourcePod: network-check-source-8894fc9bd-t9s2d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:23:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 901.644µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:05:36Z"
    - latency: 804.918µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:04:36Z"
    - latency: 775.755µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:03:36Z"
    - latency: 896.522µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:02:36Z"
    - latency: 915.431µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:01:36Z"
    - latency: 1.215018ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:00:36Z"
    - latency: 1.046117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:59:36Z"
    - latency: 1.612796ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:58:36Z"
    - latency: 1.016993ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:57:36Z"
    - latency: 826.386µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:56:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T20:16:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-118-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-118.ec2.internal
      uid: 2d64c6bb-a532-4e40-a5b4-fc87398c50d4
    resourceVersion: "39108"
    uid: cdf1c562-b279-4f93-b593-078508267a66
  spec:
    sourcePod: network-check-source-8894fc9bd-t9s2d
    targetEndpoint: a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:22:36Z"
      message: 'load-balancer-api-external: tcp connection to a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.092562ms
      message: 'load-balancer-api-external: tcp connection to a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:10:36Z"
    - latency: 7.8959ms
      message: 'load-balancer-api-external: resolved host name a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:10:36Z"
    - latency: 4.331796ms
      message: 'load-balancer-api-external: tcp connection to a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:09:36Z"
    - latency: 8.292191ms
      message: 'load-balancer-api-external: resolved host name a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:09:36Z"
    - latency: 4.955691ms
      message: 'load-balancer-api-external: tcp connection to a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:08:36Z"
    - latency: 8.17228ms
      message: 'load-balancer-api-external: resolved host name a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:08:36Z"
    - latency: 4.667313ms
      message: 'load-balancer-api-external: tcp connection to a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:07:36Z"
    - latency: 7.906156ms
      message: 'load-balancer-api-external: resolved host name a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:07:36Z"
    - latency: 4.91276ms
      message: 'load-balancer-api-external: tcp connection to a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:06:36Z"
    - latency: 7.376934ms
      message: 'load-balancer-api-external: resolved host name a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:06:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T20:16:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-118-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-118.ec2.internal
      uid: 2d64c6bb-a532-4e40-a5b4-fc87398c50d4
    resourceVersion: "39109"
    uid: a6109f38-5062-40d6-aa5a-18abac5590f3
  spec:
    sourcePod: network-check-source-8894fc9bd-t9s2d
    targetEndpoint: a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:22:36Z"
      message: 'load-balancer-api-internal: tcp connection to a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.105238ms
      message: 'load-balancer-api-internal: tcp connection to a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:10:36Z"
    - latency: 7.960863ms
      message: 'load-balancer-api-internal: resolved host name a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:10:36Z"
    - latency: 4.347864ms
      message: 'load-balancer-api-internal: tcp connection to a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:09:36Z"
    - latency: 8.240536ms
      message: 'load-balancer-api-internal: resolved host name a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:09:36Z"
    - latency: 5.967629ms
      message: 'load-balancer-api-internal: tcp connection to a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:08:36Z"
    - latency: 8.219796ms
      message: 'load-balancer-api-internal: resolved host name a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:08:36Z"
    - latency: 4.661782ms
      message: 'load-balancer-api-internal: tcp connection to a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:07:36Z"
    - latency: 7.968431ms
      message: 'load-balancer-api-internal: resolved host name a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:07:36Z"
    - latency: 4.761321ms
      message: 'load-balancer-api-internal: tcp connection to a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:06:36Z"
    - latency: 7.423978ms
      message: 'load-balancer-api-internal: resolved host name a5013424d0a6142a2a6d3ee5758ed7d6-ff9106e3ec1d2585.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:06:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T20:16:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-118-to-network-check-target-ip-10-0-137-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-118.ec2.internal
      uid: 2d64c6bb-a532-4e40-a5b4-fc87398c50d4
    resourceVersion: "36462"
    uid: 4931b8bc-b7a1-48cd-90a0-bb2dfda5c35a
  spec:
    sourcePod: network-check-source-8894fc9bd-t9s2d
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:23:36Z"
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.119237ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:05:36Z"
    - latency: 1.944643ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:04:36Z"
    - latency: 2.089916ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:03:36Z"
    - latency: 2.332371ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:02:36Z"
    - latency: 2.275532ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:01:36Z"
    - latency: 2.10895ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:00:36Z"
    - latency: 2.668222ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:59:36Z"
    - latency: 2.416151ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:58:36Z"
    - latency: 2.034184ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:57:36Z"
    - latency: 1.950894ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:56:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T20:16:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-118-to-network-check-target-ip-10-0-138-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-118.ec2.internal
      uid: 2d64c6bb-a532-4e40-a5b4-fc87398c50d4
    resourceVersion: "36460"
    uid: 295878bc-401d-4536-a40b-7b1ffbab73f1
  spec:
    sourcePod: network-check-source-8894fc9bd-t9s2d
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:23:36Z"
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.083122ms
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:05:36Z"
    - latency: 859.383µs
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:04:36Z"
    - latency: 1.113181ms
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:03:36Z"
    - latency: 1.141342ms
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:02:36Z"
    - latency: 1.362983ms
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:01:36Z"
    - latency: 1.211961ms
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:00:36Z"
    - latency: 1.266904ms
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:59:36Z"
    - latency: 2.108308ms
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:58:36Z"
    - latency: 1.389501ms
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:57:36Z"
    - latency: 702.392µs
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:56:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T20:16:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-118-to-network-check-target-ip-10-0-142-60
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-118.ec2.internal
      uid: 2d64c6bb-a532-4e40-a5b4-fc87398c50d4
    resourceVersion: "36461"
    uid: bfa243da-68a5-4760-af92-10cd15cf4db8
  spec:
    sourcePod: network-check-source-8894fc9bd-t9s2d
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:23:36Z"
      message: 'network-check-target-ip-10-0-142-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.04986ms
      message: 'network-check-target-ip-10-0-142-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:05:36Z"
    - latency: 2.312638ms
      message: 'network-check-target-ip-10-0-142-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:04:36Z"
    - latency: 1.537098ms
      message: 'network-check-target-ip-10-0-142-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:03:36Z"
    - latency: 2.322793ms
      message: 'network-check-target-ip-10-0-142-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:02:36Z"
    - latency: 2.303707ms
      message: 'network-check-target-ip-10-0-142-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:01:36Z"
    - latency: 2.278689ms
      message: 'network-check-target-ip-10-0-142-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:00:36Z"
    - latency: 2.359149ms
      message: 'network-check-target-ip-10-0-142-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:59:36Z"
    - latency: 2.236107ms
      message: 'network-check-target-ip-10-0-142-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:58:36Z"
    - latency: 1.976988ms
      message: 'network-check-target-ip-10-0-142-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:57:36Z"
    - latency: 2.029381ms
      message: 'network-check-target-ip-10-0-142-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:56:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T20:16:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-118-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-118.ec2.internal
      uid: 2d64c6bb-a532-4e40-a5b4-fc87398c50d4
    resourceVersion: "39107"
    uid: 1c35fb7c-5a9c-4306-8a0a-767d6b3c0621
  spec:
    sourcePod: network-check-source-8894fc9bd-t9s2d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:22:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 728.384µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:10:36Z"
    - latency: 1.454655ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:10:36Z"
    - latency: 923.666µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:09:36Z"
    - latency: 1.595447ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:09:36Z"
    - latency: 1.120708ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:08:36Z"
    - latency: 2.18903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:08:36Z"
    - latency: 845.044µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:07:36Z"
    - latency: 1.564614ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:07:36Z"
    - latency: 833.375µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T21:06:36Z"
    - latency: 1.52848ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T21:06:36Z"
kind: List
metadata:
  resourceVersion: ""