apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:11:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-158-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-158.ec2.internal
      uid: 15bc1d20-e81d-434d-8dbc-0560956d0341
    resourceVersion: "26699"
    uid: d32f6e74-9b4b-41f8-ae84-239765026562
  spec:
    sourcePod: network-check-source-8894fc9bd-rcf78
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:18:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 994.268µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:53:31Z"
    - latency: 957.848µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:52:31Z"
    - latency: 1.184506ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:51:31Z"
    - latency: 1.271454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:50:31Z"
    - latency: 908.059µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:49:31Z"
    - latency: 798.771µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:48:31Z"
    - latency: 791.334µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:47:31Z"
    - latency: 931.055µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:46:31Z"
    - latency: 934.799µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:45:31Z"
    - latency: 1.12751ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:44:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:11:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-158-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-158.ec2.internal
      uid: 15bc1d20-e81d-434d-8dbc-0560956d0341
    resourceVersion: "26701"
    uid: b039efce-3a06-47e6-820f-8312303ee3f8
  spec:
    sourcePod: network-check-source-8894fc9bd-rcf78
    targetEndpoint: af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:17:31Z"
      message: 'load-balancer-api-external: tcp connection to af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.574811ms
      message: 'load-balancer-api-external: tcp connection to af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:53:31Z"
    - latency: 6.42651ms
      message: 'load-balancer-api-external: resolved host name af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:53:31Z"
    - latency: 4.684573ms
      message: 'load-balancer-api-external: tcp connection to af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:52:31Z"
    - latency: 6.597273ms
      message: 'load-balancer-api-external: resolved host name af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:52:31Z"
    - latency: 4.597266ms
      message: 'load-balancer-api-external: tcp connection to af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:51:31Z"
    - latency: 6.137678ms
      message: 'load-balancer-api-external: resolved host name af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:51:31Z"
    - latency: 4.246136ms
      message: 'load-balancer-api-external: tcp connection to af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:50:31Z"
    - latency: 6.384842ms
      message: 'load-balancer-api-external: resolved host name af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:50:31Z"
    - latency: 4.917402ms
      message: 'load-balancer-api-external: tcp connection to af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:49:31Z"
    - latency: 5.867461ms
      message: 'load-balancer-api-external: resolved host name af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:49:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:11:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-158-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-158.ec2.internal
      uid: 15bc1d20-e81d-434d-8dbc-0560956d0341
    resourceVersion: "26700"
    uid: f8a31ac2-e84e-4a9b-bea2-f090870eae1b
  spec:
    sourcePod: network-check-source-8894fc9bd-rcf78
    targetEndpoint: af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:17:31Z"
      message: 'load-balancer-api-internal: tcp connection to af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.617642ms
      message: 'load-balancer-api-internal: tcp connection to af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:53:31Z"
    - latency: 6.363985ms
      message: 'load-balancer-api-internal: resolved host name af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:53:31Z"
    - latency: 4.730607ms
      message: 'load-balancer-api-internal: tcp connection to af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:52:31Z"
    - latency: 6.675497ms
      message: 'load-balancer-api-internal: resolved host name af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:52:31Z"
    - latency: 4.611805ms
      message: 'load-balancer-api-internal: tcp connection to af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:51:31Z"
    - latency: 6.051722ms
      message: 'load-balancer-api-internal: resolved host name af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:51:31Z"
    - latency: 4.272406ms
      message: 'load-balancer-api-internal: tcp connection to af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:50:31Z"
    - latency: 6.461803ms
      message: 'load-balancer-api-internal: resolved host name af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:50:31Z"
    - latency: 4.897762ms
      message: 'load-balancer-api-internal: tcp connection to af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:49:31Z"
    - latency: 5.787783ms
      message: 'load-balancer-api-internal: resolved host name af5cc1f39c79e4dcfb3ff89a9504a8c2-daec1ffff6e4d26f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:49:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:11:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-158-to-network-check-target-ip-10-0-138-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-158.ec2.internal
      uid: 15bc1d20-e81d-434d-8dbc-0560956d0341
    resourceVersion: "26695"
    uid: 54bc53df-6bfc-47e3-a425-6b6cc5df4cf0
  spec:
    sourcePod: network-check-source-8894fc9bd-rcf78
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:18:31Z"
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 749.811µs
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:53:31Z"
    - latency: 797.16µs
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:52:31Z"
    - latency: 879.978µs
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:51:31Z"
    - latency: 746.788µs
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:50:31Z"
    - latency: 848.569µs
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:49:31Z"
    - latency: 775.452µs
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:48:31Z"
    - latency: 786.078µs
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:47:31Z"
    - latency: 1.407005ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:46:31Z"
    - latency: 766.986µs
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:45:31Z"
    - latency: 787.842µs
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:44:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:11:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-158-to-network-check-target-ip-10-0-140-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-158.ec2.internal
      uid: 15bc1d20-e81d-434d-8dbc-0560956d0341
    resourceVersion: "26696"
    uid: 94f02769-dc90-4996-8156-4da15cd3b5f9
  spec:
    sourcePod: network-check-source-8894fc9bd-rcf78
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:18:31Z"
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.786934ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:53:31Z"
    - latency: 1.861838ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:52:31Z"
    - latency: 1.616301ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:51:31Z"
    - latency: 1.743256ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:50:31Z"
    - latency: 1.973861ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:49:31Z"
    - latency: 1.824646ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:48:31Z"
    - latency: 1.859493ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:47:31Z"
    - latency: 2.022287ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:46:31Z"
    - latency: 1.946595ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:45:31Z"
    - latency: 1.908396ms
      message: 'network-check-target-ip-10-0-140-104: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:44:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:11:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-158-to-network-check-target-ip-10-0-140-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-158.ec2.internal
      uid: 15bc1d20-e81d-434d-8dbc-0560956d0341
    resourceVersion: "26698"
    uid: 935e4387-7687-4e28-a431-a47fc35df18f
  spec:
    sourcePod: network-check-source-8894fc9bd-rcf78
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:18:31Z"
      message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.90711ms
      message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:53:31Z"
    - latency: 1.955171ms
      message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:52:31Z"
    - latency: 1.990561ms
      message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:51:31Z"
    - latency: 1.872734ms
      message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:50:31Z"
    - latency: 2.148888ms
      message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:49:31Z"
    - latency: 2.11677ms
      message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:48:31Z"
    - latency: 2.045303ms
      message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:47:31Z"
    - latency: 1.870023ms
      message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:46:31Z"
    - latency: 2.04085ms
      message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:45:31Z"
    - latency: 1.842464ms
      message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:44:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T14:11:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-158-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-158.ec2.internal
      uid: 15bc1d20-e81d-434d-8dbc-0560956d0341
    resourceVersion: "26697"
    uid: dd721b22-c94d-4c55-840c-687acac5792c
  spec:
    sourcePod: network-check-source-8894fc9bd-rcf78
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T14:17:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 803.515µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:53:31Z"
    - latency: 1.844851ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:53:31Z"
    - latency: 876.716µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:52:31Z"
    - latency: 1.511969ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:52:31Z"
    - latency: 993.87µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:51:31Z"
    - latency: 1.610233ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:51:31Z"
    - latency: 982.347µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:50:31Z"
    - latency: 1.791983ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:50:31Z"
    - latency: 706.157µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T14:49:31Z"
    - latency: 1.564705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T14:49:31Z"
kind: List
metadata:
  resourceVersion: ""