[metricbeat] Missing pod security context
See original GitHub issueChart version: 7.12.X
The deployment
template is missing pod securityContext, the value variable podSecurityContext
is currently used by the container:
https://github.com/elastic/helm-charts/blob/v7.12.0/metricbeat/templates/deployment.yaml#L129
Like all other chart, we must be able to configure both pod and container securityContext.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Run Metricbeat on Kubernetes - Elastic
securityContext: runAsUser: 0 privileged: true. In the manifest file, edit the metricbeat-daemonset-modules ConfigMap, and specify the following settings ...
Read more >metricbeat 8.5.1 - elastic - Artifact Hub
Official Elastic helm chart for Metricbeat. ... securityContext, Configurable securityContext for Metricbeat DaemonSet pod execution environment ...
Read more >cannot get kubernetes resource "events" using metricbeat ...
Problem: All other metricbeat modules are working fine except for the "event" resource. I can see logs from status_pod, status_node etc but ...
Read more >elasticsearch stack monitoring on kubernetes(ECK) - Justin Lim
... metricbeat pods while the new method uses filebeat and metricbeat ... securityContext: runAsUser: 0 containers: - name: metricbeat env: ...
Read more >Step By Step Installation For Elasticsearch Operator on ...
securityContext : # privileged: true # command: ['sh', '-c', 'sysctl -w vm.max_map_count=262144'] ### # uncomment the line below if you are using a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just face it. IMO this is a bug because PodSecurityContext should be at Pod level, not at container level (as there is already a
deployment.securityContext
key available). If I receive the approval of the maintainers, I have no problem doing a PR to fix it.Also, this bug is present in old versions
This issue has been automatically closed because it has not had recent activity since being marked as stale.