Migrate to Tanka

[JacksonWrath]

Since I've already started deploying with Tanka, let's get a few more things migrated for some practice.

[JacksonWrath]

Migrated Tailscale. Definitely a learning curve.

I stumbled across a tutorial from the jsonnet-libs repo which explicitly calls out both the _config pattern and the usage of $ Loki is doing as bad form.

The better solution is to use functions it seems, so I'll probably rewrite what I have to do that before moving anything else.

Something I don't particularly like: the jsonnet vscode extension isn't amazingly rich. It recognizes the language nicely, has basic autocomplete, detects the Tanka lib/vendor locations, and does eval of a file, but it doesn't pull in any documentation for IntelliSense, and the autocomplete doesn't handle everything perfectly, e.g.:

• it stops working for functions; understandable when defining a function, but annoying when I'm trying to call a function and pass in existing fields
• it doesn't remember what a field/variable is rendered to, so it can't autocomplete something that's generated by a function

[JacksonWrath]

Outside of helm, everything that is reasonable to migrate is done. Things like manifests for custom resources that basically never change aren't worth rewriting (Calico config, for example). I'll move these to a separate folder to clean up the root.

[JacksonWrath]

Basically done. Decided to just use the k3s helm-controller for helm charts, and define the HelmChart resources myself.

Major thing remaining is MinIO:

• Operator was installed with a kubectl plugin, but there's Helm chart now. Need to migrate to that
• Cluster itself is defined with a custom resource; need to determine if it's worth having any of that in jsonnet or not