ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #kubernetes
Resource Reconciliation Failure In Argo CD, the Application Controller monitors the desired state in Git against the actual state in the Kubernetes cluster. When a synchronization operation fails, the application health status often transitions to Degraded . This status is a generic indicator that can be triggered by various underlying issues, such as failed
Argo CD v2.8 and Kubernetes 1.28 Compatibility: podSecurity API Support? The goal is to confirm whether Argo CD v2.8 can reliably deploy applications to a Kubernetes 1.28 cluster, specifically regarding the new podSecurity API introduced in 1.28. Argo CD’s documented compatibility matrix lists support for Kubernetes 1.22 through 1.27. A recent discussion in
Feature state: Beta since Kubernetes v1.11 Cloud infrastructure technologies let you run Kubernetes on public, private, and hybrid clouds. Kubernetes believes in automated, API-driven infrastructure without tight coupling between components. The cloud-controller-manager is a Kubernetes control plane
Argo CD monitors the health of Kubernetes resources by comparing the live state against the desired state. When a deployment fails—such as a pod entering a CrashLoopBackOff or ImagePullBackOff state—the Application controller updates the health status to Degraded . There is a known operational gap regarding the latency between the actual Kubernetes event and
During a Helm upgrade, the --reuse-values flag causes Helm to retain the previously released values and apply only the new --set or -f overrides. The chart's values.yaml is not re-evaluated unless explicitly included again. This behavior is documented but creates a practical gap when a chart maintainer changes default values between versions. If a chart upda
My project includes a Dockerfile to build an image. I've made modifications to that Dockerfile and want to see if it works. So i closed my program and listed all docker images in powershell using docker image ls -a . I deletetd all unused images using docker rmi -f $(docker images -a -q) and docker image prune -a . But my image keeps not getting deleted, but
Why do I need 3 different kind of probes in kubernetes: startupProbe readinessProbe livenessProbe There are some questions ( k8s - livenessProbe vs readinessProbe , Setting up a readiness, liveness or startup probe ) and articles about this topic. But this is not so clear: Why do I need 3 different kind of probes? What are the use cases? What are the best pr
When a Sema‑managed deployment fails, the Deployment Event Logging feature attaches the associated Kubernetes pod logs to the deployment event record. The documentation confirms that logs are emitted to a shared stream queryable by the Sema CLI and API, but it does not specify whether Sema automatically merges logs from multiple pods into a single event entr
I have deployment and a replica set in Kubernetes that are failing to create a pod. I've tried kubectl describe deployment deployment-name and kubectl describe replicaset replicaset-name And they both say Conditions: Type Status Reason ---- ------ ------ ReplicaFailure True FailedCreate Events: <none> All of the troubleshooting guides I've seen rely on
argocd
helm
docker
sema