This Annon get locked duo to off topic. So is their any update on this?
Off Tpoic and Subjective warning
Personally, I have those concern:
From Big pricture:
Any orchestrate of docker will create another K8s, In history they called borg/docker-swan And none care them any more.
Millions company prove that Kube standard is the best of best. Everything can implements with CRD and it’s controller.
And now: Create new docker-compose based Apps. That gone need recreate wheel from UI/UX to low level logic and absolutely gone facing security/no enought custom/extract common is diffcult/hard to scale/platform lock problems that k8s already solved.
From concrete problems:
First make a define
- Normal: Someone like a photographer can only make a simple click on webUI
- HomeLab: Nerds, Which has proper knowlage and ability to handle Hardware/Debian/K8s/K3s/Storage even coding
- Enterprise: Bussiness, Any lost will cause a directly/literal meaning “COST”
- Orchestrate: Human manual operating: Too slow, Taired on Repeatedly, Not Atomic Opetaion, Mistake when taired, Mistake when bad mood, Misktake when good mood, Misktake on whatever mood or even no mood!
All those predictable problem is about orchestrate which Kube solve from the very begining:
Performance and single-failure
Run some app on NAS meant for directly storage access. “Enterprise” use CSI because it’s a trade off between data security and access proformance. Even with RDMA local direct perfomance is better then remote acces, Because cables can’t break light speed.
But rember “Enterprise” has no single-failure problem. For “Normal” install PLEX/PhotoPrism/Immich/WebDAV to centralize all data. Buy two server and access though newwork is meanless cost: Both money and perfomance and even worse: introduce the single-failure problem.
Manage HostPath by K8s is way easier then rewrite some web console. And support CSI to extend backend. In docker/compose only hostpath/volume. Of couse you can say event CSI impelemnts on this. But “orchestrate”.
Networking
CNI can provide from simples NodePort to very complex networking like BGP with hi-performance IPVS. But dokcer/compopse can only provide NAT/host. And besides MetalLB need no host networking bind
Again, You can say there is manual alternative. But “orchestrate”
In face
Those two example shows IaaC and orchestrate is future, Because it’s:
Remove human (the change to make mistake)
Remove modifyable (the change to make mistake)
K3s in SCALE for years and very very very very very stable now, The eco (TrueCharts) is enought for most users ( 20% vs 80% law) And I can packing/wrote my own application.
So TrueNAS staffs absolutely aware “orchestrate”. Why still make this unimaginable breaking change ?
BTW
K9s is an excellent tool, Not accepting rebuttal.
