Teamcity Helm Chart
A teamcity helm chart sets up a build server and agents inside a Kubernetes cluster. You define storage, network rules, and service roles in one template before you deploy. Many engineering teams use this method to run build pipelines at scale. Still, teams often grant broad cluster roles so build agents can deploy new apps. Those wide permissions let any build script read secrets or change live workloads. How a teamcity helm chart works in Kubernetes Helm packages all the Kubernetes files ne
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
A teamcity helm chart sets up a build server and agents inside a Kubernetes cluster. You define storage, network rules, and service roles in one template before you deploy. Many engineering teams use this method to run build pipelines at scale. Still, teams often grant broad cluster roles so build agents can deploy new apps. Those wide permissions let any build script read secrets or change live workloads.
How a teamcity helm chart works in Kubernetes
Helm packages all the Kubernetes files needed to run a build system. The chart sets up the main server pod and links it to a database. It also attaches a persistent disk to store build logs, plugins, and artifacts. Network services route user traffic to the web UI and agent traffic to the server.
Build agents run as separate pods in the same cluster or another namespace. When a developer pushes code, the server wakes an agent pod to run the job. The chart binds a Kubernetes service account to both the server and the agents. This service account tells the cluster API what the build pods can create or read.
Teams adjust chart values to set CPU limits, memory caps, and replica counts. You also mount database passwords and API keys into the pods from cluster secrets. Once applied, Kubernetes keeps the server running and replaces failed agent pods on its own.
What native chart roles solve and what they miss
Native chart settings and Kubernetes roles control which pods start and where they run. Role bindings limit which namespaces a build agent can reach during a job. Secret mounts keep database keys out of plain text files in your git repo. These controls handle basic setup and help teams repeat deployments across test and live clusters.
Yet cluster roles only check identity when a pod starts or calls the API. They do not inspect the actual database queries or shell commands inside a build step. Once an agent holds a valid database key or cluster role, it has full trust. A bad script or a changed pipeline can drop tables or dump customer records.
Helm Chart Security: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Standard logs in the build tool only show console output from the job. They do not record a clean audit trail of every SQL query or Kubernetes command. Also, raw query results can print sensitive data like emails or card numbers into build logs. Teams need command-level checks and data masking to keep live systems safe during builds.
Securing database and cluster tasks during builds
To reduce risk, teams should separate build agent permissions from live database and cluster roles. Agents should not hold long-lived root keys in their pod memory. Every query or command from a build job or engineer should pass a strict check. Sensitive fields like phone numbers or national IDs should be rewritten in query results. This stops private data from leaking into build logs or test artifacts.
Check Kubernetes API requests and responses on the wire
Kubernetes RBAC decides who may call the API server. RBAC does not check response payloads or split listing Secret names from reading Secret values when a role grants get access. With hoop.dev, you run an open-source HTTP proxy, a sidecar for your Kubernetes API. The kubectl client changes only the server address it talks to while RBAC stays in place.
On each call, hoop.dev guardrails read the method, normalized path, and headers to refuse bad deletes or full Secret reads with a 403 error. On the way back, hoop.dev data masking walks JSON responses by key and masks matched values in Secrets, ConfigMaps, and pod logs. Every request and verdict is logged without storing bearer tokens. View the project on GitHub.
Frequently asked questions
How does the chart store build history and artifacts?
The chart requests a persistent volume claim from your Kubernetes storage class for the server. An external database stores build history and user profiles outside the pod.
Why do build agents need a Kubernetes service account?
Agents need a service account to start test pods, pull private images, or deploy apps. You should limit this account to a single namespace with minimal rights.
How can teams protect live databases from bad build scripts?
Remove static database passwords from agent pods and check every SQL statement in flight. You can also apply data masking so queries rewrite emails and card numbers in results.
Related guides
In this post