Enable the NVCA OTel collector by default for managed clusters
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 427
Description
Description
Enable the NVCA Kubernetes event OpenTelemetry collector by default for NGC-managed and Helm-managed cluster sources. Keep explicit enabled: false overrides supported so operators can opt out or roll back without changing chart versions.
The self-managed collector default remains disabled because self-hosted registries may not contain the optional collector image.
Definition of Done
- The operator-level
otelCollector.enabledchart default istrue. - The
helmManaged.otelCollector.enabledchart default istrue. - Explicit disable overrides still render as disabled.
- The canonical and vendored NVCA Operator charts remain synchronized.
- Chart schema and generated parameter documentation match the new defaults.
- Regression tests cover both chart copies and managed cluster paths.
By submitting this issue, I acknowledge that I am an assigned member of the NVCF development team and agree to follow the repository code of conduct and contributing guidelines.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the canonical and vendored NVCA Operator charts, then inspect the operator-level and helmManaged otelCollector.enabled defaults, chart schema, and generated parameter documentation. Run the existing regression tests for both chart copies and managed cluster paths first. Done means managed defaults are enabled, self-managed remains disabled, explicit false overrides work, and the chart copies and generated documentation stay synchronized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100