website

I'm using Terraform to deploy Docker containers. Terraform's docker_container resource has a lovely 'upload' feature which one can use to upload files into the container. I make Terraform load server config files (or use multi-line strings in the .tf file), perform variable replacement, then destroy Docker containers and recreate them with updated config files. All persistent data is stored in directories bind-mounted into the Docker container. Terraform has some limitations. For example, one deployment cannot deploy hosts and their containers [1]. And there is no usable support for rolling deployments [2, 3]. So I've ended up with a 4-stage deployment: host-set1, containers on host-set1, host-set2, containers on host-set2. I also use Terraform to deploy the servers to my laptop during development. Docker for Mac works well. Someda

Can you point me to a good doc on deploying a small production service on k8s? The official documentation provides a super simple tutorial, and then nothing. There's not even documentation of the primary config file. Frustrating. https://github.com/kubernetes/website/issues/19139

I started learning Kubernetes and was overwhelmed. The biggest problem was the missing docs. I filed a Github issue asking for missing Kubernetes YAML docs: https://github.com/kubernetes/website/issues/19139 Google will ignore it like all of the tickets I file. The fact is that Google is in the business of making money and they are focused on enterprise users. Enterprise users are not sensitive to integration difficulty since they can just throw people at any problems. So eventually everything Google makes will become extremely time-consuming to learn and difficult to use. They're becoming another Oracle.

I submitted a PR to fix it :D https://github.com/kubernetes/website/pull/13417

I'm one of the leads for docs. We've got an issue open for the blog CSS: https://github.com/kubernetes/website/issues/13412

> love to see the topic of user feedback on Hacker News I'm also very interested in the topic, but in a slightly different domain. I'm on a mission to get "was this page helpful?" feedback widgets on all technical documentation across the web. Recently I just helped the Kubernetes folks [1] add it to their docs site. One of my high-level goals is to get the docs community to aggregate all of this data in order to benchmark typical ratings for common types of documents. E.g. what's the typical rating for a tutorial? I also want us to start actively experimenting in order to validate what kinds of changes lead to meaningful improvements in documentation. E.g. adding examples to conceptual overviews improves the rating by 5% (not real numbers). Find me on the interwebz if you'd like help implementing one of these systems in your docs, or wan

No, there is no concept of LTS in upstream Kubernetes yet. That's currently a job for the "distributions" (OpenShift, Canonical, GKE, Azure, etc). Regarding supported versions, it seems the project still aims to support 3 versions at a time. You can read more about it here: https://github.com/kubernetes/community/blob/master/contribu... You often find some confusing statements about supported versions because sometimes they're talking about version skew between different components. More about that here: https://github.com/kubernetes/website/issues/7103

Take a look at Kubernetes https://github.com/kubernetes/kubernetes.github.io/issues

Here's a link to the kubernetes docs repo. https://github.com/kubernetes/kubernetes.github.io There is also a special interest group for documentation on the kubernetes slack channel #sig-docs Would love some help updating the kubernetes/minikube docs :)

The docs in github/kubernetes/kubernetes.github.io are what is rendered. The documentation was broken apart at some point. 90% of the time (if not always) when I'm looking for a file mentioned in the actual website docs the link (if one exists) is to the kubernetes repo, not the kubernetes.io repo. Going to the location in the kubernetes repo just gives you a loop back to the website you were just viewing. If you've used k8s docs for any significant amount of time I can pretty much guarantee that you've encountered this. Here's an example; limit-example.yml which is mentioned over and over in the limitrange docs but the file is nowhere to be found; http://kubernetes.io/docs/admin/limitrange/ If you don't know about the kubernetes.io repo (which someone who has never gone through looking for missing docs will not know about) you'll think t

One of my huge headaches in working with Kubernetes daily over the last year is how the documentation is dispersed. The documentation on the site will point you to manfiests in github.com/kubernetes/ which just point you back to the documentation on www.kubernetes.io. If you don't know that https://github.com/kubernetes/kubernetes.github.io/tree/mast... exists you're in for a bad time.