chore(deps): update helm release eck-operator to v3.5.0 - #41
Open
github-actions[bot] wants to merge 1 commit into
Open
chore(deps): update helm release eck-operator to v3.5.0#41github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
renovate/eck-operator-3.x
branch
from
June 22, 2026 19:16
dcabefc to
e23a174
Compare
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
renovate/eck-operator-3.x
branch
from
August 4, 2026 19:46
e23a174 to
a3bbe11
Compare
github-actions
Bot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.3.2->3.5.0Release Notes
elastic/cloud-on-k8s (eck-operator)
v3.5.0Compare Source
Elastic Cloud on Kubernetes 3.5.0
Quickstart guide
Release Highlights
Dynamic namespaces
ECK now supports label-selector-based namespace scoping as an alternative to the static list of managed namespaces. When
namespaceSelectoris configured, the operator evaluates a Kubernetes label selector against namespace labels at runtime: when a namespace gains matching labels it is on-boarded immediately and the operator begins managing its Elastic resources; when a namespace's labels no longer match, it is off-boarded and the operator stops reconciling its resources. Both transitions happen live — no operator restart is required. This makes it straightforward to grow or shrink the set of managed namespaces by relabeling them, without any operator configuration changes. Dynamic namespace handling is an Enterprise feature. For more details, refer to the dynamic namespace handling documentation. For more details, refer to the dynamic namespace handling documentationPause orchestration annotation for maintenance windows
ECK now supports a
eck.k8s.elastic.co/pause-orchestrationannotation that temporarily suspends spec-driven orchestration on any ECK-managed resource. This is useful during maintenance windows — such as draining Kubernetes nodes or applying infrastructure changes — where you want to prevent ECK from applying spec changes while keeping essential housekeeping running. Unlike the existingeck.k8s.elastic.co/managed: "false"annotation (which stops all reconciliation entirely and is now deprecated), pausing orchestration keeps certificate rotation, service reconciliation, user and secret management, and health monitoring active, avoiding cluster degradation during extended pauses. The annotation is supported on all ECK-managed resource types, and its value is validated by the webhook. When orchestration is paused, ECK sets anOrchestrationPausedcondition on the resource status; on resume, any pending spec changes are applied immediately. For more details, refer to the pause orchestration documentation.Mutual TLS expansion across all Stack components
All Stack components that connect to elasticsearch — APM Server, Beats, Enterprise Search, Elastic Maps Server, Logstash, Elastic Agent (standalone), and Fleet Server — now automatically receive ECK-managed client certificates and present them when connecting to elasticsearch. For fleet-managed agents, Fleet Server propagates the client certificate information to all connected agents automatically, with no additional configuration required. For more details, refer to the elasticsearch client certificate authentication documentation.
Beyond securing connections to elasticsearch, Fleet Server can also be configured to require client certificates from the Elastic Agents connecting to it. This is an Enterprise feature. For more details, refer to the Fleet Server client certificate authentication documentation.
AutoOps agent collector configuration
The
AutoOpsAgentPolicyresource now exposesspec.configandspec.configReffields for tuning the AutoOps agent's collector configuration directly from the CRD, without manually editing configuration files. This gives you control over which metricsets are collected and at what interval. For more details, refer to the AutoOps data collection documentation.Hot-reload of secure settings without pod restarts
For elasticsearch 9.5 and later, ECK now supports an opt-in file-based delivery mechanism for
spec.secureSettingsthat eliminates the rolling restart previously required on every secret update. Enable it by adding theeck.k8s.elastic.co/file-based-secure-settings: "true"annotation to your elasticsearch resource; ECK then writes secrets directly into the elasticsearch file-based settings path and elasticsearch reloads them in place. For more details, refer to the secure settings documentation.elasticsearch role definitions in StackConfigPolicy
The new
securityRolesfield inStackConfigPolicylets you define custom elasticsearch roles declaratively within a policy and apply them consistently across all targeted clusters. ECK merges the definitions into theroles.ymlfile mounted on each elasticsearch pod and elasticsearch hot-reloads them without a pod restart. For more details, refer to the StackConfigPolicy documentation.Dynamic substitution variables in StackConfigPolicy
The new
variablesFromfield inStackConfigPolicylets you load key-value pairs from ConfigMaps and Secrets as substitution variables, referenced as${VAR}or${VAR:-default}expressions in the policy'selasticsearchandkibanafields, so a single policy definition can be reused across environments with different values. ECK watches all referenced sources and reconciles automatically when they change. StackConfigPolicy documentation.Reduced operator memory footprint
ECK 3.5 ships two complementary improvements to reduce the operator's memory usage in large clusters. The controller-runtime cache is now automatically scoped to only watch core workload resources (Pods, StatefulSets, Deployments, DaemonSets, PodDisruptionBudgets) that carry the ECK type label, avoiding the cost of caching unrelated workloads running in the same cluster. An additional opt-in flag,
--restrict-watched-resources, further narrows the cache for Secrets, Services, and ConfigMaps to those explicitly labelled witheck.k8s.elastic.co/watched=true, which significantly reduces memory and API server load in clusters with large numbers of user-managed resources of those types.Features and enhancements
pause-orchestrationannotation support for elasticsearch #9330annotator.shscript for theeck.k8s.elastic.co/pause-orchestrationannotation #9354pause-orchestrationannotation support for Elastic Agent, and Beats (boilerplate) #9417pause-orchestrationannotation support for Elastic Agent, and Beats #9398pause-orchestrationannotation #9474pause-orchestrationannotation support for Logstash #9484pause-orchestrationannotation support for AutoOps #9477--restrict-watched-resourcesflag to narrow cache for Secrets, Services, and ConfigMaps #9359spec.config/spec.configRef#9507extraObjectsin Helm charts #9478common/v1alpha1tocommon/v1#9408Fixes
ca.crtovertls.crtfor elasticsearch TLS verification #9463set-default-security-contextoperator flag #9551FLEET_SERVER_SERVICE_TOKENin Secret instead of plaintext pod env var #9626Updated dependencies
v3.4.1Compare Source
Elastic Cloud on Kubernetes 3.4.1
Dependency updates
v3.4.0Compare Source
Elastic Cloud on Kubernetes 3.4.0
Release Highlights
Elasticsearch client certificate authentication support
ECK now supports configuring Elasticsearch to require client certificates for authentication. This allows you to enforce mutual TLS (mTLS) between clients and Elasticsearch, strengthening security by requiring both the client and server to present valid certificates. Currently, Elasticsearch and Kibana support this feature - Kibana can be configured to present client certificates when connecting to Elasticsearch. Support for the remaining components that connect to Elasticsearch (Beats, Elastic Agent, APM Server, Logstash, and so on) will follow in future releases. For more details, refer to the client certificate authentication documentation.
Rolling restarts of Elasticsearch clusters
ECK now supports triggering rolling restarts of Elasticsearch clusters through a new annotation-based mechanism. This enables operators to gracefully restart all nodes in a cluster without manual intervention, useful for troubleshooting. The rolling restart documentation provides more details.
Simplified zone awareness configuration
ECK simplifies the configuration of zone awareness for Elasticsearch clusters, reducing the amount of boilerplate configuration needed to set up topology-aware allocation. For more details, refer to the zone awareness documentation.
ECK container image signing
ECK container images are now signed using Sigstore cosign. This allows users to verify the authenticity and integrity of ECK operator images before deployment, strengthening the supply chain security of their Kubernetes clusters.
Automatic password-protected keystore for Elasticsearch in FIPS mode
ECK now automatically manages a password-protected keystore for Elasticsearch when FIPS mode is enabled. When
xpack.security.fips_mode.enabledis set totruein the Elasticsearch configuration, the operator generates, stores, and configures a password-protected keystore — eliminating the need for manualpodTemplateoverrides. This feature activates for Elasticsearch 9.4.0+ and respects any existing user-provided keystore password configuration. For more details, refer to the Elasticsearch FIPS keystore password documentation.Features and enhancements
extraObjectssupport to ECK Helm charts #9069kubeAPIServerPortconfiguration option to Helm chart #8980seccompProfiletoRuntimeDefault#9012runAsNonRoottrue for recent versions of EPR #8974Fixes
require_started_replicapredicate #9188TrafficDistribution#8994UpdateReconciledwith Deployment reconciler #9256 (issue: #9246)Documentation improvements
PodTopologyLabelsAdmissionin Elasticsearch sample #9035Dependency updates
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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.