Live data from Hacker News

Kubernetes 1.6: Multi-user, Multi-workloads at Scale

blog.kubernetes.io

1–10 of 36 posts

Re: Kubernetes 1.6: Multi-user, Multi-workloads at Scale

#3
post #2

I 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

#5
post #3
post #2

I 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

Thanks.

Re: Kubernetes 1.6: Multi-user, Multi-workloads at Scale

#6
One 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

#7
post #6

One 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.

But aren't the node IPs relatively constant, barring complete node failure? You could just whitelist all of the node IPs you'd expect to connect.

Re: Kubernetes 1.6: Multi-user, Multi-workloads at Scale

#8
Those who have used kubernetes so far, what is your opinion on the kubernetes ecosystem? Is this the holy grail? Is there anything missing that you would like to have?

I 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

#10
post #6

One 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.

I don't think there is even an open issue for this. You should file one!
Post reply on HN