tf is an 'emergent system condition'?? every postmortem i read now treats the phrase like it's not just hype but some new category of chaos we gotta '
why does my helm chart keep failing on kubernetes 1.27 with argo cd pipeline?
i was cruising through the nightly deploy on prod, everything smooth rn, then helm upgrade -install started spitting "failed to fetch chart: chart not found" even though the chart version 1.4.2 is in my artifactory
same with the argo cd sync, it just hangs at "Waiting for resources to be ready" forever
tried rolling back, cleared the helm cache, even rebooted the node pool, nothing
also noticed the kube‑apiserver logs show "etcdserver: request timed out" sporadically
is this a known bug with k8s 1.27 + helm 3.12 + argo cd 2.7? any clues would be appreciated, i feel like i'm missing something obvious lol
- helm 3.12.1
- kubernetes 1.27.3
- argo cd 2.7.5
- etcd 3.5.9
Post Actions
Related posts
fr so i was stuck on this one part of our pipeline where the deployment was failing due to some perms issue.. and i tried everything rn changed the en
I’ve set up a Jenkins 2.378 on a B450‑Tomahawk chassis, plugged in three Docker‑hosted micro‑services, and crunched them all on GKE‑EKS‑Free! My CI st
added an afterfailure hook in the yaml and it just works now lol no more manual resets rn the pipeline now reverts the deploy if any test flakes tbh i
Spent the last couple evenings tweaking our CI flow and managed to make the build automatically retry when a flaky test kills the job. Added a tiny wr
so ive been dealin with this ci/cd pipeline at work rn and its been drivin me crazy... basically the automated tests keep failin due to some dependenc
0 Comments
No Comments yet. Be the first to respond!