All the quoted containers are priority candidates to be moved to Kubernetes cluster.

I wonder if we'll keep rSTAGING.

The correct course of action is to:

We'll revisit this after Kubernetes cluster is ready, as that will drastically change the scope of Dwellers (development and build server for Docker images).

We'll revisit this after Kubernetes cluster is ready, as that will drastically change the scope of Dwellers (development and build server for Docker images).

Ysul at 12.1-RELEASE-p2 everywhere.

According /etc/os-release, all are now using CentOS 8.

Prune cluster configuration

Let's stop the scope of this change at "deploy everything we need to be able to initialize the cluster".

Move apt-transport-https to core

Fix chmod

Disable swap. Set systemd as cgroup manager.

Some love for 10-gre.jinja metadata

With MOTD, state applies correctly (tested at diff 4).

MOTD aren't executable files

MOTD

Rebase against CRLF -> LF fix

Fix CRLF. Ensuire IPv6 has network

Define network variable for ipv6 too

Update source path for IPv6 tunnel scripts

Fix alias. Use gre1 for wind -> cloud.

Rebase against 6e3319483fc3.

Use namespace to modify variable in for loop to comply with Jinja2 scope. Don't use /boot/loader.conf as state file (others states could modify it too).

Fix chmod for new files. Fix typo for dict parsing.