6 ms·
Kubernetes 1.6: Multi-user, Multi-workloads at Scale
- kentt 10y agoI couldn't find it easily, but is CronJob out of alpha? As always, great work. I have no regrets about choosing k8s.
- tzaman 10y agoOne 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.
- 013a 10y agoBut 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.
- bboreham 10y agoI don't think there is even an open issue for this. You should file one!
- seeekr 10y agoWouldn't The Right Way (TM) be to have a daemon running on the cluster that's watching either your nodes (if you want to allow access from all your nodes) or specific pods and then call your PostgreSQL provider's API to let it know about valid access IPs dynamically?
- xur17 10y agoThat's the approach we used when connecting to a legacy Mongo cluster from a GKE cluster. We ran a pod that subscribed to the Kubernetes api, and updated security group rules in AWS as the nodes changed.
- thesandlord 10y agoIs IP whitelisting your only option? I really haven't found a good way to pull this off in Kubernetes. You could set up and instance outside the cluster to act as a proxy, but that just feels like a very substandard solution. On GCP, you can use the SQL Proxy [1] to avoid IP whitelisting or manual SSL setup. Postgres on GCP is still beta, so you probably don't want to run a production DB with it, but hopefully your provider has a similar option. 1: https://cloud.google.com/sql/docs/postgres/sql-proxy https://cloud.google.com/sql/docs/postgres/sql-proxy (I work on Google Cloud)
- chatmasta 10y agoThis problem could be solved by finer grained control over network routing configuration in general. The problem seems to be that this configuration differs depending on what network virtualization technology/driver you choose, and so implementing it is best left outside the scope of kubernetes.
- FooBarWidget 10y agoThose 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.
- newsat13 10y agoYeah, I feel you. I found kubernetes very hard to learn as well. I wanted was to find a good tool to run a SaaS (to handle 10k users). Only after reading up a lot did I even realize that this was not for me. I had fallen into the Hackernews hype trap and thought kubernetes is the right tool for me. I am back to my simple docker based deploys in 5 EC2 instances. It's very much by hand but works with some simple instructions to follow on a wiki page. I have also found kubernetes labor hard to find. The ones I found were way too expensive for me (upwards of 150k USD).
- rodgerd 10y ago> I found kubernetes very hard to learn as well. This is why we went down the OpenShift root, but there are not shortage of people wrapping Kube in other things, which seems sensible for a lot of use cases.
- stephane-klein 10y agoI have deployed and I use OpenShift since more that one year but I think that Ansible Playbook is crappy. What is you feeling about that?
- Kubuxu 10y agoCheck out Nomad, I have no personal experience with it yet but it seems the best candidate so far for what we are planning in terms of docker deployment and so on.
- 10y ago
- dluc 10y agoTo author: custom metrics link is broken. Looking forward to compare that with an autoscale solution I'm working on.