apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-16T19:52:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-253-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-253.ec2.internal
      uid: caffa9b8-7f71-4173-a1ae-2d52d7229beb
    resourceVersion: "52304"
    uid: 6a30c411-018f-4389-8e84-48f8922a7b7c
  spec:
    sourcePod: network-check-source-6947749cfc-78dqb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-16T20:00:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.11807ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:28:01Z"
    - latency: 911.904µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:27:01Z"
    - latency: 859.116µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:26:01Z"
    - latency: 917.69µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:25:01Z"
    - latency: 900.641µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:24:01Z"
    - latency: 1.018752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:23:01Z"
    - latency: 798.647µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:22:01Z"
    - latency: 786.564µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:21:01Z"
    - latency: 697.538µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:20:01Z"
    - latency: 1.105184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:19:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-16T19:52:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-253-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-253.ec2.internal
      uid: caffa9b8-7f71-4173-a1ae-2d52d7229beb
    resourceVersion: "46647"
    uid: 3ec22bf1-66a7-4efc-aa09-b1520c2f4bcf
  spec:
    sourcePod: network-check-source-6947749cfc-78dqb
    targetEndpoint: a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-16T19:59:01Z"
      message: 'load-balancer-api-external: tcp connection to a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.852521ms
      message: 'load-balancer-api-external: tcp connection to a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:23:01Z"
    - latency: 7.324576ms
      message: 'load-balancer-api-external: resolved host name a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:23:01Z"
    - latency: 3.770559ms
      message: 'load-balancer-api-external: tcp connection to a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:22:01Z"
    - latency: 8.047644ms
      message: 'load-balancer-api-external: resolved host name a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:22:01Z"
    - latency: 5.19602ms
      message: 'load-balancer-api-external: tcp connection to a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:21:01Z"
    - latency: 8.168041ms
      message: 'load-balancer-api-external: resolved host name a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:21:01Z"
    - latency: 4.804781ms
      message: 'load-balancer-api-external: tcp connection to a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:20:01Z"
    - latency: 8.201673ms
      message: 'load-balancer-api-external: resolved host name a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:20:01Z"
    - latency: 4.976669ms
      message: 'load-balancer-api-external: tcp connection to a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:19:01Z"
    - latency: 8.190919ms
      message: 'load-balancer-api-external: resolved host name a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:19:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-16T19:52:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-253-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-253.ec2.internal
      uid: caffa9b8-7f71-4173-a1ae-2d52d7229beb
    resourceVersion: "46646"
    uid: 3f8cac77-ea16-4648-899f-02af4a9fc44d
  spec:
    sourcePod: network-check-source-6947749cfc-78dqb
    targetEndpoint: a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-16T19:59:01Z"
      message: 'load-balancer-api-internal: tcp connection to a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.552505ms
      message: 'load-balancer-api-internal: tcp connection to a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:23:01Z"
    - latency: 7.292618ms
      message: 'load-balancer-api-internal: resolved host name a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:23:01Z"
    - latency: 3.775459ms
      message: 'load-balancer-api-internal: tcp connection to a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:22:01Z"
    - latency: 7.987142ms
      message: 'load-balancer-api-internal: resolved host name a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:22:01Z"
    - latency: 5.173129ms
      message: 'load-balancer-api-internal: tcp connection to a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:21:01Z"
    - latency: 8.053501ms
      message: 'load-balancer-api-internal: resolved host name a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:21:01Z"
    - latency: 4.891098ms
      message: 'load-balancer-api-internal: tcp connection to a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:20:01Z"
    - latency: 8.149448ms
      message: 'load-balancer-api-internal: resolved host name a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:20:01Z"
    - latency: 4.977077ms
      message: 'load-balancer-api-internal: tcp connection to a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:19:01Z"
    - latency: 8.144132ms
      message: 'load-balancer-api-internal: resolved host name a9328f96070a94002a8f0e10f4bcc82a-5b5d377a5d39f3a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:19:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-16T19:52:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-253-to-network-check-target-ip-10-0-134-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-253.ec2.internal
      uid: caffa9b8-7f71-4173-a1ae-2d52d7229beb
    resourceVersion: "52303"
    uid: 77a54f91-85d4-4481-9fae-41f35446f087
  spec:
    sourcePod: network-check-source-6947749cfc-78dqb
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-16T20:00:01Z"
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.263875ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:28:01Z"
    - latency: 2.057583ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:27:01Z"
    - latency: 1.915928ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:26:01Z"
    - latency: 2.134847ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:25:01Z"
    - latency: 2.021041ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:24:01Z"
    - latency: 2.055121ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:23:01Z"
    - latency: 1.758163ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:22:01Z"
    - latency: 2.128936ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:21:01Z"
    - latency: 1.520651ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:20:01Z"
    - latency: 2.151791ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:19:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-16T19:52:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-253-to-network-check-target-ip-10-0-138-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-253.ec2.internal
      uid: caffa9b8-7f71-4173-a1ae-2d52d7229beb
    resourceVersion: "52301"
    uid: 714fa82b-ff55-461d-b97f-1e7b1c21cd95
  spec:
    sourcePod: network-check-source-6947749cfc-78dqb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-16T20:00:01Z"
      message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 939.728µs
      message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:28:01Z"
    - latency: 962.102µs
      message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:27:01Z"
    - latency: 811.379µs
      message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:26:01Z"
    - latency: 1.070651ms
      message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:25:01Z"
    - latency: 1.082271ms
      message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:24:01Z"
    - latency: 1.397902ms
      message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:23:01Z"
    - latency: 856.541µs
      message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:22:01Z"
    - latency: 1.138777ms
      message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:21:01Z"
    - latency: 842.593µs
      message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:20:01Z"
    - latency: 835.81µs
      message: 'network-check-target-ip-10-0-138-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:19:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-16T19:52:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-253-to-network-check-target-ip-10-0-139-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-253.ec2.internal
      uid: caffa9b8-7f71-4173-a1ae-2d52d7229beb
    resourceVersion: "52302"
    uid: 79df610a-62e5-42d0-9872-851e85ba91db
  spec:
    sourcePod: network-check-source-6947749cfc-78dqb
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-16T20:00:01Z"
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.804272ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:28:01Z"
    - latency: 1.758907ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:27:01Z"
    - latency: 1.66091ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:26:01Z"
    - latency: 1.836187ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:25:01Z"
    - latency: 1.754194ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:24:01Z"
    - latency: 1.787242ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:23:01Z"
    - latency: 1.489539ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:22:01Z"
    - latency: 1.899842ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:21:01Z"
    - latency: 1.85538ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:20:01Z"
    - latency: 1.853852ms
      message: 'network-check-target-ip-10-0-139-232: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:19:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-16T19:52:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-253-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-253.ec2.internal
      uid: caffa9b8-7f71-4173-a1ae-2d52d7229beb
    resourceVersion: "46645"
    uid: 74a29333-2143-40fd-baff-f7acbcf71438
  spec:
    sourcePod: network-check-source-6947749cfc-78dqb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-16T19:59:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 962.692µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:23:01Z"
    - latency: 1.751919ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:23:01Z"
    - latency: 773.276µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:22:01Z"
    - latency: 1.75797ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:22:01Z"
    - latency: 934.908µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:21:01Z"
    - latency: 1.935383ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:21:01Z"
    - latency: 923.572µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:20:01Z"
    - latency: 1.604331ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:20:01Z"
    - latency: 972.019µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-16T20:19:01Z"
    - latency: 1.792486ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-16T20:19:01Z"
kind: List
metadata:
  resourceVersion: ""