pritunl-k8s-tf-do VS helm

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.

helm

Explanation here: https://github.com/helm/helm/issues/12681#issuecomment-19593...

Looks like it's a bug in Helm, but actually isn't Helm's fault, the issue was introduced by Fedora Linux.

Helm (Get from here https://helm.sh/)

It’s also well understood that having a k8s cluster is not enough to make developers able to host their services - you need a devops team to work with them, using tools like delivery pipelines, Helm, kustomize, infra as code, service mesh, ingress, secrets management, key management - the list goes on! Developer Portals like Backstage, Port and Cortex have started to emerge to help manage some of this complexity.

Kubernetes orchestrates deployments and manages resources through yaml configuration files. While Kubernetes supports a wide array of resources and configurations, our aim in this tutorial is to maintain simplicity. For the sake of clarity and ease of understanding, we will use yaml configurations with hardcoded values. This method simplifies the learning process but isn’t ideal for production environments due to the need for manual updates with each new deployment. Although there are methods to streamline and automate this process, such as using Helm charts or bash scripts, we’ll not delve into those techniques to keep the tutorial manageable and avoid fatigue — you might be quite tired by that point!

Helm is a package manager that automates Kubernetes applications' creation, packaging, configuration, and deployment by combining your configuration files into a single reusable package. This eliminates the requirement to create the mentioned Kubernetes resources by ourselves since they have been implemented within the Helm chart. All we need to do is configure it as needed to match our requirements. From the public Helm chart repository, we can get the charts for common software packages like Consul, Jenkins SonarQube, etc. We can also create our own Helm charts for our custom applications so that we don’t need to repeat ourselves and simplify deployments.

We can search for charts https://helm.sh/ . Charts can be pulled(downloaded) and optionally unpacked(untar).

Generally I felt as if I was diving in the deepest of waters without the correct equipement and that was horrifying. Unfortunately to me, I had to dive even deeper before getting equiped with tools like ArgoCD, and k8slens. I had to start working with... HELM.

Within the architecture of Cyclops, a central component is the Helm engine. Helm is very popular within the Kubernetes community; chances are you have already run into it. The popularity of Helm plays to Cyclops's strength because of its straightforward integration.

helm: brew install helm