Kubernetes 1.6: Multi-user, Multi-workloads at Scale
blog.kubernetes.io
Kubernetes 1.6: Multi-user, Multi-workloads at Scale
1–10 of 36 posts
Re: Kubernetes 1.6: Multi-user, Multi-workloads at Scale
#2Re: Kubernetes 1.6: Multi-user, Multi-workloads at Scale
#3I couldn't find it easily, but is CronJob out of alpha? As always, great work. I have no regrets about choosing k8s.
Re: Kubernetes 1.6: Multi-user, Multi-workloads at Scale
#4I couldn't find it easily, but is CronJob out of alpha? As always, great work. I have no regrets about choosing k8s.
Re: Kubernetes 1.6: Multi-user, Multi-workloads at Scale
#5I couldn't find it easily, but is CronJob out of alpha? As always, great work. I have no regrets about choosing k8s.
No it hasn't. You can track the progress of CronJob by subscribing to the feature issue (which should generate fairly low email traffic): https://github.com/kubernetes/features/issues/19
Re: Kubernetes 1.6: Multi-user, Multi-workloads at Scale
#6Re: Kubernetes 1.6: Multi-user, Multi-workloads at Scale
#7One thing that's still missing but would be quite valuable is a good egress approach/configuration. For example, we use an external PostgreSQL provider in which I can configure access IPs. Since K8s nodes (on GKE) get different IPs, I have to be very loose with CIDR selection, which I don't like.
Re: Kubernetes 1.6: Multi-user, Multi-workloads at Scale
#8I have found kubernetes hard to learn. There are a lot of concepts. That in itself isn't bad, but I have found that the quality of the documentation is variable. Once I get past the basics tutorial, I have the feeling that I have landed in a big information dump that require expert knowledge ala the git man pages.
Re: Kubernetes 1.6: Multi-user, Multi-workloads at Scale
#9Looking forward to compare that with an autoscale solution I'm working on.
Re: Kubernetes 1.6: Multi-user, Multi-workloads at Scale
#10One thing that's still missing but would be quite valuable is a good egress approach/configuration. For example, we use an external PostgreSQL provider in which I can configure access IPs. Since K8s nodes (on GKE) get different IPs, I have to be very loose with CIDR selection, which I don't like.