Fully cross platform dotfile manager and dev environment bootstrapper written in Rust.

This repository embodies a structured approach to organizing Terraform code with Terragrunt, focusing on reusability, ease of management, and scalability across multiple environments and cloud providers. It's crafted to guide teams in building robust cloud infrastructure that adheres to best practices and principles.

OneUptime is a comprehensive solution for monitoring and managing your online services. Whether you need to check the availability of your website, dashboard, API, or any other online resource, OneUptime can alert your team when downtime happens and keep your customers informed with a status page. OneUptime also helps you handle incidents, set up on-call rotations, run tests, secure your services, analyze logs, track performance, and debug errors.

Learn how to effectively implement emptyDir memory for pods, with hands-on use cases for temporary data handling in Kubernetes.

Let’s talk about how at Hepsiburada, we efficiently manage hundreds of Kubernetes clusters that directly handle about 95% of our over 100 million monthly visitor traffic. We’ll delve into the complexities of managing multiple clusters and discuss the strategies we employ to tackle these challenges.

In this article I will write about the horizontal autoscaling in kubernetes. The intended audience is the software developers and devops/SRE engineers with at least some elementary background in kubernetes interested in learning about auto-scaling. When I was learning this topic, I didn’t find a single straightforward article that explains all the relveant concepts, so I took the challenge and rolled one myself.

This article may be useful for those who are aware of service meshes and probably trying to improve scalability and connectivity between applications in Kubernetes and other container orchestration systems, e.g., adding encryption and authorization for application connections.

Optimizing the use of limited AI training accelerators

Around 4 years ago, the ELMO Infrastructure team began the Kubernetes journey which involved building out multiple production clusters across multiple AWS regions, across multiple AWS accounts. Since then we have been able to migrate almost all our applications into Kubernetes from various different places such as Amazon ECS, AWS Opsworks and datacenters. One of the biggest challenges we faced, and i’m sure everyone has faced, is ensuring that we didn’t blow out the AWS bill with our Kubernetes costs. The idea is to have the cheapest but highest performing cluster possible… it’s important to not compromise performance for cost.

If you’re anything like me then using product features that you don’t fully understand always leaves you with a feeling of unease. Sure, using the feature might even be easy and cheerful at least as long as everything works as expected. We could even leave it at that. However, somewhere in between intrinsic engineering curiosity and the life experience that at some point in the future a deeper understanding will come in handy, we still have the desire to understand and debunk the magic.

When a pod is launched in Kubernetes, it starts with several policies. In this series, we will understand these policies, starting with imagePullPolicy.

Learn practical uses of terminationMessagePolicy in Kubernetes for efficient container debugging and error diagnostics.

Learn key aspects of Kubernetes Pod Policies, focusing on dnsPolicy, including practical insights into configurations like ClusterFirst, Default, and more.

Let’s install kubecost in 1 minute and get a fine grain report of your K8S expenses

ArgoCD is a fantastic tool to deploy applications via GitOps. You can defined all your kubernetes manifests in git and have ArgoCD watch them for changes. It’s a very popular product used to manage resources in kubernetes.

There are a couple syncing options that you can use, automated, self health or manually sync. I would love to see some kind of approval process in the future. Let’s build one.

Podinfo is a tiny web application made with Go that showcases best practices of running microservices in Kubernetes. Podinfo is used by CNCF projects like Flux and Flagger for end-to-end testing and workshops.