Blog by Lup Peng about Virtualization, Containerization, Databases, IaaS, PaaS, DevOps, and everything else he’s learning about.
I found the official documentation a bit too generic / confusing, so decided to jot down how I set mine up. Gitea will be running directly on the host, while Atlantis as a podman container on the same host.
Before I learnt this approach, one of the challenges I faced when building a reusuable VM image is to define the mountpoints ahead of time. I found this breakthrough when I read more about systemd's mount unit configuration, which specifically states that under the [Mount] section:
GNU Core Utilities's du is one of the most widely used Linux utility to estimate how much disk space a particular set of files are using on a filesystem. I chanced across duc (du-cached) and wanted to give it a try to evaluate its effectiveness against a large filesystem. But I kept wondering how du and duc worked, and which one was really faster when calculating disk utilization.
If both types of receivers are contained within the configuration file, it will result in duplicated processing of scraped signals by multiple collectors. This may result in unintended outcomes, such as excessively scaling out a downstream system, or sinking twice as many logs into a third party storage service.
I took and passed the Certified Argo Project Associate certification exam offered by Linux Foundation. I believe that my knowledge in Kubernetes allowed me to pick this up quickly, and focus solely on the Argo specific nuances. These are the resources I used:
The Argo project is currently made up of four different tools - Workflows, CD, Rollouts, and Events. While there are UI dashboards available for each tool, the way they are meant to be used or made available are not quite standardized. In the world of Platform Engineering, I believe that there is value in installing all four tools in a single Kubernetes cluster. This Kubernetes cluster can then be…
This certification focuses on the skills required to create and implement security solutions in the AWS cloud. As with the more advanced levels, it also looks at how to implement these solutions at scale - both multi-region and multi-account. I spent 4 months preparing for this certification, and these are the resources I used.
When you need to define the startup sequence of your Systemd units, you have a few options under the [Unit] section that define the ordering and/or dependency. Ordering is the sequence of which the Systemd units start, while dependency is the relationship between two (or more) units.
TL;DR - When CloudWatch Logs receives the logs, the logs take a few minutes before it's available to query via Log Insights. I found that waiting for 3 minutes before querying works reliably. If you want real time event processing, use a service like AWS Kinesis.
This post explains how to enable huge pages for GitLab Runner jobs using the Kubernetes exectuor, deployed on an AWS Elastic Kubernetes Service (EKS) cluster using Karpenter.