Finding which values key controls a rendered field in 21 public Helm charts — judging keys by marker rendering, narrowing candidates, why 18 of 209 fields were missed, comparing code with an LLM on five charts, and what a single render costs.
From an approval click to a merged pull request — rechecking file blobs and base before merging, the missing server route that left a card spinning, recording the merge first, separating the response from sync watching after a CloudFront 504, and replacing a stale AI answer with a code-written sentence.
From a chat request to an opened pull request — verifying GitHub App install callbacks, deciding between PR and kubectl per resource, steering the LLM with ModelRetry and a one-line history memo instead of prompts, code-chosen edits for plain YAML and Kustomize, and render comparison against an expected result.
Before a chat-driven kubectl change gets silently reverted — a measured selfHeal revert in about six seconds, detecting ArgoCD-managed resources from tracking-id and instance labels, warn-then-allow approval cards, the real scope of a cluster-admin connection role, and the read-only views built on Application resources.
What ArgoCD actually does in the Kukie dev cluster — the two repositories it reads, the GitHub App that lets it read them, the loop that turns a merge into cluster state, the controllers that take over after it, and the checks at the API server that decide what it may put in.
How a develop merge in each app repo becomes exactly one image in ECR — a role that can push to one repository only, a commit-SHA tag that never moves so the job checks before it builds, a build cache that silently never saved, and a digest a person still copies into the manifest by hand.
Standing up the EKS cluster on top of the comment-approved pipeline — a NAT instance that costs a quarter of the gateway, three applies to finish one plan, an input that leaks into the next plan, and ArgoCD installed once from outside with every other Application kept in Git.
How a three-person team made Terraform changes go through review and a PR comment — the deploy-config repo split off like a parcel box, plan and apply as two different badges, and one saved plan applied exactly once.
Secret은 암호화가 아니라 인코딩이다. Sealed Secrets·External Secrets·sops로 Git 노출을 막고, CSI·사이드카 주입으로 클러스터에 아무것도 남기지 않는 방법.
Git 에 적힌 쿠버네티스 객체를 클러스터에 맞춰 넣는 GitOps 도구. Application · AppProject 라는 객체 종류를 추가해 무엇을 어디에 넣을지 정한다.