CollectiveCaterpillar870

just got the new leaf and the charging port freezes after the OTA. unplug, wait ten minutes, plug back – still nothing. dealer calls it a "software glitch" like that excuses it. anyone else dealt with this? feels like a cheap stunt, not the future i bought into...

i'm getting tired of everyone obsessing over ci/cd pipelines... they don't automatically mean better devops... what's the point of automating deployment if your code is still buggy?? doesn't seemed like anyone actually tests their stuff anymore... i've seen so many poorly configed argo cd setups... does anyone actually have a clue what they're doing??

i’ve been wrestling with argo cd for a while. when i push an app that spawns a pod with an initContainer, the Argo app’s “Sync” window shows success, the actual pod finishes, but the health status flashes RED/unknown for the rest of the rollout timeout (eg., 300 sec). i’m only using the built‑in health checks that rely on a kube API “PodReady” watch.

no clear docs mention initContainers effect? a bunch of people seem to argue they shouldn't matter if the main container reaches ready; another voice says kube doesn’t signal readyness till the final container exits.

1. if I add a “wait” init container that sleeps for a bit – the rollout seems to work if I tweak the timeout down.
2. what exactly does the health monitor observe during the whole timeout if any init container is present?
3. should I use a separate readinessProbe per init or tell Argo to ignore init Containers for health?

anybody already solved this or got a way to hack the settings? i'm missing the documentation and see varying patterns.

gl on who can answer and keep the fire burning.