Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Metricbeat daemonset not reloading on configmap changes #632

Closed
MaxRink opened this issue May 18, 2020 · 2 comments
Closed

Metricbeat daemonset not reloading on configmap changes #632

MaxRink opened this issue May 18, 2020 · 2 comments

Comments

@MaxRink
Copy link
Contributor

MaxRink commented May 18, 2020

Chart version:
7.7.0
Kubernetes version:
1.18.2
Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
CAPI
Helm Version:
3.1.2

Describe the bug:
If i change the metricbeat config and do an helm upgrade, the metricbeat configmap gets changed, but the metricbeat daemonset and deployment never restart to grab the new config.
Steps to reproduce:

  1. install metricbeat via helm
  2. change for example the output server
  3. the daemonset stays the same

Expected behavior:
The daeomset and deployment get restarted to use the new configmap
@MaxRink
Copy link
Contributor Author

MaxRink commented May 18, 2020 •
edited
Loading

seems like the config checksume doesnt get applied in all cases

@MaxRink MaxRink mentioned this issue May 19, 2020
Merged
4 tasks
@jmlrt
Copy link
Member

jmlrt commented May 27, 2020

Fixed by #634

@jmlrt jmlrt closed this as completed May 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MaxRink @jmlrt