apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T08:07:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-247-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-247.us-west-2.compute.internal
      uid: 4d7f63c6-d7d9-4941-b15c-8ee4bf9f9b10
    resourceVersion: "81313"
    uid: e8be49d4-fa44-4459-8ce5-e7691ebdf503
  spec:
    sourcePod: network-check-source-6f78d59f99-2ngtk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T08:14:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.238521ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:49:21Z"
    - latency: 1.150294ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:48:21Z"
    - latency: 904.283µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:47:21Z"
    - latency: 1.355106ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:46:21Z"
    - latency: 1.375073ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:45:21Z"
    - latency: 3.960089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:44:21Z"
    - latency: 2.81214ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:43:21Z"
    - latency: 2.226328ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:42:21Z"
    - latency: 5.713472ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:41:21Z"
    - latency: 1.231522ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:40:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T08:07:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-247-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-247.us-west-2.compute.internal
      uid: 4d7f63c6-d7d9-4941-b15c-8ee4bf9f9b10
    resourceVersion: "81314"
    uid: 614150e6-556d-47d9-860a-a9f67d5313f7
  spec:
    sourcePod: network-check-source-6f78d59f99-2ngtk
    targetEndpoint: a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T08:13:21Z"
      message: 'load-balancer-api-external: tcp connection to a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 50.828262ms
      message: 'load-balancer-api-external: tcp connection to a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:49:21Z"
    - latency: 7.054419ms
      message: 'load-balancer-api-external: resolved host name a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:49:21Z"
    - latency: 53.185534ms
      message: 'load-balancer-api-external: tcp connection to a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:48:21Z"
    - latency: 7.422569ms
      message: 'load-balancer-api-external: resolved host name a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:48:21Z"
    - latency: 49.565358ms
      message: 'load-balancer-api-external: tcp connection to a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:47:21Z"
    - latency: 6.622575ms
      message: 'load-balancer-api-external: resolved host name a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:47:21Z"
    - latency: 55.158257ms
      message: 'load-balancer-api-external: tcp connection to a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:46:21Z"
    - latency: 6.673133ms
      message: 'load-balancer-api-external: resolved host name a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:46:21Z"
    - latency: 54.942581ms
      message: 'load-balancer-api-external: tcp connection to a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:45:21Z"
    - latency: 7.142741ms
      message: 'load-balancer-api-external: resolved host name a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:45:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T08:07:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-247-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-247.us-west-2.compute.internal
      uid: 4d7f63c6-d7d9-4941-b15c-8ee4bf9f9b10
    resourceVersion: "81315"
    uid: f029e194-1664-465b-9807-5a567c65b7a9
  spec:
    sourcePod: network-check-source-6f78d59f99-2ngtk
    targetEndpoint: a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T08:13:21Z"
      message: 'load-balancer-api-internal: tcp connection to a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.691255ms
      message: 'load-balancer-api-internal: tcp connection to a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:49:21Z"
    - latency: 7.111083ms
      message: 'load-balancer-api-internal: resolved host name a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:49:21Z"
    - latency: 51.567906ms
      message: 'load-balancer-api-internal: tcp connection to a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:48:21Z"
    - latency: 7.525912ms
      message: 'load-balancer-api-internal: resolved host name a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:48:21Z"
    - latency: 49.604625ms
      message: 'load-balancer-api-internal: tcp connection to a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:47:21Z"
    - latency: 6.592875ms
      message: 'load-balancer-api-internal: resolved host name a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:47:21Z"
    - latency: 54.674016ms
      message: 'load-balancer-api-internal: tcp connection to a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:46:21Z"
    - latency: 6.725093ms
      message: 'load-balancer-api-internal: resolved host name a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:46:21Z"
    - latency: 55.501022ms
      message: 'load-balancer-api-internal: tcp connection to a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:45:21Z"
    - latency: 7.165467ms
      message: 'load-balancer-api-internal: resolved host name a4c4bab8d27dd4bf6a9cd51fc9ec0bbf-5d8bc6b0cc418bd2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:45:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T08:07:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-247-to-network-check-target-ip-10-0-135-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-247.us-west-2.compute.internal
      uid: 4d7f63c6-d7d9-4941-b15c-8ee4bf9f9b10
    resourceVersion: "81323"
    uid: fe8802b4-51d5-4bf1-9b95-3f2ad7599029
  spec:
    sourcePod: network-check-source-6f78d59f99-2ngtk
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T08:14:22Z"
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 958.455µs
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:49:22Z"
    - latency: 2.38467ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:48:22Z"
    - latency: 1.010259ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:47:22Z"
    - latency: 2.512986ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:46:22Z"
    - latency: 2.109523ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:45:22Z"
    - latency: 2.233571ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:44:22Z"
    - latency: 2.562755ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:43:22Z"
    - latency: 2.826552ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:42:22Z"
    - latency: 9.41245ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:41:22Z"
    - latency: 2.736336ms
      message: 'network-check-target-ip-10-0-135-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:40:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T08:07:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-247-to-network-check-target-ip-10-0-136-103
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-247.us-west-2.compute.internal
      uid: 4d7f63c6-d7d9-4941-b15c-8ee4bf9f9b10
    resourceVersion: "81308"
    uid: 1ddc5bbf-a521-40a6-9cb1-5c41c5085838
  spec:
    sourcePod: network-check-source-6f78d59f99-2ngtk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T08:14:21Z"
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.170928ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:49:21Z"
    - latency: 2.491847ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:48:21Z"
    - latency: 2.216302ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:47:21Z"
    - latency: 2.36753ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:46:21Z"
    - latency: 2.011027ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:45:21Z"
    - latency: 9.433159ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:44:21Z"
    - latency: 2.316651ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:43:21Z"
    - latency: 3.774999ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:42:21Z"
    - latency: 6.440394ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:41:21Z"
    - latency: 2.319777ms
      message: 'network-check-target-ip-10-0-136-103: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:40:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T08:07:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-247-to-network-check-target-ip-10-0-139-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-247.us-west-2.compute.internal
      uid: 4d7f63c6-d7d9-4941-b15c-8ee4bf9f9b10
    resourceVersion: "81307"
    uid: df8b1e22-703e-4349-9f51-8a68d8852852
  spec:
    sourcePod: network-check-source-6f78d59f99-2ngtk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T08:14:21Z"
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.755872ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:49:21Z"
    - latency: 1.068474ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:48:21Z"
    - latency: 1.118137ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:47:21Z"
    - latency: 1.009859ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:46:21Z"
    - latency: 1.027094ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:45:21Z"
    - latency: 5.003761ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:44:21Z"
    - latency: 3.519473ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:43:21Z"
    - latency: 892.933µs
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:42:21Z"
    - latency: 9.013585ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:41:21Z"
    - latency: 1.35981ms
      message: 'network-check-target-ip-10-0-139-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:40:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T08:07:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-247-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-247.us-west-2.compute.internal
      uid: 4d7f63c6-d7d9-4941-b15c-8ee4bf9f9b10
    resourceVersion: "81310"
    uid: ba8332bf-f4b0-4b29-87e5-4acf8af9f94e
  spec:
    sourcePod: network-check-source-6f78d59f99-2ngtk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T08:13:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.405401ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:49:21Z"
    - latency: 2.376443ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:49:21Z"
    - latency: 952.37µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:48:21Z"
    - latency: 2.520958ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:48:21Z"
    - latency: 2.723032ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:47:21Z"
    - latency: 1.936318ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:47:21Z"
    - latency: 936.902µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:46:21Z"
    - latency: 1.912317ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:46:21Z"
    - latency: 970.633µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T08:45:21Z"
    - latency: 2.071967ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T08:45:21Z"
kind: List
metadata:
  resourceVersion: ""