WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@rogercoll
Copy link
Contributor

@rogercoll rogercoll commented Nov 28, 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?
  • ...

@mergify
Copy link
Contributor

mergify bot commented Nov 28, 2025

This pull request does not have a backport label. Could you fix it @rogercoll? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@rogercoll rogercoll marked this pull request as ready for review December 4, 2025 11:04
@rogercoll rogercoll requested review from a team as code owners December 4, 2025 11:04
@pierrehilbert pierrehilbert added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label Dec 4, 2025
@elasticmachine
Copy link
Contributor

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

osullivandonal
osullivandonal previously approved these changes Dec 4, 2025
Copy link
Contributor

@swiatekm swiatekm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do you need to bump Go dependencies in this PR?

@rogercoll
Copy link
Contributor Author

Why do you need to bump Go dependencies in this PR?

That was a side effect of updating Helm dependency to v4 as defined in go.mod (check-ci was failing if only helm was bumped).

swiatekm
swiatekm previously approved these changes Dec 10, 2025
@rogercoll
Copy link
Contributor Author

buildkite test this

@ChrsMark
Copy link
Member

Hmm, should this be fixed in other places too? I see #11596 reports something similar.

@rogercoll rogercoll dismissed stale reviews from swiatekm and osullivandonal via 583ba49 December 10, 2025 13:58
@rogercoll
Copy link
Contributor Author

Hmm, should this be fixed in other places too? I see #11596 reports something similar.

Definitely, not sure why this was not caught in previous CI runs. 583ba49

swiatekm
swiatekm previously approved these changes Dec 10, 2025
osullivandonal
osullivandonal previously approved these changes Dec 10, 2025
@rogercoll rogercoll dismissed stale reviews from osullivandonal and swiatekm via cf9f4b8 December 10, 2025 17:31
@rogercoll
Copy link
Contributor Author

@swiatekm and @osullivandonal I end up rolling back the go.mod changes as it hasn't updating Helm to v4 at all. The repository upgrade to v4 requires breaking changes to a few files I am not familiar with. Opened this issue to tackle it a separate PR: #11727

For now, this PR prevents having null YAML objects which are permitted in Helm v3 but not in Helm v4

@rogercoll
Copy link
Contributor Author

buildkite test this

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

History

cc @rogercoll

@rogercoll rogercoll merged commit 6a7cd38 into elastic:main Dec 12, 2025
21 checks passed
@rogercoll rogercoll added the backport-active-all Automated backport with mergify to all the active branches label Dec 12, 2025
@github-actions
Copy link
Contributor

@Mergifyio backport 8.19 9.1 9.2

@mergify
Copy link
Contributor

mergify bot commented Dec 12, 2025

backport 8.19 9.1 9.2

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Dec 12, 2025
* 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/logs-values.yaml
#	deploy/helm/edot-collector/kube-stack/managed_otlp/values.yaml
#	deploy/helm/edot-collector/kube-stack/values.yaml
mergify bot pushed a commit that referenced this pull request Dec 12, 2025
* 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 bot pushed a commit that referenced this pull request Dec 12, 2025
* 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)
rogercoll added a commit that referenced this pull request Dec 12, 2025
* 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)

Co-authored-by: Roger Coll <[email protected]>
rogercoll added a commit that referenced this pull request Dec 12, 2025
…1771)

* fix: spec invalid rendered values "null" (#11481)

* 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/logs-values.yaml
#	deploy/helm/edot-collector/kube-stack/managed_otlp/values.yaml
#	deploy/helm/edot-collector/kube-stack/values.yaml

* fix conflicts

---------

Co-authored-by: Roger Coll <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-active-all Automated backport with mergify to all the active branches 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.

6 participants