apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:07:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-15-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-15.ec2.internal
      uid: 7373f2cb-1e34-4d45-bc09-474a86db0cea
    resourceVersion: "19381"
    uid: 8777b767-82b5-4496-bdc8-2ecc25e066f8
  spec:
    sourcePod: network-check-source-7b678d77c7-bmn9v
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:14:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 832.724µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:21:51Z"
    - latency: 1.18203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:20:51Z"
    - latency: 945.237µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:19:51Z"
    - latency: 776.753µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:18:51Z"
    - latency: 1.391247ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:17:51Z"
    - latency: 1.377929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:16:51Z"
    - latency: 1.096347ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:15:51Z"
    - latency: 903.553µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:14:51Z"
    - latency: 1.041133ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:13:51Z"
    - latency: 1.101343ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:12:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:07:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-15-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-15.ec2.internal
      uid: 7373f2cb-1e34-4d45-bc09-474a86db0cea
    resourceVersion: "18188"
    uid: c156f070-079f-4dda-b1cb-63b5714ae0f5
  spec:
    sourcePod: network-check-source-7b678d77c7-bmn9v
    targetEndpoint: a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:13:51Z"
      message: 'load-balancer-api-external: tcp connection to a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.386511ms
      message: 'load-balancer-api-external: tcp connection to a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:19:51Z"
    - latency: 10.420321ms
      message: 'load-balancer-api-external: resolved host name a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:19:51Z"
    - latency: 5.322815ms
      message: 'load-balancer-api-external: tcp connection to a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:18:51Z"
    - latency: 7.729382ms
      message: 'load-balancer-api-external: resolved host name a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:18:51Z"
    - latency: 5.210592ms
      message: 'load-balancer-api-external: tcp connection to a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:17:51Z"
    - latency: 7.193661ms
      message: 'load-balancer-api-external: resolved host name a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:17:51Z"
    - latency: 4.870361ms
      message: 'load-balancer-api-external: tcp connection to a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:16:51Z"
    - latency: 7.922751ms
      message: 'load-balancer-api-external: resolved host name a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:16:51Z"
    - latency: 5.450191ms
      message: 'load-balancer-api-external: tcp connection to a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:15:51Z"
    - latency: 10.214117ms
      message: 'load-balancer-api-external: resolved host name a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:15:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:07:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-15-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-15.ec2.internal
      uid: 7373f2cb-1e34-4d45-bc09-474a86db0cea
    resourceVersion: "18189"
    uid: 556175b0-152e-437b-9b41-54c0a1b66055
  spec:
    sourcePod: network-check-source-7b678d77c7-bmn9v
    targetEndpoint: a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:13:51Z"
      message: 'load-balancer-api-internal: tcp connection to a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.604485ms
      message: 'load-balancer-api-internal: tcp connection to a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:19:51Z"
    - latency: 10.509677ms
      message: 'load-balancer-api-internal: resolved host name a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:19:51Z"
    - latency: 5.274408ms
      message: 'load-balancer-api-internal: tcp connection to a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:18:51Z"
    - latency: 7.844148ms
      message: 'load-balancer-api-internal: resolved host name a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:18:51Z"
    - latency: 4.516804ms
      message: 'load-balancer-api-internal: tcp connection to a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:17:51Z"
    - latency: 7.268561ms
      message: 'load-balancer-api-internal: resolved host name a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:17:51Z"
    - latency: 5.376907ms
      message: 'load-balancer-api-internal: tcp connection to a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:16:51Z"
    - latency: 8.028263ms
      message: 'load-balancer-api-internal: resolved host name a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:16:51Z"
    - latency: 5.393095ms
      message: 'load-balancer-api-internal: tcp connection to a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:15:51Z"
    - latency: 10.292711ms
      message: 'load-balancer-api-internal: resolved host name a0d360f65a6504d9685333e5000d3f13-475a8fb1f83b421c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:15:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:07:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-15-to-network-check-target-ip-10-0-128-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-15.ec2.internal
      uid: 7373f2cb-1e34-4d45-bc09-474a86db0cea
    resourceVersion: "19379"
    uid: a4f75d7a-0a39-4e23-865d-5fb67c8b629c
  spec:
    sourcePod: network-check-source-7b678d77c7-bmn9v
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:14:51Z"
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.127197ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:21:51Z"
    - latency: 2.054595ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:20:51Z"
    - latency: 2.379232ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:19:51Z"
    - latency: 2.153588ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:18:51Z"
    - latency: 1.954192ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:17:51Z"
    - latency: 2.125052ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:16:51Z"
    - latency: 2.455357ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:15:51Z"
    - latency: 2.092151ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:14:51Z"
    - latency: 2.514727ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:13:51Z"
    - latency: 1.951026ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:12:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:07:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-15-to-network-check-target-ip-10-0-137-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-15.ec2.internal
      uid: 7373f2cb-1e34-4d45-bc09-474a86db0cea
    resourceVersion: "19380"
    uid: 76153723-50ee-455b-8c76-4c8962f8c6d3
  spec:
    sourcePod: network-check-source-7b678d77c7-bmn9v
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:14:51Z"
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.393173ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:21:51Z"
    - latency: 2.423194ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:20:51Z"
    - latency: 2.465177ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:19:51Z"
    - latency: 2.194399ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:18:51Z"
    - latency: 2.889735ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:17:51Z"
    - latency: 2.160092ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:16:51Z"
    - latency: 2.453213ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:15:51Z"
    - latency: 2.385351ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:14:51Z"
    - latency: 2.315353ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:13:51Z"
    - latency: 2.309295ms
      message: 'network-check-target-ip-10-0-137-213: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:12:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:07:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-15-to-network-check-target-ip-10-0-138-15
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-15.ec2.internal
      uid: 7373f2cb-1e34-4d45-bc09-474a86db0cea
    resourceVersion: "19378"
    uid: b9952b98-8661-41e6-9d91-db878eef350f
  spec:
    sourcePod: network-check-source-7b678d77c7-bmn9v
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:14:51Z"
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.323968ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:21:51Z"
    - latency: 971.979µs
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:20:51Z"
    - latency: 1.039496ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:19:51Z"
    - latency: 1.456367ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:18:51Z"
    - latency: 761.407µs
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:17:51Z"
    - latency: 1.109801ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:16:51Z"
    - latency: 1.46274ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:15:51Z"
    - latency: 983.52µs
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:14:51Z"
    - latency: 1.004667ms
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:13:51Z"
    - latency: 872.98µs
      message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:12:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:07:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-15-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-15.ec2.internal
      uid: 7373f2cb-1e34-4d45-bc09-474a86db0cea
    resourceVersion: "18187"
    uid: 6d5da2c5-b014-4aa7-aa4b-93ae50e02a85
  spec:
    sourcePod: network-check-source-7b678d77c7-bmn9v
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:13:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.23308ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:19:51Z"
    - latency: 1.894938ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:19:51Z"
    - latency: 924.686µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:18:51Z"
    - latency: 2.203122ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:18:51Z"
    - latency: 718.91µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:17:51Z"
    - latency: 1.841373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:17:51Z"
    - latency: 883.856µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:16:51Z"
    - latency: 2.095545ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:16:51Z"
    - latency: 833.979µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:15:51Z"
    - latency: 2.407997ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:15:51Z"
kind: List
metadata:
  resourceVersion: ""