Add Karpenter & Keda metrics integration to OTEL Container Insights - #2223
Open
vaishnavi-30-beep wants to merge 15 commits into
Open
Add Karpenter & Keda metrics integration to OTEL Container Insights#2223vaishnavi-30-beep wants to merge 15 commits into
vaishnavi-30-beep wants to merge 15 commits into
Conversation
…anslation Revert temporary CI workflow changes pointing to fork.
Add the solutions field to the container_insights schema definition with a global enabled toggle and the karpenter.enabled sub-field. This validates configs that use the karpenter pipeline toggle.
… test Add KEDA metrics scraping as a new solution alongside Karpenter in the OTel Container Insights translator. The KEDA pipeline discovers the keda-operator pod via K8s service discovery and scrapes its Prometheus metrics endpoint, dropping generic Go runtime metrics that conflict with the apiserver pipeline. Changes: - Add keda.yaml pipeline template with receiver, processors, and pipeline wiring matching the helm chart config - Register keda solution in translator.go with solutionEnabled gate - Add keda schema entry in schema.json - Add golden test (input JSON + expected YAML) for KEDA pipeline - Fix Karpenter test: update JSON to use correct key paths (opentelemetry.cluster_name, role instead of mode) and regenerate expected YAML to match current translator output
sky333999
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds the Karpenter and KEDA metrics pipeline YAMLs to the agent's config translator, ensuring both scraping configurations are preserved during the transition from helm chart templates to agent-side config translation.
Companion to helm chart PR:
Description of changes:
translator/translate/otel/pipeline/opentelemetry/containerinsights/karpenter.yaml
cloudwatch.pipeline: karpenter) for pipeline attributiontranslator/translate/otel/pipeline/opentelemetry/containerinsights/keda.yaml
cloudwatch.pipeline: keda,scope.name: github.com/kedacore/keda) for pipeline attributiontranslator/translate/otel/pipeline/opentelemetry/containerinsights/translator.go
karpenter.yamlandkeda.yamlvia//go:embedroleClusterinNewTranslators(), gated bysolutionEnabled()translator/config/schema.json
karpenterandkedaobjects withenabledboolean undersolutionstranslator/tocwconfig/tocwconfig_test.go
TestContainerInsightsKarpenterConfiggolden testTestContainerInsightsKedaConfiggolden testtranslator/tocwconfig/sampleConfig/opentelemetry/
Testing
go build ./...passesTestContainerInsightsKarpenterConfigpassesTestContainerInsightsKedaConfigpassesBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.