apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T15:17:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-36-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-36.ec2.internal
      uid: 539cf54a-05de-4ae5-895b-feb3791eeef6
    resourceVersion: "63280"
    uid: edc15ce3-68e2-4fc8-a543-72a1a4ebc7a6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-rf5ks
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T15:24:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.159458ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:59:11Z"
    - latency: 1.109535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:58:11Z"
    - latency: 1.586394ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:57:11Z"
    - latency: 1.50492ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:56:11Z"
    - latency: 899.076µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:55:11Z"
    - latency: 1.058265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:54:11Z"
    - latency: 1.112884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:53:11Z"
    - latency: 804.701µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:52:11Z"
    - latency: 1.091343ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:51:11Z"
    - latency: 897.968µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:50:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T15:17:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-36-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-36.ec2.internal
      uid: 539cf54a-05de-4ae5-895b-feb3791eeef6
    resourceVersion: "63282"
    uid: e900e8e8-1235-4a85-bb3d-14123682c751
  spec:
    sourcePod: network-check-source-7bc5b6bf85-rf5ks
    targetEndpoint: a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T15:23:11Z"
      message: 'load-balancer-api-external: tcp connection to a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.819889ms
      message: 'load-balancer-api-external: tcp connection to a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:59:11Z"
    - latency: 9.901598ms
      message: 'load-balancer-api-external: resolved host name a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:59:11Z"
    - latency: 4.830039ms
      message: 'load-balancer-api-external: tcp connection to a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:58:11Z"
    - latency: 9.070084ms
      message: 'load-balancer-api-external: resolved host name a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:58:11Z"
    - latency: 4.455025ms
      message: 'load-balancer-api-external: tcp connection to a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:57:11Z"
    - latency: 8.508209ms
      message: 'load-balancer-api-external: resolved host name a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:57:11Z"
    - latency: 3.664975ms
      message: 'load-balancer-api-external: tcp connection to a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:56:11Z"
    - latency: 9.363166ms
      message: 'load-balancer-api-external: resolved host name a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:56:11Z"
    - latency: 3.70479ms
      message: 'load-balancer-api-external: tcp connection to a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:55:11Z"
    - latency: 8.012238ms
      message: 'load-balancer-api-external: resolved host name a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:55:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T15:17:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-36-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-36.ec2.internal
      uid: 539cf54a-05de-4ae5-895b-feb3791eeef6
    resourceVersion: "63281"
    uid: a1234b5a-c9a1-4f14-86d7-1f8766593430
  spec:
    sourcePod: network-check-source-7bc5b6bf85-rf5ks
    targetEndpoint: a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T15:23:11Z"
      message: 'load-balancer-api-internal: tcp connection to a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.789845ms
      message: 'load-balancer-api-internal: tcp connection to a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:59:11Z"
    - latency: 9.868004ms
      message: 'load-balancer-api-internal: resolved host name a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:59:11Z"
    - latency: 3.633095ms
      message: 'load-balancer-api-internal: tcp connection to a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:58:11Z"
    - latency: 9.164859ms
      message: 'load-balancer-api-internal: resolved host name a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:58:11Z"
    - latency: 4.16553ms
      message: 'load-balancer-api-internal: tcp connection to a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:57:11Z"
    - latency: 8.437097ms
      message: 'load-balancer-api-internal: resolved host name a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:57:11Z"
    - latency: 3.698552ms
      message: 'load-balancer-api-internal: tcp connection to a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:56:11Z"
    - latency: 9.314469ms
      message: 'load-balancer-api-internal: resolved host name a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:56:11Z"
    - latency: 3.730106ms
      message: 'load-balancer-api-internal: tcp connection to a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:55:11Z"
    - latency: 7.956889ms
      message: 'load-balancer-api-internal: resolved host name a3d3456e110a34daa85e748cad0c5558-504520122657ce09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:55:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T15:17:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-36-to-network-check-target-ip-10-0-133-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-36.ec2.internal
      uid: 539cf54a-05de-4ae5-895b-feb3791eeef6
    resourceVersion: "63277"
    uid: 845ce953-4cc9-4c58-ae8f-f548f2fd1425
  spec:
    sourcePod: network-check-source-7bc5b6bf85-rf5ks
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T15:24:11Z"
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.462543ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:59:11Z"
    - latency: 2.576419ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:58:11Z"
    - latency: 2.343735ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:57:11Z"
    - latency: 2.108557ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:56:11Z"
    - latency: 2.138321ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:55:11Z"
    - latency: 2.240953ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:54:11Z"
    - latency: 2.310749ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:53:11Z"
    - latency: 2.126943ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:52:11Z"
    - latency: 2.474757ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:51:11Z"
    - latency: 2.556537ms
      message: 'network-check-target-ip-10-0-133-167: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:50:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T15:17:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-36-to-network-check-target-ip-10-0-136-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-36.ec2.internal
      uid: 539cf54a-05de-4ae5-895b-feb3791eeef6
    resourceVersion: "63279"
    uid: 1da8e54d-067c-4f12-8260-7c850bf1eb36
  spec:
    sourcePod: network-check-source-7bc5b6bf85-rf5ks
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T15:24:11Z"
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.341814ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:59:11Z"
    - latency: 1.391493ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:58:11Z"
    - latency: 1.7849ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:57:11Z"
    - latency: 919.473µs
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:56:11Z"
    - latency: 841.107µs
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:55:11Z"
    - latency: 877.752µs
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:54:11Z"
    - latency: 798.468µs
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:53:11Z"
    - latency: 884.023µs
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:52:11Z"
    - latency: 1.247956ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:51:11Z"
    - latency: 1.048383ms
      message: 'network-check-target-ip-10-0-136-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:50:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T15:17:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-36-to-network-check-target-ip-10-0-143-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-36.ec2.internal
      uid: 539cf54a-05de-4ae5-895b-feb3791eeef6
    resourceVersion: "63276"
    uid: 994b458f-8afa-417c-ae74-9956cbd7f53c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-rf5ks
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T15:24:11Z"
      message: 'network-check-target-ip-10-0-143-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.16982ms
      message: 'network-check-target-ip-10-0-143-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:59:11Z"
    - latency: 2.082481ms
      message: 'network-check-target-ip-10-0-143-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:58:11Z"
    - latency: 2.237434ms
      message: 'network-check-target-ip-10-0-143-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:57:11Z"
    - latency: 2.121669ms
      message: 'network-check-target-ip-10-0-143-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:56:11Z"
    - latency: 1.98927ms
      message: 'network-check-target-ip-10-0-143-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:55:11Z"
    - latency: 2.181442ms
      message: 'network-check-target-ip-10-0-143-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:54:11Z"
    - latency: 2.173209ms
      message: 'network-check-target-ip-10-0-143-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:53:11Z"
    - latency: 1.883788ms
      message: 'network-check-target-ip-10-0-143-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:52:11Z"
    - latency: 2.233229ms
      message: 'network-check-target-ip-10-0-143-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:51:11Z"
    - latency: 2.035002ms
      message: 'network-check-target-ip-10-0-143-231: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:50:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T15:17:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-36-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-36.ec2.internal
      uid: 539cf54a-05de-4ae5-895b-feb3791eeef6
    resourceVersion: "63278"
    uid: 79a4a1af-164f-4f81-b139-ac1a5a68e5ce
  spec:
    sourcePod: network-check-source-7bc5b6bf85-rf5ks
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T15:23:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.06631ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:59:11Z"
    - latency: 1.655327ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:59:11Z"
    - latency: 1.206723ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:58:11Z"
    - latency: 2.031135ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:58:11Z"
    - latency: 1.04696ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:57:11Z"
    - latency: 1.804614ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:57:11Z"
    - latency: 926.072µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:56:11Z"
    - latency: 2.003652ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:56:11Z"
    - latency: 1.14675ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T15:55:11Z"
    - latency: 1.991678ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T15:55:11Z"
kind: List
metadata:
  resourceVersion: ""