I would like to have complete control of the config, so creating the filebeat helm chart through rancher api is not what i want even if this solves my automation “problem”. I know that the helm chart for filebeat correctly creates a service account to access the kubernetes api, my manual setup don’t do this and therefor i get an error.
I’m trying to install filebeat without using rancher app (helm).
Se below for workload yaml and container error related to my problem.
