Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bare-Metal Kubernetes with K3s

blog.alexellis.io

Post reply on HN
Print view View original

131–136 of 136 posts

Re: Bare-Metal Kubernetes with K3s

#131

Post by tutfbhuf »

ninjha wrote: post #89
nicolast wrote: post #85

Earlier quoted context omitted.

> Getting Kubernetes up and running isn't really the issue anymore, that's pretty easy to do. The tricky part is long term maintenance and storage. This times 100. Deploying basic clusters is easy. Keeping a test/dev-cluster running for a while? Sure. Keeping production clusters running (TLS cert TTLs expiring, anyone?), upgrading to new K8s versions, proper monitoring (the whole stack, not just your app or the contr…

I’m working on this right now. My theory is that having every cluster object defined in git (but with clever use of third party helm charts to reduce maintenance burden) is the way to go. Our cluster configuration is public[1] and I’m almost done with a blog post going over all the different choices you can make wrt the surrounding monitoring/etc infrastructure on a Kubernetes cluster. [1] https://github.com/ocf/kube…

If I already have an production cluster up and running for a while, how can I get it git tracked now?

Another question: how about things like autoscaler which automatically edits numbers in deployments, how to git track that?

Re: Bare-Metal Kubernetes with K3s

#132

Post by INTPenis »

rmdashrfstar wrote: post #129
aprdm wrote: post #123

Earlier quoted context omitted.

Are they OSS by any chance? And what kind of tasks do they do?

Just use Kubespray, not much sense in wasting time writing your own unless your intention is specifically learning how to manage cluster setup with stateless Ansible

I actually looked at kubespray first but first of all it did not work out of box as promised. And to troubleshoot it you basically had to know about kubernetes already.

So it made a lot of sense to start at the official docs. And while I'm reading the docs, why not build the cluster at the same time. And while I'm building the cluster, why not write each step down in Ansible so I won't have to repeat myself.

So end result is my own ansible setup that I'm happy with and I know inside and out.

It always bothered me to run other people's ansible playbooks. I'm too much of a control freak.

Re: Bare-Metal Kubernetes with K3s

#133

Post by cassianoleal »

xaduha wrote: post #94
cassianoleal wrote: post #88

Earlier quoted context omitted.

It has to start with something. It would be a lot weirder if the first revision had been a white paper. If you disagree with what's on the page, please add or edit the information there. With proper references, it will be appreciated by everyone that uses Wikipedia.

I'm saying the term is much older than this, don't be obtuse.

Most terms are much older than their corresponding Wikipedia pages. I'm really failing to see your point here.

Re: Bare-Metal Kubernetes with K3s

#134

Post by lifty »

xaduha wrote: post #130
lifty wrote: post #110

Earlier quoted context omitted.

I am a professional in the field for many years and your version of the term is not widely accepted. There is a wikipedia page which describes the accepted definition: https://en.wikipedia.org/wiki/Bare-metal_server

Man you guys are laughable, brandishing one wiki page like it's one true source. But nevermind that, several older ones were presented to you and crickets. https://en.wikipedia.org/wiki/Close_to_Metal https://en.wikipedia.org/wiki/Bare_machine https://wiki.c2.com/?CloseToTheMetal This term goes back to early 2000 at least.

If you read again my comment you will see that I made a point about how common the term is. Once again, your version of the definition is just not wide-spread. If you do a google search for "bare-metal", the vast majority of pages refer to the definition that me and the other posted mentioned.

Re: Bare-Metal Kubernetes with K3s

#135

Post by captn3m0 »

INTPenis wrote: post #103
mrweasel wrote: post #59

Getting Kubernetes up and running isn't really the issue anymore, that's pretty easy to do. The tricky part is long term maintenance and storage. I'm not really sure what people expect gain from these kinds of article, they're great as notes, but it's not something I'd use as a starting point for installing a production Kubernetes cluster. The initial setup of a Kubernetes cluster is something most HN readers could d…

I was one of those backwards people who opposed containers, until late 2019. My start was the official kubernetes docs, step by step. Try everything, write it down, make ansible playbooks. Even used some of their interactive training modules, but I quickly had my own cluster up in vagrant so didn't really need the online shell. Now we have two clusters at work, I have ansible playbooks I'm really happy with that help…

Do the playbooks rely on kubeadm internally for setup?

Re: Bare-Metal Kubernetes with K3s

#136

Post by ncrmro »

mitjam wrote: post #99
ncrmro wrote: post #2

I actually just got a NUC with 64gb ram. Alpine installed to encrypted NVMe zfs zpool. This runs KVM One of these guests is alpine with k3s (tried k3os, very limiting in a good way) that allows me to pass a host directory directly into the vm using p9 (tried nfs but lil heavy) So any storage needs get the benifit of regular snapshots, compression and sync to nas. Really wish it would be more know that k8 single node…

Can you explain what p9 is?

When you create or a edit a vm you can add a file system passthrough.

You mount this in your guest vms fstab and specify 9p in the options

Post reply on HN