Letter to Santa Kube
jpetazzo.github.io
Letter to Santa Kube
1–10 of 30 posts
Re: Letter to Santa Kube
#2Regarding logs, I found this quite useful: https://github.com/johanhaleby/kubetail
Re: Letter to Santa Kube
#3As a relatively new Kubernetes user, the big thing on my wishlist is templates (for example so I can share YAML between my production and staging environments). Unfortunately the k8s team have already said "no" to that, and point to a list of alternatives. But without a simple solution that lots of people use, it's hard to know which one to pick and it doesn't look like any are particularly good. I took a quick look at a bunch of them and they seem to be either half-baked solutions that someone put up on GitHub, or tools that introduce way more complexity than I need right now (like Helm).
Re: Letter to Santa Kube
#4As a relatively new Kubernetes user, the big thing on my wishlist is templates (for example so I can share YAML between my production and staging environments). Unfortunately the k8s team have already said "no" to that, and point to a list of alternatives. But without a simple solution that lots of people use, it's hard to know which one to pick and it doesn't look like any are particularly good. I took a quick look…
[deleted]
Re: Letter to Santa Kube
#5As a relatively new Kubernetes user, the big thing on my wishlist is templates (for example so I can share YAML between my production and staging environments). Unfortunately the k8s team have already said "no" to that, and point to a list of alternatives. But without a simple solution that lots of people use, it's hard to know which one to pick and it doesn't look like any are particularly good. I took a quick look…
helm recently(ish) added a helm template command to do client side rendering of a chart
So if you wanted to just create a folder with a Chart.yaml, and a templates/file.yml.tpl with some `{{.Values.foo}}` template strings
It is sufficient to just run `helm template --set foo=bar | kubectl apply -f -` at that point.
Idk if that is little enough complexity for you. Similarly I use https://github.com/gliderlabs/sigil a few places where I want to include specific fields from external json files
Re: Letter to Santa Kube
#6As a relatively new Kubernetes user, the big thing on my wishlist is templates (for example so I can share YAML between my production and staging environments). Unfortunately the k8s team have already said "no" to that, and point to a list of alternatives. But without a simple solution that lots of people use, it's hard to know which one to pick and it doesn't look like any are particularly good. I took a quick look…
But if you don't love YAML itself you might just wanna check out ksonnet: https://ksonnet.io/
Re: Letter to Santa Kube
#7Somewhat off-topic, but as someone interested in k8s, why is it seemingly such a pain to set up in non-"cloud" environments? I know that Rancher exists - and I'm waiting for 2.0 to drop before migrating to Rancher-managed k8s - but beyond that the whole "ecosystem" of k8s seems pretty unfriendly to get started in without using AWS/GCE/Azure/etc (to the point of not being able to set up a cluster on bare metal at all!). Am I missing something here?
Re: Letter to Santa Kube
#8Somewhat off-topic, but as someone interested in k8s, why is it seemingly such a pain to set up in non-"cloud" environments? I know that Rancher exists - and I'm waiting for 2.0 to drop before migrating to Rancher-managed k8s - but beyond that the whole "ecosystem" of k8s seems pretty unfriendly to get started in without using AWS/GCE/Azure/etc (to the point of not being able to set up a cluster on bare metal at all!…
Check out Kubeadm. It's by far the best way to do k8s on Bare metal right now in terms of ease of use.
If you want something highly customizable, check out kubespray, which is basically a big fat ansible playbook which will deployment k8s almost anywhere.
Re: Letter to Santa Kube
#9As a relatively new Kubernetes user, the big thing on my wishlist is templates (for example so I can share YAML between my production and staging environments). Unfortunately the k8s team have already said "no" to that, and point to a list of alternatives. But without a simple solution that lots of people use, it's hard to know which one to pick and it doesn't look like any are particularly good. I took a quick look…
I just hacked together a solution using Jinja2. I literally throw template strings in whatever fields I need templated and render the whole thing to /tmp/ using a stupid simple python script. It's not pretty, and admittedly it's a little fragile and home spun, but it works.
Re: Letter to Santa Kube
#10As a relatively new Kubernetes user, the big thing on my wishlist is templates (for example so I can share YAML between my production and staging environments). Unfortunately the k8s team have already said "no" to that, and point to a list of alternatives. But without a simple solution that lots of people use, it's hard to know which one to pick and it doesn't look like any are particularly good. I took a quick look…
You can use any templating system you like, then "| kubectl create -f -"
I would like YAML includes, or some way to re-use templates directly. It's mildly inconvenient to have all of my env vars templated, but to require N copies for N variants on runcommand / base name / port / etc. I could Xzibit templates in my templates I suppose, by having a simpler format than YAML with #include would be awesome.