6 ms·

Kubernetes the Hard Way – Vagrant, Ansible, No Cloud

39 points by meysamazad 3y ago

falcolas 3y ago
Old (sysad)man yells at cloud: Using provisioning software is not the "Hard Way". Does bring back memories of working with Docker in the early days though.
- ok_dad 3y ago
  Yea, I used some bash scripts to manage ~250 rack mounted servers running Linux with a bunch of custom kernel shit. I don’t even remember everything it did but they specifically couldn’t use virtualization with this system due to latency and only the software included with the OS distribution was allowed so no Ansible or anything.
  - drdaeman 3y ago
    > only the software included with the OS distribution was allowed so no Ansible or anything IIRC, Ansible, unlike Puppet or Salt, didn't require anything particular provisioned on the server - just old good SSH.
    - ok_dad 3y ago
      Yea, we were only allowed the tools on the ISO of one specific distribution even for the workstations! It was a secure closed network for testing stuff. My scripts were probably just a worse ansible. Occasionally I would threaten the servers aloud that I would “beat them with a stick” if they misbehaved, because I had a special USB stick which I would use to boot a mini distro that would format the server and pull the approved install image down and setup the network and stuff. It was easier to do that when something hung than diagnose it.
- anton5mith2 3y ago
  Right! I starred this awhile back, it’s the really hard way imo, really great for learning: https://github.com/ghik/kubernetes-the-harder-way https://github.com/ghik/kubernetes-the-harder-way
dijit 3y ago
Hrm, I have a repo like this for comparing Nomad and Agones. I even have inspec profiles to test everything and it even supports windows (agones is teaching kubernetes to run gameservers so Windows and Gameservers is common) Honestly I spent a good chunk of a month working on it, if there is any actual interest I could release it but I dont think anyone has the same problems I do.
- mannycalavera42 3y ago
  raised-hand-here :)
  - dijit 3y ago
    Here you go buddy; https://gitlab.com/jmh/agones-nomad-research https://gitlab.com/jmh/agones-nomad-research
    - mannycalavera42 3y ago
      thank you!
    - mrala 3y ago
      Thanks for sharing! It looks like the linked google docs are not public, though.
deleted 3y ago
[deleted]
INTPenis 3y ago
This is the only way for me. I generally have one repo for Terraform to provision the k8s nodes, wherever they may live, and another with Ansible to provision the k8s services and some basic operators like observability stack for example. But now I'm moving more into using atomic server OS so I'm doing everything in one Terraform repo with ignition (or cloudinit).
nunez 3y ago
getting kubernetes up and running is crazy easy these days, but this is still THE way to learn Kubernetes inside out. i wouldn't recommend doing this for production though unless you want to manage k8s as your day job.
musicale 3y ago
Kubernetes is always the hard way. Or the expensive way, which is also the hard way.

39 points by meysamazad 3y ago

Old (sysad)man yells at cloud: Using provisioning software is not the "Hard Way". Does bring back memories of working with Docker in the early days though.

ok_dad 3y ago
Yea, I used some bash scripts to manage ~250 rack mounted servers running Linux with a bunch of custom kernel shit. I don’t even remember everything it did but they specifically couldn’t use virtualization with this system due to latency and only the software included with the OS distribution was allowed so no Ansible or anything.
- drdaeman 3y ago
  > only the software included with the OS distribution was allowed so no Ansible or anything IIRC, Ansible, unlike Puppet or Salt, didn't require anything particular provisioned on the server - just old good SSH.
  - ok_dad 3y ago
    Yea, we were only allowed the tools on the ISO of one specific distribution even for the workstations! It was a secure closed network for testing stuff. My scripts were probably just a worse ansible. Occasionally I would threaten the servers aloud that I would “beat them with a stick” if they misbehaved, because I had a special USB stick which I would use to boot a mini distro that would format the server and pull the approved install image down and setup the network and stuff. It was easier to do that when something hung than diagnose it.
anton5mith2 3y ago
Right! I starred this awhile back, it’s the really hard way imo, really great for learning: https://github.com/ghik/kubernetes-the-harder-way https://github.com/ghik/kubernetes-the-harder-way

dijit 3y ago

Hrm, I have a repo like this for comparing Nomad and Agones. I even have inspec profiles to test everything and it even supports windows (agones is teaching kubernetes to run gameservers so Windows and Gameservers is common) Honestly I spent a good chunk of a month working on it, if there is any actual interest I could release it but I dont think anyone has the same problems I do.

mannycalavera42 3y ago
raised-hand-here :)
- dijit 3y ago
  Here you go buddy; https://gitlab.com/jmh/agones-nomad-research https://gitlab.com/jmh/agones-nomad-research
  - mannycalavera42 3y ago
    thank you!
  - mrala 3y ago
    Thanks for sharing! It looks like the linked google docs are not public, though.

deleted 3y ago

[deleted]

INTPenis 3y ago

This is the only way for me. I generally have one repo for Terraform to provision the k8s nodes, wherever they may live, and another with Ansible to provision the k8s services and some basic operators like observability stack for example. But now I'm moving more into using atomic server OS so I'm doing everything in one Terraform repo with ignition (or cloudinit).

nunez 3y ago

getting kubernetes up and running is crazy easy these days, but this is still THE way to learn Kubernetes inside out. i wouldn't recommend doing this for production though unless you want to manage k8s as your day job.

musicale 3y ago

Kubernetes is always the hard way. Or the expensive way, which is also the hard way.