ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #kubernetes
The coordination gap Spring Boot 2.3 introduced graceful shutdown for every embedded server: with server.shutdown=graceful , Tomcat, Jetty, Undertow, and Netty stop accepting new requests while in-flight work runs until spring.lifecycle.timeout-per-shutdown-phase (default 30 seconds) expires. Migrating a small Spring Boot 3.2 service to this setting behind K
Based on the docs that I've read, there are 3 methods of patching: patches patchesStrategicMerge patchesJson6902. The difference between patchesStrategicMerge and patchesJson6902 is obvious. patchesStrategicMerge requires a duplicate structure of the kubernetes resource to identify the base resource that is being patched followed by the modified portion of t
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
The kubectl command-line tool supports several different ways to create and manage Kubernetes objects . This document provides an overview of the different approaches. Read the Kubectl book for details of managing objects by Kubectl. Management techniques Warning: A Kubernetes object should be manag
Feature state: Stable since Kubernetes v1.24 When you run a Pod on a Node, the Pod itself takes an amount of system resources. These resources are additional to the resources needed to run the container(s) inside the Pod. In Kubernetes, Pod Overhead is a way to account for the resources consumed by
Compare suitability, operational responsibilities and limits before choosing this technology for a project. Which trade-offs should guide the decision?
Helm v3 persists each release revision as a separate object in the configured storage backend, typically a Kubernetes Secret in the release namespace, and retains that history indefinitely by default with no built-in maximum revision enforcement. The helm uninstall command preserves revision history unless --no-keep-history is specified, yet the client does
Wanted your guidance on an issue while executing a Kubernetes YAML file. My kubectl version is as follows: Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.0", GitCommit:"af46c47ce925f4c4ad5cc8d1fca46c7b77d13b38", GitTreeState:"clean", BuildDate:"2020-12-08T17:59:43Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"windows/amd64"} Server
Helm leverages the Sprig library to provide date manipulation functions within chart templates. Because these templates are rendered on the local client or CI/CD runner before being sent to the Kubernetes API, the resulting manifests are static and reflect the environment of the execution machine. A challenge arises when maintaining charts across diverse env
spring
helm