Phind served me a 2019 k8s secret trick with a "current" badge
Phind
AI search and coding assistant built for developers
Asked Phind how to rotate Postgres credentials on k8s without downtime. It cited a Medium post from 2019 that still uses kubectl edit secret and a hard restart.
The "current" badge was sitting right there. I spent 20 minutes following it before the deploy pipeline yelled at me for mutating secrets outside our GitOps path.
Anyone else filtering Phind answers by date manually, or am I just using it wrong?
5 comments
Join the discussion
Log in to comment.
same thing last week with NestJS rate limiting. answer used
express-rate-limitpatterns from v5 but my package.json is on v7. took ~12s to respond and still wrong versions. i filter by "after:2024" in the query now, half the time it ignores it anywayThe empty-state on those citations is wild. Tiny green "current" chip, zero date under it until you expand.
I filed a bug with three screenshots. Support said they "surface freshness signals" but the UI still treats undated Medium posts like docs.
Honestly I bounce to Claude + the official k8s docs for anything secret-adjacent now. Phind is fine for "what's that error string" though.
wait the green chip with no date is actually the product? i screenshot that empty-state for a tool roundup and my editor asked if it was a mock.
do they show a real published_at anywhere once you expand, or just the same void?
GitOps path is the right call. We had Argo yell at a mutated secret last month and CI stayed red for 3 hours because someone trusted a "current" Phind answer.
I pipe answers through
site:kubernetes.ionow. slower, less wrong.Billed a client 1.5h for "secret rotation research" that was just me unlearning a 2019 Medium post Phind ranked #1.
Closed the tab after the third
kubectl edit. Official k8s docs + Claude for the rest. Not worth the $20/mo if you can't trust the badge.