-
Notifications
You must be signed in to change notification settings - Fork 718
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
Refactor stack monitoring templating #8327
base: main
Are you sure you want to change the base?
Conversation
buildkite test this -f p=gke,t=Test.*StackMonitoring -m s=8.16.0,s=7.17.25,s=8.15.4 |
return stackmon.BeatSidecar{}, err | ||
} | ||
|
||
caVolume, err := stackmon.CAVolume(client, k8s.ExtractNamespacedName(&es), esv1.ESNamer, commonv1.KbMonitoringAssociationType /*???*/, es.Spec.HTTP.TLS.Enabled()) |
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.
I was just doing a first read of your PR and noticed the /*???*/
, I agree that KbMonitoringAssociationType
feels a bit odd here but did not dig enough to be sure.
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.
I wanted to investigate this myself too and forgot about it. It just has an effect on the name of the volume mount. Changing it would mean a restart for the cluster. But maybe we should do it nonetheless
buildkite test this -f p=gke,t=Test.*StackMonitoring -m s=8.17.0,s=7.17.25,s=8.15.4 |
Fixes #8314
This PR introduces the following changes:
Not addressed:
stackmon.Metricbeat|Filebeat
are called twice: once for generating the config secret and once to generate the side cars (duplicated work)