Managed to get it working by passing in env vars from a secret now.
ArgoCD has a really handy web UI that allows you to quickly see what kind of resources get deployed.
Especially for learning k8s I found that much easier to visualize than raw kubectl outputs.
Passing in the secrets once via the global: section is very neat. Got it working now with a few of the other tips and stole your trick for my secret handling. Thank you :)
Did you also have to set all these env vars by hand?
I am wondering if it might have something to do with rendering Helm Charts under ArgoCD.
I’ll give it another try with your recommendations.
And should I get it working finally, I will obviously switch back to using Secrets.
I only removed them to reduce possible points of failure.
As for blueprints, that’s a task for future me xD
Since projects of the same language often use the same tooling this makes it easier to clean up the whole directory by running something like this:
for d in ./*/ ; do (cd "$d" && somecommand); done
somecommand could be cargo clean if you’re in the Rust directory for example.
Depends on the exact system but there will be a method to switch to a newer release channel without reinstalling. Rinse and repeat every x years.
Got it working thanks to your troubleshooting tips now. Also found a very neat way to handle secrets from another comment.
I tend to run a DB instance per service as that makes backup restoration much easier for me. An idle postgres sits at around 50MB which is a cost I’m willing to pay.
Thank you again for your help :)