You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 16, 2023. It is now read-only.
Describe the bug: When upgrading Metricbeat while using custom metricbeatConfig value for metricbeat.yml and kube-state-metrics-metricbeat.yml, Metricbeat deployment doesn't start.
I am getting same issue for metricbeat 7.10.2 chart version. Repo - https://helm.elastic.co
Error: Exiting: missing field accessing 'metricbeat.modules.0.hosts.0' (source:'metricbeat.yml')
While installing using helm (version 3) in k8 cluster, Can anyone know solution for this?
I am getting same issue for metricbeat 7.10.2 chart version. Repo - https://helm.elastic.co
Error: Exiting: missing field accessing 'metricbeat.modules.0.hosts.0' (source:'metricbeat.yml')
While installing using helm (version 3) in k8 cluster, Can anyone know solution for this
I got it missing env variables -
-name: NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
Chart version: 7.7.0
Kubernetes version: 1.16.6
Kubernetes provider: Docker for Mac
Helm Version: 2.16.7
helm get release
outputOutput of helm get release
Describe the bug: When upgrading Metricbeat while using custom
metricbeatConfig
value formetricbeat.yml
andkube-state-metrics-metricbeat.yml
, Metricbeat deployment doesn't start.Steps to reproduce:
values.yaml
:helm install --name metricbeat elastic/metricbeat --version 7.6.2 --values values.yaml
helm upgrade metricbeat metricbeat --force --values values.yaml
Expected behavior: Upgrade is successful
Provide logs and/or server output (if relevant):
Any additional context:
The text was updated successfully, but these errors were encountered: