apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T17:01:07Z"
    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: 1358fd0c-3280-46ef-8fa6-e00a4873ed69
    resourceVersion: "53464"
    uid: 511ede28-3e4a-4caa-928a-d9825c6d4dc2
  spec:
    sourcePod: network-check-source-56499946bc-d5kdr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T17:08:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.455358ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:36:09Z"
    - latency: 953.463µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:35:09Z"
    - latency: 1.418526ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:34:09Z"
    - latency: 887.989µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:33:09Z"
    - latency: 1.073957ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:32:09Z"
    - latency: 1.161792ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:31:09Z"
    - latency: 1.671141ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:30:09Z"
    - latency: 924.083µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:29:09Z"
    - latency: 1.121352ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:28:09Z"
    - latency: 1.283703ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:27:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T17:01:07Z"
    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: 1358fd0c-3280-46ef-8fa6-e00a4873ed69
    resourceVersion: "54472"
    uid: 705f641f-9f39-49c4-8f12-5d4895419c17
  spec:
    sourcePod: network-check-source-56499946bc-d5kdr
    targetEndpoint: a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T17:07:09Z"
      message: 'load-balancer-api-external: tcp connection to a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.744139ms
      message: 'load-balancer-api-external: tcp connection to a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:37:09Z"
    - latency: 9.963215ms
      message: 'load-balancer-api-external: resolved host name a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:37:09Z"
    - latency: 4.153556ms
      message: 'load-balancer-api-external: tcp connection to a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:36:09Z"
    - latency: 9.301352ms
      message: 'load-balancer-api-external: resolved host name a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:36:09Z"
    - latency: 4.459433ms
      message: 'load-balancer-api-external: tcp connection to a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:35:09Z"
    - latency: 8.839354ms
      message: 'load-balancer-api-external: resolved host name a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:35:09Z"
    - latency: 4.427491ms
      message: 'load-balancer-api-external: tcp connection to a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:34:09Z"
    - latency: 8.736459ms
      message: 'load-balancer-api-external: resolved host name a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:34:09Z"
    - latency: 3.723054ms
      message: 'load-balancer-api-external: tcp connection to a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:33:09Z"
    - latency: 8.477276ms
      message: 'load-balancer-api-external: resolved host name a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:33:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T17:01:07Z"
    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: 1358fd0c-3280-46ef-8fa6-e00a4873ed69
    resourceVersion: "54473"
    uid: e24fefb2-3084-4a91-91fd-41741de59777
  spec:
    sourcePod: network-check-source-56499946bc-d5kdr
    targetEndpoint: a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T17:07:09Z"
      message: 'load-balancer-api-internal: tcp connection to a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.755903ms
      message: 'load-balancer-api-internal: tcp connection to a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:37:09Z"
    - latency: 9.88231ms
      message: 'load-balancer-api-internal: resolved host name a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:37:09Z"
    - latency: 4.185297ms
      message: 'load-balancer-api-internal: tcp connection to a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:36:09Z"
    - latency: 9.219968ms
      message: 'load-balancer-api-internal: resolved host name a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:36:09Z"
    - latency: 4.391071ms
      message: 'load-balancer-api-internal: tcp connection to a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:35:09Z"
    - latency: 8.751737ms
      message: 'load-balancer-api-internal: resolved host name a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:35:09Z"
    - latency: 3.155103ms
      message: 'load-balancer-api-internal: tcp connection to a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:34:09Z"
    - latency: 8.713436ms
      message: 'load-balancer-api-internal: resolved host name a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:34:09Z"
    - latency: 3.80371ms
      message: 'load-balancer-api-internal: tcp connection to a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:33:09Z"
    - latency: 8.442517ms
      message: 'load-balancer-api-internal: resolved host name a58c4d9a139e54079bc3dcb508392f9d-9aafa295a6f65741.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:33:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T17:01:07Z"
    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: 1358fd0c-3280-46ef-8fa6-e00a4873ed69
    resourceVersion: "53461"
    uid: f9762f19-d2a7-4367-ab18-99beff22c9da
  spec:
    sourcePod: network-check-source-56499946bc-d5kdr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T17:08:09Z"
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.50262ms
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:36:09Z"
    - latency: 1.998618ms
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:35:09Z"
    - latency: 1.095098ms
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:34:09Z"
    - latency: 1.106619ms
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:33:09Z"
    - latency: 1.002829ms
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:32:09Z"
    - latency: 2.203651ms
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:31:09Z"
    - latency: 1.311109ms
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:30:09Z"
    - latency: 764.524µs
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:29:09Z"
    - latency: 1.005715ms
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:28:09Z"
    - latency: 1.004723ms
      message: 'network-check-target-ip-10-0-132-15: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:27:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T17:01:07Z"
    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-134-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-15.ec2.internal
      uid: 1358fd0c-3280-46ef-8fa6-e00a4873ed69
    resourceVersion: "53463"
    uid: 59445bf7-6fc1-40fe-abfb-0dc5b443224c
  spec:
    sourcePod: network-check-source-56499946bc-d5kdr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T17:08:09Z"
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.191945ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:36:09Z"
    - latency: 2.314975ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:35:09Z"
    - latency: 2.197693ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:34:09Z"
    - latency: 2.281333ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:33:09Z"
    - latency: 2.309454ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:32:09Z"
    - latency: 1.895627ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:31:09Z"
    - latency: 2.327097ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:30:09Z"
    - latency: 2.018103ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:29:09Z"
    - latency: 2.423232ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:28:09Z"
    - latency: 2.630428ms
      message: 'network-check-target-ip-10-0-134-244: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:27:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T17:01:07Z"
    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-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-15.ec2.internal
      uid: 1358fd0c-3280-46ef-8fa6-e00a4873ed69
    resourceVersion: "53462"
    uid: 95949b03-70c5-4688-a04c-690f190d823f
  spec:
    sourcePod: network-check-source-56499946bc-d5kdr
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T17:08:09Z"
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.887323ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:36:09Z"
    - latency: 1.63804ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:35:09Z"
    - latency: 1.566983ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:34:09Z"
    - latency: 1.588193ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:33:09Z"
    - latency: 1.597208ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:32:09Z"
    - latency: 1.789695ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:31:09Z"
    - latency: 2.163938ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:30:09Z"
    - latency: 1.414738ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:29:09Z"
    - latency: 1.793254ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:28:09Z"
    - latency: 1.771603ms
      message: 'network-check-target-ip-10-0-136-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:27:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T17:01:07Z"
    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: 1358fd0c-3280-46ef-8fa6-e00a4873ed69
    resourceVersion: "54469"
    uid: 42c02c13-2406-49e1-b3ac-56d4c0dd70ad
  spec:
    sourcePod: network-check-source-56499946bc-d5kdr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T17:07:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.657µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:37:09Z"
    - latency: 2.020438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:37:09Z"
    - latency: 1.010311ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:36:09Z"
    - latency: 1.736056ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:36:09Z"
    - latency: 743.359µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:35:09Z"
    - latency: 2.163284ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:35:09Z"
    - latency: 845.221µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:34:09Z"
    - latency: 2.159252ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:34:09Z"
    - latency: 904.95µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T17:33:09Z"
    - latency: 1.816944ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T17:33:09Z"
kind: List
metadata:
  resourceVersion: ""