News for hackers. Stuff that matters.
Re:Kubernetes 1.6: Multi-user, Multi-workloads at Scale by jondubois on Wednesday March 29, 2017 @06:54AM (#13984912)
I think it's the holy grail for stateless services. For stateful systems though, (that need to persist data) things can be tricky. Maybe the improved node affinity features in this release will improve things but I still feel limited because I can't seem to find a way to permanently bind a Pod to a specific host's file system. They keep pushing for NFS or other complex network file systems that add huge network I/O overheads instead of letting you deal with distributed storage across multiple hosts yourself (which would work better with most new database engines that have built-in cluster support). Last time I checked, you COULD bind a Pod to the underlying host's file system but the documentation says that this is only for debugging purposes and not suitable for production.
Re:Kubernetes 1.6: Multi-user, Multi-workloads at Scale by vishh on Thursday March 30, 2017 @07:10PM (#13999741)
FYI: Local Storage for stateful services will be tackled in the upcoming releases - https://github.com/kubernetes/community/pull/306