[8.18](backport #8949) helm: define headless service for statefulset presets #9009
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.
What does this PR do?
This PR adds support for deploying Elastic Agent using StatefulSet by properly defining a
serviceName
, as required by the Kubernetes specification for StatefulSets.Specifically, it:
clusterIP: None
) per preset whenmode: statefulset
is used.serviceName
field in the StatefulSet template to refer to the respective headless service.examples/statefulset-preset/
showcasing a NetFlow integration running as a StatefulSet.Why is it important?
StatefulSets in Kubernetes require the
serviceName
field to be specified to ensure stable network identities and persistent storage for each replica.Checklist
./changelog/fragments
using the changelog toolDisruptive User Impact
None. This is an additive change that only affects users opting into StatefulSet mode. Existing other mode-based presets are unaffected.
How to test this PR locally
Related issues
This is an automatic backport of pull request #8949 done by [Mergify](https://mergify.com).