In this blog post, we provide the necessary steps to setup a single-node standalone Consul server to be used as TF state backend.
In doing so, we aim to provide idempotent and reproducible codes using Tofu and Ansible, for the sake of disaster recovery as well as enabling team collaboration within version control system.
In this blog post you will learn how to authenticate and deploy your frontend code to Azure CDN, backed by Azure Blob Storage to deliver low-latency static website to your users.
The objective is to avoid hard-coded credentials and only employ OpenID Connect to establish trust relationship between the Identity Provider (GitHub) and the Service Provider (Azure).
External Secrets is the de-facto choice for secrets management in Kubernetes clusters. It simplifies the task of the administrator(s) of the cluster, ensuring only the secrets that are explicitly defined are present and accessible.
It comes with many great features but most important than all is its integration with major cloud providers.
In this blog post you will learn how to deploy it without hard-coded credentials and using only the power of OpenID Connect for trust relationship between services.
Promtail is (was) the lightweight log collector solution that sends the log over the HTTP to the remote backend. This remote backend is normally Loki but you can choose to send the logs to VictoriaLogs as well.
In this blog post, you will see the newer alternative to Promtail, Grafana Alloy. You will see what it is, why it's a good idea to migrate, and the how-to guide to make the jump with least friction.
Preview environment is where you see a live state of your changes from your pull request before being merged into the default branch. It gives you a look'n feel of what it would be like if you merged your changes.
Kubernetes on the other hand, is what powers the production setups. But that's not all it can do for you. I have spun up preview environments in Kubernetes with different technologies in the past.
And in this blog post, I will show you how to achive this using FluxCD Operator.
Building and deploying static sites is rarely an issue these days. Most of the PaaS providers already have full support for your live and your preview environments and a clean integration with your favorite Git provider.
However, some organizations may choose to stick with big players like GCP for various reasons.
In this blog post, you will learn how to build your frontend and deploy your static files to GCP bucket using GitHub Actions and serve it behind GCP CDN.
In this approach we will employ OpenID Connect to authenticate GitHub Actions runner to GCP API to avoid passing hard-coded credentials (Actually, GCP calls this Federated Workload Identity but it is unsurprisingly based on OIDC).
If this sounds interesting to you, let's not keep you waiting any longer.
In this blog post, you will learn how to leverage GitHub Actions to deploy static files to the GitHub Pages of another repository.
This can be useful if you keep your source code in a private repository, but also, you may find additional reasons to need this setup.
Stick around till the end to find out how to do this with OpenTofu.
In this blog post I share my opinioated version of provisioning a Kubernetes cluster in the Google Cloud Platform (GCP) using nothing but Opentofu.
The principles discussed here are the ones I have learned while dealing with production setups at the same scale.
If you enjoy Kubernetes or want to learn more about GCP, this is for you.
Packer is a powerful tool to create immutable images, with support for various cloud providers.
In this blog post, I share how I built a NixOS 24 snapshot using Packer on Hetzner Cloud.
If you're a fan of NixOS or want to learn more about Packer, this post is for you.
Most of the modern software deployment these days benefit from containerization and Kubernetes as the de-facto orchestration platform.
However, occasionally, I find myself in need of some Ansible provisioning and configuration management.
In this blog post, I will share how to create Ansible dynamic inventory in a way that avoids the need to write hard-coded IP addresses of the target hosts.