Skip to content

feat: adding new post aks stability #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
axeII wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: adding new post aks stability #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions content/posts/how-to-improve-stabity-low-cost-aks/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
---
title: How I helped company to improve stability of low-cost AKS clusters
draft: false
date: 2025-12-07
tags: [Kubernetes, AKS, Stability, DevOps]

# showHero: false
---

# Introduction
In my company we run our product on Azure Kubernetes Service (AKS) clusters. We use for non production environments spot machines for nodes. What that means is that those nodes can be evicted at any time when Azure needs the capacity back. But as trade-off for that we pay much less for those nodes. Sometimes even up to 80% less of original price.

After recent months of running our product on those low-cost AKS clusters, we started to experience stability issues. It was getting much worse and we had to solve this problem.

I was given task - improve the stability of the cluster but keep the cost low.

Sounds challenging, right?

Let's dive in.


## Chapter 1: Identifying the stability problem

## Chapter 2: Finding solution

## Chapter 3: Tains and tolerations

## Chapter 4: Applying the changes and monitoring results

## Conclusion