K8s and limits

On K8s, for every pod you can define how much memory and CPU the pod needs. To make things "simpler", K8s define two set of values: requests and limits, both for CPU and memory. After some trouble on GCP, I was forced to dig a bit in the subject.

---

 

Read More

I am always amused on how complex K8s/Docker Swarm are, and how easy “plain” docker is.

Read More

Context: Spring microservice application to be deployed on K8s via helm + boring Friday

In this scenario, you end up writing the SAME configuration string in a lot of places:

1. On at least 2 application.properties (main and test)
2. On the final, helm-generated application properties (or in the relevant environment variable if you use them in place (1))
3. On the default K8s values.yaml used by helm. Possibly on other yaml file too, all documented a bit to be kindly with the K8s SRE.
4. On the relevant Java code, as a @Value annotation to finally use that damn config.

These configuration are not particular exciting: they are all similar, some case can change but, really, ChatGPT could do it for you. If you have 4 parameters, you end up losing half an hour to do everything and test it. We can do better, for sure^TM
Read More

In the last projects, I get used to use K8s CronJob(s) to schedule tasks.

Read More

Sometimes you need to create a lot of CronJobs in k8s. In particular, in my last project I need to create a lot of stupid “web hooks” to fire complex job execution. K8s is well suited for this task because it take care of launching a single job instance, and relaunch them in case of error.

Read More