-
Notifications
You must be signed in to change notification settings - Fork 204
fix: spec invalid rendered values "null" #11481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
This pull request does not have a backport label. Could you fix it @rogercoll? 🙏
|
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
swiatekm
left a comment
There was a problem hiding this 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?
That was a side effect of updating Helm dependency to v4 as defined in |
|
buildkite test this |
|
Hmm, should this be fixed in other places too? I see #11596 reports something similar. |
583ba49
cf9f4b8
b59e62d to
5714d92
Compare
|
@swiatekm and @osullivandonal I end up rolling back the For now, this PR prevents having |
|
buildkite test this |
💚 Build Succeeded
History
cc @rogercoll |
|
@Mergifyio backport 8.19 9.1 9.2 |
✅ Backports have been created
|
* 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: 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
* 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)
* 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]>
…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]>
What does this PR do?
Why is it important?
Fixes the deployment with Helm 4, error message:
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself