Host server setup
This documents my adventure in setting up Tinkerbell
In This post (Part One) we’ll get the system ready. and go over some fundamental stuff.
In the followups, part two, and part three, we’ll actually use tinkerbell for awesomeness.
This is ground broken by many before me. Adam Otto at The container-solutions-blog has done a great job walking someone through this process in a three part blog:
As well as the following
- Aaron’s “geek gone crazy” blog post on tinkerbell
- based on the above blogpost: Tinkerbell’s baremetal walkthrough
in Part 1 of the container-solutions-blog blog series, Adam describes the moving parts.
To follow along here, You’ll need:
- a host from which to run the various tinkerbell components.
- This host should have (at least) two network interfaces.
- The host should be using hardware which runs linux well.
- This host will run several docker containers which comprise the Tinkerbell Stack.
- We cover installing
Docker
in This Blog post
- We cover installing
- A network segment allocated for Tinkerbell to use to provision hosts.
HP T730 additional ethernet interface for pxe
installed ubuntu 22.04
Quick oneliner to install any needed packages:
|
|
Not strictly necessary packages
These aren’t NECESSARY, but I’ve found them useful to have:
root@tinky:~#
apt-get install memtest86+ htop silversearcher-ag tcputils sockstat silversearcher-ag bpytop
Journald is cool, but it’s a good idea to set the local log to be small and push all yer systemic logs to a log ingestion host.
systemd-resolved
is a pretty nifty local caching nameserver.
Check to see if it’s enabled by running resolvectl
:
If systemd-resolved isn’t configured, you’ll see a message like this:
This is fairly straightforward:
root@tinky:~#
systemctl enable systemd-resolved && systemctl start systemd-resolved
There are a few files that need be put in place which are specific to your environment:
/etc/systemd/resolved.conf
/etc/systemd/resolved.conf
, /etc/resolv.conf
This file controls how systemd-resolved works overall.
Documentation: [here][resolved.conf]
Here’s an example file. Obviously, adjust the DNS
, FallbackDNS
, and Domains
entries to be relevant to your environment.
root@tinky:~#
apt-get install libnss-mymachines libnss-resolve dialog
Lets continue to Part Two, where we configure Tinkerbell or Part Three, where we provision our first node!