apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:34:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 8dc0b652-affa-4873-84f3-32eb291e8c65
    resourceVersion: "66665"
    uid: 29d969d0-3389-46d0-9786-a70e3fb6a80c
  spec:
    sourcePod: network-check-source-6f8b768455-6hxrk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:41:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.272779ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:09:19Z"
    - latency: 1.102085ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:08:19Z"
    - latency: 1.278748ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:07:19Z"
    - latency: 1.305201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:06:19Z"
    - latency: 827.982µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:05:19Z"
    - latency: 1.270631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:04:19Z"
    - latency: 1.251757ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:03:19Z"
    - latency: 828.038µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:02:19Z"
    - latency: 1.178285ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:01:19Z"
    - latency: 1.059222ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:34:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 8dc0b652-affa-4873-84f3-32eb291e8c65
    resourceVersion: "67704"
    uid: e13ec7e2-e9c4-4b2d-9181-7e511efb754e
  spec:
    sourcePod: network-check-source-6f8b768455-6hxrk
    targetEndpoint: a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:40:19Z"
      message: 'load-balancer-api-external: tcp connection to a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.198713ms
      message: 'load-balancer-api-external: tcp connection to a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:10:19Z"
    - latency: 12.027471ms
      message: 'load-balancer-api-external: resolved host name a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:10:19Z"
    - latency: 5.331573ms
      message: 'load-balancer-api-external: tcp connection to a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:09:19Z"
    - latency: 7.135134ms
      message: 'load-balancer-api-external: resolved host name a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:09:19Z"
    - latency: 3.911803ms
      message: 'load-balancer-api-external: tcp connection to a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:08:19Z"
    - latency: 11.211841ms
      message: 'load-balancer-api-external: resolved host name a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:08:19Z"
    - latency: 5.938904ms
      message: 'load-balancer-api-external: tcp connection to a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:07:19Z"
    - latency: 12.168523ms
      message: 'load-balancer-api-external: resolved host name a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:07:19Z"
    - latency: 5.346938ms
      message: 'load-balancer-api-external: tcp connection to a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:06:19Z"
    - latency: 8.844262ms
      message: 'load-balancer-api-external: resolved host name a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:06:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:34:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 8dc0b652-affa-4873-84f3-32eb291e8c65
    resourceVersion: "67705"
    uid: c5c65274-d5c0-4e9a-9db0-fbb4c47b1a92
  spec:
    sourcePod: network-check-source-6f8b768455-6hxrk
    targetEndpoint: a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:40:19Z"
      message: 'load-balancer-api-internal: tcp connection to a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.195042ms
      message: 'load-balancer-api-internal: tcp connection to a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:10:19Z"
    - latency: 12.107275ms
      message: 'load-balancer-api-internal: resolved host name a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:10:19Z"
    - latency: 5.095442ms
      message: 'load-balancer-api-internal: tcp connection to a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:09:19Z"
    - latency: 7.208593ms
      message: 'load-balancer-api-internal: resolved host name a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:09:19Z"
    - latency: 3.907202ms
      message: 'load-balancer-api-internal: tcp connection to a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:08:19Z"
    - latency: 11.151967ms
      message: 'load-balancer-api-internal: resolved host name a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:08:19Z"
    - latency: 5.828413ms
      message: 'load-balancer-api-internal: tcp connection to a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:07:19Z"
    - latency: 12.252276ms
      message: 'load-balancer-api-internal: resolved host name a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:07:19Z"
    - latency: 5.364258ms
      message: 'load-balancer-api-internal: tcp connection to a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:06:19Z"
    - latency: 8.924785ms
      message: 'load-balancer-api-internal: resolved host name a7a8f2e2b7bfd42b1b81185a0d8a3588-308c6b66438a3833.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:06:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:34:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-network-check-target-ip-10-0-129-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 8dc0b652-affa-4873-84f3-32eb291e8c65
    resourceVersion: "66663"
    uid: 5e8e7c29-51eb-4041-bde5-b8fdb621a34d
  spec:
    sourcePod: network-check-source-6f8b768455-6hxrk
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:41:19Z"
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.186104ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:09:19Z"
    - latency: 2.131221ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:08:19Z"
    - latency: 2.272594ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:07:19Z"
    - latency: 1.779355ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:06:19Z"
    - latency: 1.809351ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:05:19Z"
    - latency: 2.32663ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:04:19Z"
    - latency: 1.969924ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:03:19Z"
    - latency: 1.859498ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:02:19Z"
    - latency: 2.372689ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:01:19Z"
    - latency: 2.039817ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:34:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-network-check-target-ip-10-0-132-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 8dc0b652-affa-4873-84f3-32eb291e8c65
    resourceVersion: "66664"
    uid: 103f6f41-f459-4deb-8031-0c712fb167fd
  spec:
    sourcePod: network-check-source-6f8b768455-6hxrk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:41:19Z"
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.391513ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:09:19Z"
    - latency: 2.50803ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:08:19Z"
    - latency: 2.083886ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:07:19Z"
    - latency: 2.218024ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:06:19Z"
    - latency: 2.035107ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:05:19Z"
    - latency: 2.289505ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:04:19Z"
    - latency: 2.202119ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:03:19Z"
    - latency: 2.290602ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:02:19Z"
    - latency: 2.297627ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:01:19Z"
    - latency: 2.26238ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:34:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-network-check-target-ip-10-0-139-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 8dc0b652-affa-4873-84f3-32eb291e8c65
    resourceVersion: "66662"
    uid: a59357bd-61f2-46ac-8afe-6e5755053cf6
  spec:
    sourcePod: network-check-source-6f8b768455-6hxrk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:41:19Z"
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 852.959µs
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:09:19Z"
    - latency: 940.117µs
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:08:19Z"
    - latency: 862.54µs
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:07:19Z"
    - latency: 953.945µs
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:06:19Z"
    - latency: 1.029687ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:05:19Z"
    - latency: 966.352µs
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:04:19Z"
    - latency: 1.014851ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:03:19Z"
    - latency: 1.119427ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:02:19Z"
    - latency: 1.51754ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:01:19Z"
    - latency: 1.130248ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:00:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:34:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 8dc0b652-affa-4873-84f3-32eb291e8c65
    resourceVersion: "67702"
    uid: d64d922c-684c-462d-9102-92b0f78e3f86
  spec:
    sourcePod: network-check-source-6f8b768455-6hxrk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:40:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.079154ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:10:19Z"
    - latency: 2.670323ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:10:19Z"
    - latency: 1.268309ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:09:19Z"
    - latency: 1.927616ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:09:19Z"
    - latency: 1.090146ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:08:19Z"
    - latency: 2.137055ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:08:19Z"
    - latency: 977.762µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:07:19Z"
    - latency: 1.876783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:07:19Z"
    - latency: 989.174µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:06:19Z"
    - latency: 1.954867ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:06:19Z"
kind: List
metadata:
  resourceVersion: ""