Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Dec 12, 2025

What does this PR do?

  • Modifies the kube-stack configurations to prevent "null" values in the Helm v4.
  • Bumps Helm v4 and its dependencies.

Why is it important?

Fixes the deployment with Helm 4, error message:

Error: Instrumentation.opentelemetry.io "elastic-instrumentation" is invalid: spec.env: Invalid value: "null": spec.env in body must be of type array: "null"
OpenTelemetryCollector.opentelemetry.io "opentelemetry-kube-stack-gateway" is invalid: [spec.config.service.pipelines.metrics/aggregated-otel-metrics.processors: Invalid value: "null": spec.config.service.pipelines.metrics/aggregated-otel-metrics.processors in body must be of type array: "null", <nil>: Invalid value: "null": some validation rules were not checked because the object was invalid; correct the existing errors to complete validation]

Checklist

  • I have read and understood the pull request guidelines of this project.
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool
  • I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...

This is an automatic backport of pull request #11481 done by [Mergify](https://mergify.com).

* fix: spec invalid rendered values "null"

* chore: add fragments

* update helm to v4

* fix: k8s_events empty config

* rollback go mod changes

* rollback licenses

(cherry picked from commit 6a7cd38)

# Conflicts:
#	deploy/helm/edot-collector/kube-stack/managed_otlp/values.yaml
#	deploy/helm/edot-collector/kube-stack/values.yaml
@mergify mergify bot requested a review from a team as a code owner December 12, 2025 09:44
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Dec 12, 2025
@mergify
Copy link
Contributor Author

mergify bot commented Dec 12, 2025

Cherry-pick of 6a7cd38 has failed:

On branch mergify/bp/9.1/pr-11481
Your branch is up to date with 'origin/9.1'.

You are currently cherry-picking commit 6a7cd38f5.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   changelog/fragments/1764348725-fix_templates_for_helm_4.yaml
	modified:   deploy/helm/edot-collector/kube-stack/managed_otlp/logs-values.yaml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   deploy/helm/edot-collector/kube-stack/managed_otlp/values.yaml
	both modified:   deploy/helm/edot-collector/kube-stack/values.yaml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@mergify mergify bot mentioned this pull request Dec 12, 2025
8 tasks
@github-actions github-actions bot added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label Dec 12, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

@rogercoll rogercoll enabled auto-merge (squash) December 12, 2025 15:28
@elasticmachine
Copy link
Contributor

⏳ Build in-progress, with failures

Failed CI Steps

History

cc @rogercoll

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport conflicts There is a conflict in the backported pull request Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants