Intune Shared Android Devices for QA: The Real Trade-off
A field note on choosing Dedicated with Entra Shared Device Mode or Fully Managed Intune enrollment for shared Android QA phones and tablets.
A field note on choosing Dedicated with Entra Shared Device Mode or Fully Managed Intune enrollment for shared Android QA phones and tablets.
A field note on choosing capacity over flash performance for an older Proxmox host, including RAID10 math, controller risk, cost, and migration impact.
A recovery-first field note: an earlier VM restore was unsatisfying, so compare Veeam, PBS and native Proxmox backup using the same isolated full-VM restore and host-rebuild criteria.
A practical, evidence-based VM-to-k3s migration checklist from a real Snipe-IT cutover: independent backups, data verification, NFS writes, TLS testing, DNS change and rollback.
A field note from a small k3s environment: etcd snapshots matter, but credible recovery also needs the original server token, GitOps state, database backups, persistent file protection and restore evidence.
A practical design note for building a resource-constrained Kubernetes developer platform on an existing k3s cluster with Rancher, isolated namespaces, quotas, dedicated workers and automatic cleanup.
A real troubleshooting sequence for QNAP-backed Kubernetes storage when root can write to an NFS PVC but the non-root application user receives Permission denied.
A practical architecture decision: Azure Arc for the existing k3s cluster, a stretched cluster, or separate on-premises k3s and Azure AKS.
This k3s migration inventory produced seven practical rules for deciding what belongs in Kubernetes, what stays on a VM and what should be retired.
Four worker nodes looked redundant until I mapped them back to the single Proxmox host underneath. This is the HA redesign before more workloads move to k3s.