Skip to content

feat(charts): document every value, expose runner apiTokenSource, fix metrics TLS name - #117

Closed
ryanmcafee wants to merge 1 commit into
mainfrom
feat/chart-service-account-annotations-and-docs
Closed

ryanmcafee wants to merge 1 commit into
mainfrom
feat/chart-service-account-annotations-and-docs

Conversation

@ryanmcafee

Copy link
Copy Markdown
Contributor

Audit of both charts against their templates and the operator CRDs. Based on origin/main; independent of #116.

Operator chart 1.3.4 -> 1.3.5. nameOverride, controllerManager.pod.labels and crd.keep were read by templates but absent from values.yaml; now declared. ServiceMonitor serverName named ...-controller-manager-metrics-service, a Service that does not exist, so TLS scraping failed with prometheus.enable + certmanager.enable; now matches the metrics Service and the cert-manager dnsNames. README parameters table covered 4 values; now all of them plus the manager env vars, ServiceAccount annotations (IRSA), Secrets Manager and metrics examples. New test fails if a template reads an undeclared value.

Runner chart 1.0.3 -> 1.1.0. CRD supports apiTokenSource (Kubernetes Secret or AWS Secrets Manager) but the chart only exposed the deprecated secretAPITokenName; now exposed with validation. Rendering with a placeholder accountID/apiToken now fails instead of registering a runner with a literal <api-token>. README rewritten: example used non-existent collectorID/authToken, upgrade/uninstall acted on the operator release; adds a parameters table, external-Secret and Secrets Manager examples, and states the runner has no ServiceAccount -- job pod identity is operator-chart config.

helm lint clean; 48 render assertions pass across three test scripts. #116 (integration ServiceAccount annotations) will need a rebase onto this for values.yaml/README.

https://jupiterone.atlassian.net/browse/TD-9103

… metrics TLS name

Operator chart (1.3.5): declare nameOverride, controllerManager.pod.labels
and crd.keep, which templates already read but values.yaml never listed;
fix the ServiceMonitor serverName, which pointed at a Service that does
not exist so TLS scraping failed whenever prometheus and cert-manager were
both enabled; document all values, the manager environment variables and
the ServiceAccount annotation, Secrets Manager and metrics setups in the
README; add a test that fails when a template reads an undeclared value.

Runner chart (1.1.0): expose apiTokenSource so the runner can read its API
token from AWS Secrets Manager or a named Kubernetes Secret, which the CRD
already supported; refuse to render with a placeholder accountID or
apiToken instead of registering a runner with a literal "<api-token>";
rewrite the README, whose example used values that do not exist and whose
upgrade and uninstall commands acted on the operator release, and state
that the runner has no ServiceAccount of its own so job pod identity is
configured on the operator chart; add render tests.

Co-Authored-By: Ryan McAfee - Bot <ryan.mcafee+bot@jupiterone.com>
@ryanmcafee
ryanmcafee requested a review from a team as a code owner September 16, 2026 21:39
@ryanmcafee ryanmcafee closed this Sep 16, 2026
@ryanmcafee
ryanmcafee deleted the feat/chart-service-account-annotations-and-docs branch September 16, 2026 21:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant