With the release of Kubernetes 1.34, a new alpha feature is introduced that gives you more granular control over container restarts within a Pod. This feature, named Container Restart Policy and Rules, allows you to specify a restart policy for each container individually, overriding the Pod's global restart policy. In addition, it also allows you to conditionally restart individual containers based on their exit codes. This feature is available behind the alpha feature gate ContainerRestartRules.

This has been a long-requested feature. Let's dive into how it works and how you can use it.

Trace individual microservice costs by combining Kubernetes metrics, APM, and CUR for granular spending insights

В программе:
😶‍🌫 в чем ключевые отличия в эксплуатации Self-Hosted и Managed PostgreSQL

😶‍🌫 какие задачи полностью автоматизирует облачный провайдер, а что остается под вашим контролем даже в managed-сервисе

😶‍🌫 как быстро развернуть отказоустойчивый кластер Managed PostgreSQL в Cloud․ru и подключить к нему тестовое приложение

A simple and standalone WebDAV server.

Every millisecond matters when you're in the critical path of API authentication. After two years of fighting serverless limitations, we rebuilt our entire API stack and slashed the end-to-end latency.

Building a safer, more reliable path forward for Chef at Slack

In this article, we’re going to cover a few things that might’ve puzzled you if you’ve been running your applications, especially Go applications, in Kubernetes:

- How Kubernetes and the Linux kernel handle CPU stuff for containers
- What the Go runtime does with CPU, and whether you should bother setting GOMAXPROCS
- Which metrics are actually worth paying attention to

Maybe you’ve seen some of these metrics before while keeping an eye on your applications, but didn’t fully know what to make of them. This should help clear that up.

session persistence for terminal processes

On hosting images without the price tag.