News for hackers. Stuff that matters.
Re:Docker Compose reads your “.env” without opt-out by hosh on Thursday October 17, 2019 @03:31PM (#21285572)
I'm more than willing to run K8S on my personal machine in the form of microk8s, k3s, minikube, and similar cut-down versions of k8s.
Re:Docker Compose reads your “.env” without opt-out by arcticfox on Thursday October 17, 2019 @05:49PM (#21286664)
The others are probably fine, but for anyone thinking about this, minikube uses 50% CPU even on powerful machines for no reason [0]. I switched to kind and it works perfectly, super lightweight.

[0] https://github.com/kubernetes/minikube/issues/3207

Re:Docker Compose reads your “.env” without opt-out by hosh on Thursday October 17, 2019 @08:08PM (#21287506)
I have used minikube before. Back when it was using localkube, it was ok. It isn't as much now. (Now, it uses kubeadm to bring up the full suite).

microk8s might not give as much gains.

k3s from Rancher actually cuts out a lot of code, and from I hear, can run fine on Rapsberry Pis.

I have not heard of "kind", but neat.

Re:Docker Compose reads your “.env” without opt-out by verdverm on Thursday October 17, 2019 @08:15PM (#21287547)
Using the KVM driver reduces minkube cpu waste a lot, only supported on Linux...
Re:Docker Compose reads your “.env” without opt-out by idnefju on Thursday October 17, 2019 @08:43PM (#21287684)
do you have any article links about your kind setup?
Re:Docker Compose reads your “.env” without opt-out by hosh on Friday October 18, 2019 @10:25AM (#21291619)
I don't know about the other guy's setup, but here's the github repo: https://github.com/kubernetes-sigs/kind

KIND - Kubernetes In Docker