Skip to content

Conversation

@barkbay
Copy link
Contributor

@barkbay barkbay commented Jun 19, 2025

As reported in #8618 deploy/eck-stack/examples/logstash/basic-eck.yaml is currently broken.

This PR fixes the issue and also moves from .spec which is deprecated as stated in

# ** Deprecation Notice **
# The previous versions of this Helm Chart simply used the `spec` field here
# and allowed the user to specify any fields below spec that were templated directly
# into the final Beats manifest. This is no longer the preferred way to specify these
# fields and each field that is supported underneath `spec` is now directly specified
# in this values file. Currently both patterns are supported for backwards compatibility
# but we plan to remove the `spec` field in the future.
# spec: {}

@prodsecmachine
Copy link
Collaborator

prodsecmachine commented Jun 19, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

Copy link
Collaborator

@pebrc pebrc left a comment

Choose a reason for hiding this comment

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

LGTM quick smoke test was successful

@barkbay barkbay merged commit bfaee0b into main Jun 27, 2025
8 checks passed
@barkbay barkbay deleted the fix-helm-logstash-basic-eck branch June 27, 2025 08:36
alexlebens pushed a commit to alexlebens/infrastructure that referenced this pull request Jul 30, 2025
This PR contains the following updates: | Package | Update | Change | |---|---|---| | [eck-operator](https://github.com/elastic/cloud-on-k8s) | minor | `3.0.0` -> `3.1.0` | --- ### Release Notes <details> <summary>elastic/cloud-on-k8s (eck-operator)</summary> ### [`v3.1.0`](https://github.com/elastic/cloud-on-k8s/releases/tag/v3.1.0) [Compare Source](elastic/cloud-on-k8s@v3.0.0...v3.1.0) ### Elastic Cloud on Kubernetes 3.1.0 - [Quickstart guide](https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s#eck-quickstart) ##### Release Highlights - It is now possible to propagate metadata from the parent custom resource to the child resources created by the operator. If you add labels or annotations on an Elasticsearch, Kibana, or Agent resource, for example, these can be automatically propagated to the Pods, Services, and other resources created by the operator. Refer to the [Propagate Labels and Annotations](https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md) page for examples and more details. - To reduce the attack surface and improve overall security UBI images are now based on the UBI micro base image. ##### Features and enhancements - UBI: Use micro image instead of minimal [#&#8203;8704](elastic/cloud-on-k8s#8704) - Propagate metadata to children [#&#8203;8673](elastic/cloud-on-k8s#8673) (issue: [#&#8203;2652](elastic/cloud-on-k8s#2652)) - Allow advanced configuration for fleet-managed Elastic Agents [#&#8203;8623](elastic/cloud-on-k8s#8623) (issue: [#&#8203;8619](elastic/cloud-on-k8s#8619)) ##### Fixes - Set owner on service account Secret, update it when application is recreated [#&#8203;8716](elastic/cloud-on-k8s#8716) - fix: Cannot disable TLS in Logstash [#&#8203;8706](elastic/cloud-on-k8s#8706) (issue: [#&#8203;8600](elastic/cloud-on-k8s#8600)) - Move from deprecated container input to filestream [#&#8203;8679](elastic/cloud-on-k8s#8679) (issue: [#&#8203;8667](elastic/cloud-on-k8s#8667)) - Add automated workaround for 9.0.0 maps issue [#&#8203;8665](elastic/cloud-on-k8s#8665) (issue: [#&#8203;8655](elastic/cloud-on-k8s#8655)) - Bump go.mod to v3 [#&#8203;8609](elastic/cloud-on-k8s#8609) - Helm: Add support for missing `remoteClusterServer` value [#&#8203;8612](elastic/cloud-on-k8s#8612) ##### Documentation improvements - \[Helm] Fix examples/logstash/basic-eck.yaml [#&#8203;8695](elastic/cloud-on-k8s#8695) ##### Miscellaneous - Update Go version to 1.24.5 [#&#8203;8745](elastic/cloud-on-k8s#8745) - chore(deps): update registry.access.redhat.com/ubi9/ubi-micro docker tag to v9.6-1750858477 [#&#8203;8711](elastic/cloud-on-k8s#8711) - fix(deps): update k8s to v0.33.2 [#&#8203;8699](elastic/cloud-on-k8s#8699) - fix(deps): update module cloud.google.com/go/storage to v1.52.0 [#&#8203;8629](elastic/cloud-on-k8s#8629) - fix(deps): update module github.com/go-git/go-git/v5 to v5.16.0 [#&#8203;8631](elastic/cloud-on-k8s#8631) - fix(deps): update module github.com/google/go-containerregistry to v0.20.6 [#&#8203;8672](elastic/cloud-on-k8s#8672) - fix(deps): update module github.com/magiconair/properties to v1.8.10 [#&#8203;8625](elastic/cloud-on-k8s#8625) - fix(deps): update module github.com/prometheus/common to v0.63.0 [#&#8203;8569](elastic/cloud-on-k8s#8569) - fix(deps): update module github.com/spf13/viper to v1.20.1 [#&#8203;8570](elastic/cloud-on-k8s#8570) - fix(deps): update module google.golang.org/api to v0.227.0 [#&#8203;8529](elastic/cloud-on-k8s#8529) - fix(deps): update module helm.sh/helm/v3 to 3.17.3 [#&#8203;8598](elastic/cloud-on-k8s#8598) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xLjMiLCJ1cGRhdGVkSW5WZXIiOiI0MS4xLjMiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbImNoYXJ0Il19--> Reviewed-on: https://gitea.alexlebens.dev/alexlebens/infrastructure/pulls/1057 Co-authored-by: Renovate Bot <renovate-bot@alexlebens.net> Co-committed-by: Renovate Bot <renovate-bot@alexlebens.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

4 participants