apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:22:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-15-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-15.ec2.internal
      uid: f84519d6-1b6b-491e-9dcf-7e273747a134
    resourceVersion: "55942"
    uid: 2696350f-8212-464a-9cbc-c87f438f25db
  spec:
    sourcePod: network-check-source-989f8b8dc-h6l8q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:29:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 844.244µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:57:36Z"
    - latency: 1.03932ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:56:36Z"
    - latency: 1.142327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:55:36Z"
    - latency: 1.050872ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:54:36Z"
    - latency: 1.026394ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:53:36Z"
    - latency: 813.816µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:52:36Z"
    - latency: 976.922µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:51:36Z"
    - latency: 1.03197ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:50:36Z"
    - latency: 1.236179ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:49:36Z"
    - latency: 999.585µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:48:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:22:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-15-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-15.ec2.internal
      uid: f84519d6-1b6b-491e-9dcf-7e273747a134
    resourceVersion: "57004"
    uid: af95d8af-3be8-4a23-a50e-9e018f1d9fbf
  spec:
    sourcePod: network-check-source-989f8b8dc-h6l8q
    targetEndpoint: a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:28:36Z"
      message: 'load-balancer-api-external: tcp connection to a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.376207ms
      message: 'load-balancer-api-external: tcp connection to a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:58:36Z"
    - latency: 7.545539ms
      message: 'load-balancer-api-external: resolved host name a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:58:36Z"
    - latency: 5.015544ms
      message: 'load-balancer-api-external: tcp connection to a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:57:36Z"
    - latency: 8.175693ms
      message: 'load-balancer-api-external: resolved host name a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:57:36Z"
    - latency: 3.541902ms
      message: 'load-balancer-api-external: tcp connection to a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:56:36Z"
    - latency: 8.296988ms
      message: 'load-balancer-api-external: resolved host name a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:56:36Z"
    - latency: 5.307044ms
      message: 'load-balancer-api-external: tcp connection to a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:55:36Z"
    - latency: 7.029151ms
      message: 'load-balancer-api-external: resolved host name a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:55:36Z"
    - latency: 4.209783ms
      message: 'load-balancer-api-external: tcp connection to a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:54:36Z"
    - latency: 9.038838ms
      message: 'load-balancer-api-external: resolved host name a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:54:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:22:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-15-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-15.ec2.internal
      uid: f84519d6-1b6b-491e-9dcf-7e273747a134
    resourceVersion: "57005"
    uid: 8ac8030b-21a1-4e8b-b216-289d3d88a903
  spec:
    sourcePod: network-check-source-989f8b8dc-h6l8q
    targetEndpoint: a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:28:36Z"
      message: 'load-balancer-api-internal: tcp connection to a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.046305ms
      message: 'load-balancer-api-internal: tcp connection to a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:58:36Z"
    - latency: 7.694461ms
      message: 'load-balancer-api-internal: resolved host name a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:58:36Z"
    - latency: 3.165177ms
      message: 'load-balancer-api-internal: tcp connection to a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:57:36Z"
    - latency: 8.233335ms
      message: 'load-balancer-api-internal: resolved host name a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:57:36Z"
    - latency: 3.646284ms
      message: 'load-balancer-api-internal: tcp connection to a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:56:36Z"
    - latency: 8.355897ms
      message: 'load-balancer-api-internal: resolved host name a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:56:36Z"
    - latency: 4.917605ms
      message: 'load-balancer-api-internal: tcp connection to a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:55:36Z"
    - latency: 7.112508ms
      message: 'load-balancer-api-internal: resolved host name a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:55:36Z"
    - latency: 3.947211ms
      message: 'load-balancer-api-internal: tcp connection to a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:54:36Z"
    - latency: 9.022598ms
      message: 'load-balancer-api-internal: resolved host name a59eab0d57ebf42c3bb575afa91f9a11-bd9ddd7506c62de4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:54:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:22:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-15-to-network-check-target-ip-10-0-132-15
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-15.ec2.internal
      uid: f84519d6-1b6b-491e-9dcf-7e273747a134
    resourceVersion: "55939"
    uid: 79bc8a18-ff49-469c-bbad-f5f63b900006
  spec:
    sourcePod: network-check-source-989f8b8dc-h6l8q
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:29:36Z"
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.315498ms
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:57:36Z"
    - latency: 1.095788ms
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:56:36Z"
    - latency: 944.458µs
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:55:36Z"
    - latency: 988.525µs
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:54:36Z"
    - latency: 1.254756ms
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:53:36Z"
    - latency: 1.061549ms
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:52:36Z"
    - latency: 847.251µs
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:51:36Z"
    - latency: 974.712µs
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:50:36Z"
    - latency: 1.50043ms
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:49:36Z"
    - latency: 783.969µs
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:48:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:22:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-15-to-network-check-target-ip-10-0-136-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-15.ec2.internal
      uid: f84519d6-1b6b-491e-9dcf-7e273747a134
    resourceVersion: "55941"
    uid: 5a1b1962-ef11-46f1-8377-433086fa0e3c
  spec:
    sourcePod: network-check-source-989f8b8dc-h6l8q
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:29:36Z"
      message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.948762ms
      message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:57:36Z"
    - latency: 2.222951ms
      message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:56:36Z"
    - latency: 2.112795ms
      message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:55:36Z"
    - latency: 2.194559ms
      message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:54:36Z"
    - latency: 2.456142ms
      message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:53:36Z"
    - latency: 2.041078ms
      message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:52:36Z"
    - latency: 2.571533ms
      message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:51:36Z"
    - latency: 1.884483ms
      message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:50:36Z"
    - latency: 2.414948ms
      message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:49:36Z"
    - latency: 2.297191ms
      message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:48:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:22:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-15-to-network-check-target-ip-10-0-139-106
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-15.ec2.internal
      uid: f84519d6-1b6b-491e-9dcf-7e273747a134
    resourceVersion: "55940"
    uid: 1392f9d3-37a2-43d4-8c5b-f2d61bc2e347
  spec:
    sourcePod: network-check-source-989f8b8dc-h6l8q
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:29:36Z"
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.391995ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:57:36Z"
    - latency: 2.510826ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:56:36Z"
    - latency: 2.205566ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:55:36Z"
    - latency: 2.338456ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:54:36Z"
    - latency: 2.615865ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:53:36Z"
    - latency: 2.160041ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:52:36Z"
    - latency: 2.607076ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:51:36Z"
    - latency: 2.491685ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:50:36Z"
    - latency: 2.460138ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:49:36Z"
    - latency: 2.167854ms
      message: 'network-check-target-ip-10-0-139-106: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:48:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:22:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-15-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-15.ec2.internal
      uid: f84519d6-1b6b-491e-9dcf-7e273747a134
    resourceVersion: "57003"
    uid: 90c6267a-54bd-4579-ab7e-d2c473241324
  spec:
    sourcePod: network-check-source-989f8b8dc-h6l8q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:28:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 886.302µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:58:36Z"
    - latency: 1.699851ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:58:36Z"
    - latency: 817.107µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:57:36Z"
    - latency: 1.553807ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:57:36Z"
    - latency: 935.198µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:56:36Z"
    - latency: 1.889532ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:56:36Z"
    - latency: 965.17µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:55:36Z"
    - latency: 1.707412ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:55:36Z"
    - latency: 787.498µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:54:36Z"
    - latency: 1.713964ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:54:36Z"
kind: List
metadata:
  resourceVersion: ""