Filebeat Helm chart 8.x requires `elasticsearch-master-certs`

We are using beats to ship our logs from k8s to the elastic cloud.

I would like to upgrade our beats helm chart version from 7.x to 8.x and it introduces a breaking change where i would have to create a secret with elasticsearch-master-certs.

Is that something i absolutely have todo , or i am misunderstanding something

If yes where do i get these certificates from ?

2 Likes

@Roman_Kournjaev did you ever figure this out? having the same issue here.

Hi Guys,

I registered to post this, basically you can override secretMounts by declaring it empty.
Here is an example with filebeat:

imageTag: 8.3.2
daemonset:
  # Extra environment variables for Filebeat container.
  secretMounts:
  extraEnvs:
  - name: ELASTICSEARCH_HOST
    value: elasticsearch
  - name: ELASTICSEARCH_PORT
    value: "9200"
  - name: NODE_NAME
    valueFrom:
      fieldRef:
        fieldPath: spec.nodeName
  - name: ELASTICSEARCH_USERNAME
    value: elastic
  - name: ELASTICSEARCH_PASSWORD
    value: password
  filebeatConfig:
    filebeat.yml: |
      filebeat.inputs:
      - type: container
        paths:
          - /var/log/containers/*.log
        processors:
        - add_kubernetes_metadata:
            host: ${NODE_NAME}
            matchers:
            - logs_path:
                logs_path: "/var/log/containers/"
      output.elasticsearch:
        host: "${NODE_NAME}"
        hosts: '["http://${ELASTICSEARCH_HOST}:${ELASTICSEARCH_PORT}"]'
        username: "${ELASTICSEARCH_USERNAME}"
        password: "${ELASTICSEARCH_PASSWORD}"
        protocol: http
        ssl.verification_mode: none
        ssl.certificate_authorities: []

3 Likes

@thefolenangel thanks for posting this! worked for me!

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.