Menu

1 / 5

October: Kubernetes memory semantics and Collector edge fixes

DEV Community: kubernetes·Abhimanyu Bajaj·15 days ago
#EhwCiFqF
Reading 0:00
15s threshold

In October I had 10 PRs merged across four projects. The common thread was practical observability work: clearer Kubernetes memory conventions, Helm chart behavior that is easier to reason about, less flaky Collector tests, and maintainership for components that need active review.

Most of my week goes into one question: why does something that looks correctly configured not work in a real cluster? These PRs came from the same place.

TL;DR

Fixed flaky Kubernetes inventory cache-sync tests.

Removed a Java 11+ startup failure in a DataPower monitoring extension.

Let Operator chart users override only the Target Allocator repository.

Added Kubernetes memory utilization conventions.

Clarified Kubernetes working set descriptions.

Added Pod-level memory limit and request conventions.

Joined Flink Metrics Receiver code ownership.

Fixed broad Flink operator metric matching.

Documented Operator chart certificate drift with Argo CD.

Restored Azure Data Explorer Exporter active ownership and beta…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.