Grant privileged permissions to Beats
editGrant privileged permissions to Beats
editDeploying Beats on Openshift may require some privileged permissions. This section describes how to create a ServiceAccount, add the ServiceAccount to the privileged
SCC, and use it to run Beats.
The following example assumes that Beats is deployed in the Namespace elastic
with the ServiceAccount heartbeat
. You can replace these values according to your environment.
If you used the examples from the recipes directory, the ServiceAccount may already exist.
-
Create a dedicated ServiceAccount:
oc create serviceaccount heartbeat -n elastic
-
Add the ServiceAccount to the required SCC:
oc adm policy add-scc-to-user privileged -z heartbeat -n elastic
-
Update the Beat manifest to use the new ServiceAccount, for example:
apiVersion: beat.k8s.elastic.co/v1beta1 kind: Beat metadata: name: heartbeat spec: type: heartbeat version: 8.15.2 elasticsearchRef: name: elasticsearch config: heartbeat.monitors: - type: tcp schedule: '@every 5s' hosts: ["elasticsearch-es-http.default.svc:9200"] - type: tcp schedule: '@every 5s' hosts: ["kibana-kb-http.default.svc:5601"] deployment: replicas: 1 podTemplate: spec: serviceAccountName: heartbeat securityContext: runAsUser: 0
If SELinux is enabled, the Beat Pod might fail with the following message:
Exiting: Failed to create Beat meta file: open /usr/share/heartbeat/data/meta.json.new: permission denied
To fix this error, apply the label svirt_sandbox_file_t
to the directory /var/lib/elastic/heartbeat/heartbeat-data/
on the Kubernetes node:
chcon -Rt svirt_sandbox_file_t /var/lib/elastic/heartbeat/heartbeat-data/
Repeat this step on all the hosts where the heartbeat Pod can be deployed.
Some Beats may require additional permissions. For example, Filebeat
needs additional privileges to read other container logs on the host. In this case, you can use the privileged
field in the security context of the container spec:
apiVersion: beat.k8s.elastic.co/v1beta1 kind: Beat metadata: name: filebeat spec: type: filebeat ... daemonSet: podTemplate: spec: serviceAccountName: filebeat automountServiceAccountToken: true ... containers: - name: filebeat securityContext: runAsUser: 0 privileged: true # This is required to access other containers logs volumeMounts: - name: varlibdockercontainers mountPath: /var/lib/docker/containers volumes: - name: varlibdockercontainers hostPath: path: /var/lib/docker/containers
Check the complete examples in the recipes directory.