awx-on-k3s VS k3s

I used THIS GUIDE to configure Kerberos and it's more-or-less working fine. It's just that I'm using hostnames and AWX has issues picking correct AD domain (I have multiple domains specified), despite having the following:

Ref: https://github.com/kurokobo/awx-on-k3s/tree/main/builder

Haha, I wasn't even aware there were any other AWX-on-K3s playbooks out there! Like there's https://github.com/kurokobo/awx-on-k3s, but this playbook I've made is basically just a wrapper for it.

short heads-up: i started a position at a new company, the prior employee didn‘t do any documentation. i have a awx 19 on k3s in a constrained environment (multiple ads/proxies etc… firewall rings etc.) where all the setup seems to be happen with an older/modified version of this and someone tried to update with [https://github.com/ansible/awx-operator](this (awx operator)) but failed multiple times. no one touched it since.

I just deployed AWX latest version using k3s, following this neat guide: https://github.com/kurokobo/awx-on-k3s/

Give this a try, it's a step-by-step guide to setting it all up using k3s (mini/single-node Kubernetes): https://github.com/kurokobo/awx-on-k3s

I would recommend this guide: https://github.com/kurokobo/awx-on-k3s it's by far the best guide to install operator and awx afterwards out there on a kubernetes cluster/single node.

For self-hosting I've found https://k3s.io to be really good from the SUSE people. Works on basically any Linux distro and makes self-hosting k8s not miserable.

Yes it’s going to depend on which k8s distribution you’re using. We have work in-progress for k3s to natively support nix-snapshotter: https://github.com/k3s-io/k3s/pull/9319

For other distributions, nix-snapshotter works with official containerd releases so it’s just a matter of toml configuration and a systemd unit for nix-snapshotter.

We run Kubernetes outside of NixOS, but yes the NixOS modules provided by the nix-snapshotter certainly make it simple.

K3S: is a lightweight distribution of Kubernetes that is designed for resource-constrained environments. It is an excellent option for running Kubernetes on a virtual machine or cloud server.

I recently purchased a used Lenovo M900 Think Centre (i7 with 32GB RAM) from eBay to expand my mini-homelab, which was just a single Synology DS218+ plugged into my ISP's router (yuck!). Since I've been spending a big chunk of time at work playing around with Kubernetes, I figured that I'd put my skills to the test and run a k3s node on the new server. While I was familiar with k3s before starting this project, I'd never actually run it before, opting for tools like kind (and minikube before that) to run small test clusters for my local development work.

Kubernetes - k3s distribution

I’ve created a local cluster with K3S and installing Windmill could not be simpler with just one chart to configure, which already has sane defaults to get started. For this demo we will also configure workers to passthrough environment variables to our scripts so that they have access to the Kubernetes API server for later.

You should be familiar with Kubernetes and have set up a Kubernetes cluster. I recommend k3s.

K3s' go.mod[0] is insane.

[0] https://github.com/k3s-io/k3s/blob/master/go.mod