CatOps
DevOps and other issues by Yurii Rochniak (@grem1in) - SRE @ Preply && Maksym Vlasov (@MaxymVlasov) - Engineer @ Star. Opinions on our own. We do not post ads including event announcements. Please, do not bother us with such requests!
Більше- Підписники
- Перегляди допису
- ER - коефіцієнт залучення
Триває завантаження даних...
Триває завантаження даних...
_This article is also available on Substack. This is a very basic example of using Helm Unittestas well as an example of the “test pyramid” discussed in the previous article. The code is available on GitHub. Structure We have two charts: fw-demo - a chart with our demo application monitiring - a library chart that applies some DataDog monitoring rules for the main chart. monitoring chart is a dependency.
This article is also available on Substack. Before answering this question, we should decide why to test Helm chart? and if you even need to bother with that. Following an example from this xkcd comic, the real answer is: it depends. So, I want to share with you my story of Helm chart testing. How and, more importantly, why it started, and how it played out in the end. On a side note, I did a talk on this topic at the DevOps FW Days conference.
A story of a fruitful collaboration between Site Reliability and Database Engineering teams
What was on CatOps in the last couple of weeks...
You Need Lazy People to Have Restless Features
The Qualys Threat Research Unit (TRU) has discovered a Remote Unauthenticated Code Execution (RCE) vulnerability in OpenSSH’s server (sshd) in glibc-based Linux systems. CVE assigned to this…
7 simple steps to tackle any feedback situation
Надсилайте безкоштовно та безпечно кошти
It’s more than rails!
На вашому тарифі доступна аналітика тільки для 5 каналів. Щоб отримати більше — оберіть інший тариф.