pritunl-k8s-tf-do VS helmfile

I have a full example here of a working GHA pipeline that deploys terraform infrastructure. This deploys atlantis, which can then be used to deploy Pritunl VPN. Works almost perfectly except for the fact that helm yaml encoded sensitive values are revealed on terraform destroy, so I simply don't have anything sensitive encoded in yaml.

Hey now, I've already got a homelab that launches a k8s cluster and installs Pritunl VPN for coffee shop wifi. I do at least understand that tools need a valid use case before being applied, although admittedly installing it on k8s vs just using Nomad or something is more RDD than not for this one.

I'm looking for a company that is willing to judge me based off of past experience and previous projects I've already completed. So ideally no LeetCode, and no more take homes unless you want me to post them publicly. Ideally looking to come in at $160K+ for mid level or $200K+ for senior, depending on how much of a match there is between me and the position, and a sign-on bonus would be incredible. Hopefully I have enough of a reputation at this point where you've seen my posts and comments in /r/devops and already know what I'm capable of, but if not, I'm happy to chat about previous projects in-depth and go over what I've worked on. A code review as part of the interview process would be absolutely stellar. This is what I've been working on recently as well as my "homelab" if you re looking for some specifics. DM or chat with your work email for an official resume

Already done, but good call on learning how to create conditionals. I will look into it!

Playing around with grafana/loki/prometheus all via Terraform, GitHub Actions, and Atlantis in a public repo.

I set up a whole pipeline to install and configure Pritunl VPN on DigitalOcean and it only costs me like $60/month for a 3 node cluster.

https://github.com/autotune/pritunl-k8s-tf-do/blob/master/README.md is the repo. The README should answer any questions about how the pipeline works but the end result is a pritunl webgui listening on port 80 with an ingress route for https, a SERVICE load balancer that listens for VPN connections, and the ability to connect to said service load balancer over Pritunl VPN client. Note this is missing a few things, for one you can only have a replica set of 1 in the deployment. I need to figure out how to add HA with the "enterprise" edition at $70/month extra (still relatively cheap for what you get!). But for personal use it should suffice. Also, I tried using an ingress for the vpn itself but can't get it working, so stuck with SVC load balaner instead, which works fine. Any suggestions here would be appreciated!

All I know for sure is the one cert I was using with letsencrypt kept failing to renew. I just tried it with zerossl since the sign up page cert was finally renewed last night and people have generally been happy with them outside this little incident and seems to actually be working as expected. The helm release I am using is linked to via tf here and the ingress rules are here.

What we’re going to install into the newly created AKS cluster is located in the helm directory. The descriptive Helmfile approach enables us to define applications and their settings in the helmfile.yaml file.

Is there any alternative to https://github.com/roboll/helmfile you are currently using in your company.

Interesting, I have approached this problem using Helmfile (https://github.com/roboll/helmfile) to define a “platform release package.”

To make managing the Helm deployments a little easier I used helmfile (https://github.com/roboll/helmfile).

But in general it's always easier to keep things quite separated. Meaning in separate helm releases. If you want to be able to manage things "together" at will, then you can use helmfile ( https://github.com/roboll/helmfile )

I agree; helm is too declarative.

Whenever I can, I use helmfile[0] for storing variables for helm since it does add a declarative layer on top of helm.

0 - https://github.com/roboll/helmfile

I went through the Helmfile repo Readme to figure out the difference between helmfile sync and helmfile apply. It seems like unlike the apply command, the sync command doesn't do a diff and helm upgrades the hell out of all releases 😃. But from the word sync, you'd expect the command to apply those releases that have been changed. There is also mention of the potential application of helmfile apply to periodically syncing of releases. Why not use helmfile sync for this purpose? Overall, the difference didn't become crystal clear, and I though there could probably be more to it. So, I'm asking.

helmfile is something i’ve used in the past for this https://github.com/roboll/helmfile

I always felt like dependencies in helm are for very simple non-coupled packages. I many times use Helmfile (https://github.com/roboll/helmfile) to manage dependencies instead of banging my head with vanilla Helm.

Once you do that, learn to create dynamic helm charts that use go templating and conditionals: https://github.com/roboll/helmfile