apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T01:09:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: b43523c6-8b84-461f-a07b-cb542ef3004b
    resourceVersion: "46548"
    uid: 7efc4bec-0f4e-44ab-9538-45b041e11b92
  spec:
    sourcePod: network-check-source-dbd9cf844-5d962
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T01:16:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.226321ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:37:23Z"
    - latency: 954.513µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:36:23Z"
    - latency: 939.858µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:35:23Z"
    - latency: 744.583µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:34:23Z"
    - latency: 1.050985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:33:23Z"
    - latency: 1.247964ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:32:23Z"
    - latency: 1.014929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:31:23Z"
    - latency: 925.09µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:30:23Z"
    - latency: 1.32857ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:29:23Z"
    - latency: 841.437µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:28:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T01:09:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: b43523c6-8b84-461f-a07b-cb542ef3004b
    resourceVersion: "48749"
    uid: 85d0059e-bf17-405c-9745-0e0a6decfad2
  spec:
    sourcePod: network-check-source-dbd9cf844-5d962
    targetEndpoint: acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T01:15:23Z"
      message: 'load-balancer-api-external: tcp connection to acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.296485ms
      message: 'load-balancer-api-external: tcp connection to acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:39:23Z"
    - latency: 6.271331ms
      message: 'load-balancer-api-external: resolved host name acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:39:23Z"
    - latency: 4.942716ms
      message: 'load-balancer-api-external: tcp connection to acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:38:23Z"
    - latency: 6.519347ms
      message: 'load-balancer-api-external: resolved host name acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:38:23Z"
    - latency: 5.376774ms
      message: 'load-balancer-api-external: tcp connection to acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:37:23Z"
    - latency: 8.987351ms
      message: 'load-balancer-api-external: resolved host name acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:37:23Z"
    - latency: 4.060093ms
      message: 'load-balancer-api-external: tcp connection to acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:36:23Z"
    - latency: 6.598868ms
      message: 'load-balancer-api-external: resolved host name acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:36:23Z"
    - latency: 4.316307ms
      message: 'load-balancer-api-external: tcp connection to acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:35:23Z"
    - latency: 6.567359ms
      message: 'load-balancer-api-external: resolved host name acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:35:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T01:09:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: b43523c6-8b84-461f-a07b-cb542ef3004b
    resourceVersion: "48748"
    uid: d5db5cd2-baac-4378-b9d4-228e68366d4b
  spec:
    sourcePod: network-check-source-dbd9cf844-5d962
    targetEndpoint: acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T01:15:23Z"
      message: 'load-balancer-api-internal: tcp connection to acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.736676ms
      message: 'load-balancer-api-internal: tcp connection to acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:39:23Z"
    - latency: 6.334816ms
      message: 'load-balancer-api-internal: resolved host name acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:39:23Z"
    - latency: 4.912636ms
      message: 'load-balancer-api-internal: tcp connection to acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:38:23Z"
    - latency: 6.622558ms
      message: 'load-balancer-api-internal: resolved host name acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:38:23Z"
    - latency: 5.22498ms
      message: 'load-balancer-api-internal: tcp connection to acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:37:23Z"
    - latency: 9.081531ms
      message: 'load-balancer-api-internal: resolved host name acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:37:23Z"
    - latency: 4.042708ms
      message: 'load-balancer-api-internal: tcp connection to acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:36:23Z"
    - latency: 6.660524ms
      message: 'load-balancer-api-internal: resolved host name acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:36:23Z"
    - latency: 4.776156ms
      message: 'load-balancer-api-internal: tcp connection to acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:35:23Z"
    - latency: 6.634606ms
      message: 'load-balancer-api-internal: resolved host name acfb03b83463748059da11d096dcc611-704cddb2d82b73ac.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:35:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T01:09:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-network-check-target-ip-10-0-132-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: b43523c6-8b84-461f-a07b-cb542ef3004b
    resourceVersion: "46547"
    uid: a9b0659f-7bbe-46b1-9051-758abcab5029
  spec:
    sourcePod: network-check-source-dbd9cf844-5d962
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T01:16:23Z"
      message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.359841ms
      message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:37:23Z"
    - latency: 2.501089ms
      message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:36:23Z"
    - latency: 1.73993ms
      message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:35:23Z"
    - latency: 2.414096ms
      message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:34:23Z"
    - latency: 2.363323ms
      message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:33:23Z"
    - latency: 2.193045ms
      message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:32:23Z"
    - latency: 2.32246ms
      message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:31:23Z"
    - latency: 2.28586ms
      message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:30:23Z"
    - latency: 2.423606ms
      message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:29:23Z"
    - latency: 1.909763ms
      message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:28:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T01:09:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-network-check-target-ip-10-0-142-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: b43523c6-8b84-461f-a07b-cb542ef3004b
    resourceVersion: "46545"
    uid: 8bf0dfd4-d935-41e4-aa32-1a9cf3aeb79e
  spec:
    sourcePod: network-check-source-dbd9cf844-5d962
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T01:16:23Z"
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.626µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:37:23Z"
    - latency: 1.012387ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:36:23Z"
    - latency: 935.804µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:35:23Z"
    - latency: 1.014028ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:34:23Z"
    - latency: 945.938µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:33:23Z"
    - latency: 850.268µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:32:23Z"
    - latency: 988.527µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:31:23Z"
    - latency: 881.5µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:30:23Z"
    - latency: 1.103956ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:29:23Z"
    - latency: 1.276533ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:28:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T01:09:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-network-check-target-ip-10-0-142-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: b43523c6-8b84-461f-a07b-cb542ef3004b
    resourceVersion: "46546"
    uid: 91ab3c54-c8fa-433a-8838-4b14e1b35eba
  spec:
    sourcePod: network-check-source-dbd9cf844-5d962
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T01:16:23Z"
      message: 'network-check-target-ip-10-0-142-67: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.033746ms
      message: 'network-check-target-ip-10-0-142-67: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:37:23Z"
    - latency: 2.002935ms
      message: 'network-check-target-ip-10-0-142-67: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:36:23Z"
    - latency: 1.836067ms
      message: 'network-check-target-ip-10-0-142-67: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:35:23Z"
    - latency: 2.36841ms
      message: 'network-check-target-ip-10-0-142-67: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:34:23Z"
    - latency: 1.82473ms
      message: 'network-check-target-ip-10-0-142-67: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:33:23Z"
    - latency: 2.307376ms
      message: 'network-check-target-ip-10-0-142-67: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:32:23Z"
    - latency: 2.295012ms
      message: 'network-check-target-ip-10-0-142-67: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:31:23Z"
    - latency: 1.944917ms
      message: 'network-check-target-ip-10-0-142-67: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:30:23Z"
    - latency: 2.040897ms
      message: 'network-check-target-ip-10-0-142-67: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:29:23Z"
    - latency: 1.828735ms
      message: 'network-check-target-ip-10-0-142-67: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:28:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T01:09:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: b43523c6-8b84-461f-a07b-cb542ef3004b
    resourceVersion: "48747"
    uid: 20add3c0-3672-4e13-b08b-f4aaadd6dbcd
  spec:
    sourcePod: network-check-source-dbd9cf844-5d962
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T01:15:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 906.14µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:39:23Z"
    - latency: 1.645242ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:39:23Z"
    - latency: 1.197054ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:38:23Z"
    - latency: 1.960463ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:38:23Z"
    - latency: 1.252002ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:37:23Z"
    - latency: 1.749865ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:37:23Z"
    - latency: 884.343µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:36:23Z"
    - latency: 1.838363ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:36:23Z"
    - latency: 937.854µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:35:23Z"
    - latency: 1.757081ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:35:23Z"
kind: List
metadata:
  resourceVersion: ""