xkarga00

You have confused BestEffort with Burstable. Agreed about the docs.

> This is the exact opposite of what Kubernetes seek to provide

Not true. You can have dedicated machines for your db instances, check out 1. node affinity 2. Statefulsets.

Statefulsets are designed to provide consistency (no "split brain"), stable network identity ("at a consistent address"), stable storage identity ("and that the data directory will be available to the server as soon as it starts up"). Those features are beta but it's a matter of time (hardening and the likes) before we tut them stable.

> why would you?

For all the same reasons you would run any other workload on the same platform.

That's the problem, we are only _materially_ better. It is sad we still cannot figure that out.

What's your solution?

rkt is still not fully functional as a container runtime for kubelet[1]. kubelet is the underlying daemon used by Kubernetes and OpenShift for running containers. I am not sure if and when rkt will reach feature parity with the docker runtime but once it does, we wouldn't need to do much and enable it in OpenShift.

[1] https://kubernetes.io/docs/getting-started-guides/rkt/notes/

Export needs more work.

FWIW, you can constrain a DaemonSet to run on a specific set of nodes by using nodeAffinity but you would need to label those nodes appropriately which you are going to do anyway in a production cluster (use a specific set of nodes for running infra components such as routers or registries).

I think this is about policing yourself and understanding the outcome of your own acts rather than policing others of their acts. Imagine a community where everyone is responsible for their own behavior.

> wouldn't being able to say "I want to donate X gb of disk space, cache some stuff for people to use" be better?

I believe this is addressed by Filecoin

http://filecoin.io/filecoin.pdf

Previous discussion on IPFS:

https://news.ycombinator.com/item?id=12772093

https://news.ycombinator.com/item?id=10187555

https://news.ycombinator.com/item?id=8069836

https://news.ycombinator.com/item?id=11134766

https://news.ycombinator.com/item?id=9321209

Does anybody have any info on the development of Filecoin (sister protocol of IPFS)?

You may want to check out lowRISC.

http://www.lowrisc.org/

https://github.com/lowRISC

Naive question: Why should I use this over CoinCap? I'm running it on Android and it has been a pretty sweet app to keep track of cc

I ditched Facebook two years ago for all the principles stated in the article (among other reasons) and I have never looked back. I am literately a healthier person ever since. Minimalism is a way of life, having to think about or deal with less things or situations helps me handle those better. Great article.

Edit: One nit, the author mentions Orwell to describe today's social media. I would say it's more like what Aldous Huxley described in Brave New World and Neil Postman embodied in Amusing Ourselves To Death rather than an Orwellian world.

There is a separation of concerns slowly baked into Kubernetes in that as a normal user you shouldn't need to manage the infrastracture.

I am working for Red Hat on OpenShift for the past two years almost and it has been more like 3, working with the Kubernetes community.

The One Straw Revolution has been very inspiring for me. Highly recommended to anyone who wants to learn about natural farming.

I don't think there is a distinction between a supporting and a developing organization at this point in the Kube ecosystem. At Red Hat we offer an enterprise version of Kube (OpenShift v3) and at the same time we contribute a ton of stuff back upstream. Personally it has been a great experience for me working with engineers from Google, different companies, and even individual contributors and I am pretty sure most if not all of my coworkers feel the same thing.

Define "successful financial systems"

Disclaimer: I work for Red Hat on OpenShift v3, an open-source enterprise-ready distribution of Kubernetes.

We have solved #2 by deploying an internal docker registry [1], push to it once a build succeeds, and automatically (or not) trigger deployments once an expected image lands in it [2].

In the future we will support webhooks so you can trigger deployments from external registries such as quay.io or DockerHub.

You can have a look at the all-in-one VM we have:

git clone https://github.com/openshift/origin

cd origin

vagrant up

vagrant ssh

oc cluster up

The last command will spin up a cluster with a docker registry, a HTTP router, and a bunch of images for you to play around with.

https://asciinema.org/a/49402

[1] The same underlying registry thay powers DockerHub: https://github.com/docker/distribution

[2] A Kubernetes controller loop that watches for new images and triggers new deployments.

See, from my point of view enough was added to the discussion with just a comment about a "niche book". Rest of the comments on it are mere reactions of ego:)

Wow, I am not sure how you managed to infer my lack of appreciation for people's freedom of choice merely from a title of a book. You may understand what I am trying to convey, if you ever read the book.

Ever heard of Amusing Ourselves to Death by Neil Postman?

I don't understand why tootie is getting downvoted but it seems that both of you talk about the same thing, albeit with exactly the opposite wording.

I also find weird that a subject like missing features in Go has beaten so much to death and still it continues to be a thing after so many explanations. See https://news.ycombinator.com/item?id=11888219

Why not? It's cool to point things out.

I have been working as a Go programmer for the past two years and I really love the language but dependency management has been one of the biggest pains for me. Godep really sucks (that's what we use in my current gig - we plan on switching to Glide, still haven't played around with it) and I am not sure I like the fact that I need to go out in the wild and choose between the rest of the existing solutions. I would prefer to have something that works ootb. The Rust team really got this right and Cargo is amazing. One of the main reason I have been dabbling with Rust lately.

Great sum up of Tarkovsky! Legend.

Anonymity is good not per se but because it implies privacy. Let's not argue if privacy is a good thing or not. Anonymity also supersedes fake identities.

I never considered myself as a bitcoin enthusiast but I am enthusiastic about digital cryptocurrencies in general for most of the reasons you mentioned. Bitcoin (and all other cryptocurrencies) is not there yet but most of those are problems that cryptocurrencies target to solve.

An example: you could never move money over the wire anonymously before crypto came in. Well, except if you had a fake identity, which is illegal. Now you can. Of course, you need to be a security expert in order to do it but ultimately UX will get there. I wasn't around at the early days of internet but I am pretty sure if my mother could access it back then she would have no idea what to do. And here she is calling me on Skype every other night.

Another example: There are millions of people who cannot afford buying a computer as you already said but possess low-cost mobile phones. There are already a bunch of bitcoin startups targeting that market. Apps and tools will eventually evolve up to the point where they will be accessible, easy-to-use, scam-free, safe. We just need to build them.