Allow Beats stack monitoring w/o elasticseachRef #8273
Merged
Conversation
This file contains 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
|
buildkite test this -f p=gke,t=Test.*StackMonitoring,s=8.15.5 |
barkbay
approved these changes
Nov 29, 2024
pebrc
added a commit
to pebrc/cloud-on-k8s
that referenced
this pull request
Nov 29, 2024
Fix an issue where the ECK stack monitoring integration would abort reconciliation when there is no elasticsearchRef defined. This removes the cluster_uuid property from the Metricbeat configuration in such cases. (cherry picked from commit af5a6c1)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
pebrc
added a commit
that referenced
this pull request
Nov 29, 2024
Fix an issue where the ECK stack monitoring integration would abort reconciliation when there is no elasticsearchRef defined. This removes the cluster_uuid property from the Metricbeat configuration in such cases. (cherry picked from commit af5a6c1)
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.
Fixes #8194
There are cases where we cannot work out the associated Elasticsearch cluster (see the linked issue).
This:
monitoring.cluster_uuidpropertyBased on my testing this should be fine. Beats will show up as "standalone cluster (!)" in the stack monitoring UI.
