[Paamicky]

Description of the issue

OTEL Container Insights supports now supports scrapping of KEDA and Karpenter cluster metrics in Helm Chart.
Customer should be able to configure and scrape those metrics on the CloudWatch Agent.

Description of changes

• Added agent-side KEDA and Karpenter cluster-scoped pipelines (keda.yaml, karpenter.yaml), gated on
  opentelemetry.collect.container_insights.solutions.{keda,karpenter}.
• Added solutions field in the cwagent schema.json for customers
• They forward into the shared metrics/opentelemetry pipeline and use mark_cluster, so they inherit the
  shared host/AZ/ec2.tag suppression, schema_url clear, awsattributelimit, and batching.
• Aligned set_workload to the canonical full definition so all copies are identical (avoids an order-dependent merge
  collision).
• Enabled solutions in the cluster test config and regenerated the golden.

License

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this
contribution, under the terms of your choice.

Tests

• go build ./... and go test ./translator/... pass; gofmt clean; golden regenerated.
• E2E on EKS (operator + JSON config, solutions enabled): cluster-scraper discovered the KEDA/Karpenter
  endpoints and added the scrape jobs; confirmed keda_scaler_active and karpenter_nodes_total in CloudWatch.

Requirements

1. Run make fmt and make fmt-sh
2. Run make lint

Integration Tests

To run integration tests against this PR, add the ready for testing label.

[github-actions]

Binary Size Report

linux/amd64

Binary	PR	vs main (87efdff)	vs v1.300072.0
amazon-cloudwatch-agent	194.8 MB	${\color{red}▲}$ +1.5 MB (+0.8%)	${\color{red}▲}$ +1.5 MB (+0.8%)
amazon-cloudwatch-agent-config-wizard	2.0 MB	+0 B	+0 B
config-downloader	2.0 MB	+0 B	+0 B
config-translator	2.0 MB	+0 B	+0 B
start-amazon-cloudwatch-agent	2.5 MB	+0 B	+0 B
workload-discovery	3.0 MB	+0 B	+0 B
Total	206.3 MB	${\color{red}▲}$ +1.5 MB (+0.7%)	${\color{red}▲}$ +1.5 MB (+0.7%)

linux/amd64 amazon-cloudwatch-agent (last 9 main commits + this PR)

 195 ┤                                        
     ┤                                    ███ 
     ┤                                    ███ 
     ┤                                    ███ 
     ┤                                    ███ 
     ┤                                    ███ 
     ┤                                    ███ 
     ┤                                    ███ 
 193 ┤▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄▄▄ ███ 
 MB  └────────────────────────────────────────
      589a727             v1.300072.0     PR

Notable changes:

• +1.5 MB at PR

linux/arm64

Binary	PR	vs main (87efdff)	vs v1.300072.0
amazon-cloudwatch-agent	178.5 MB	${\color{red}▲}$ +1.4 MB (+0.8%)	${\color{red}▲}$ +1.4 MB (+0.8%)
amazon-cloudwatch-agent-config-wizard	2.0 MB	+0 B	+0 B
config-downloader	2.0 MB	+0 B	+0 B
config-translator	2.0 MB	+0 B	+0 B
start-amazon-cloudwatch-agent	2.4 MB	+0 B	+0 B
workload-discovery	2.9 MB	+0 B	+0 B
Total	189.8 MB	${\color{red}▲}$ +1.4 MB (+0.8%)	${\color{red}▲}$ +1.4 MB (+0.8%)

windows/amd64

Binary	PR	vs main (87efdff)	vs v1.300072.0
amazon-cloudwatch-agent.exe	196.1 MB	${\color{red}▲}$ +34.3 KB (+0.0%)	${\color{red}▲}$ +34.3 KB (+0.0%)
amazon-cloudwatch-agent-config-wizard.exe	2.1 MB	+0 B	+0 B
config-downloader.exe	2.1 MB	+0 B	+0 B
config-translator.exe	2.1 MB	+0 B	+0 B
start-amazon-cloudwatch-agent.exe	2.3 MB	+0 B	+0 B
workload-discovery.exe	2.9 MB	+0 B	+0 B
Total	207.8 MB	${\color{red}▲}$ +34.3 KB (+0.0%)	${\color{red}▲}$ +34.3 KB (+0.0%)

Investigating size changes

Use go-size-analyzer to compare binaries:

GOEXPERIMENT=jsonv2 go install github.com/Zxilly/go-size-analyzer/cmd/gsa@latest
gsa diff --old <baseline-binary> --new <new-binary>

[jefchien]

nit: Description seems incomplete. I think we're trying to say that this takes precedence over the individual solution "enabled" toggles.

The merge-base changed after approval.