mjnagel/k3d-irsa

A walkthrough for setting up IRSA on a local k3d cluster

k3d-irsa's Issues

Alternatives to aws cli commands

Currently the setup in this repo relies on a lot of aws cli command for setup/teardown. While this works for simple dev use cases it could result in lingering resources since nothing is "in code". We could switch the AWS commands to instead use opentofu / similar to manage those pieces as IaC.

This would be a decent rewrite to the docs, but hopefully make the setup more approachable with a simple tofu apply. We could still keep things simple and local for key setup, state, etc, but this would make the tutorial a bit easier to follow and less error prone.

Thank you very much

❤️

Switch deploy manifests to helm chart

Currently the deploy manifests under deploy/ are simple and work for the demo deploy, but could be wrapped in a helm chart. This would solve a couple issues:

• Configuration of the annotation key (this is called out in the docs)
• Timing of jobs (leverage helm hooks to orchestrate these)
• Configuration of the region (current setup does not mutate in the region if I recall correctly)

The current image used in this repo will also likely be out of date eventually, so abstracting this into a helm value would enable easier updates for end usage without an update in this repo.