-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fluentd-Elasticsearch helm chart #50
Comments
fluentd-elasticsearch daemonset does not sign its request. |
@cosmo0920 what steps would one need to do to get THIS plugin to work with the helm chart (stable helm charts) located here: https://github.com/kiwigrid/helm-charts/tree/master/charts/fluentd-elasticsearch ? do you have suggestions on this ? |
Again, fluent-plugin-elasticsearch cannot handle AWS required sigv4 requests. |
@cosmo0920 its clear it cannot handle that.. thanks again for clarification. My question is how to resolve. As this is not exactly a rare use case. I'm asking for the next steps to get AWS support .. in that helm chart.. you're saying we need:
are there other steps to do this? I appreciate your response |
Someone who wants to create it. Perhaps, including you.
I have no idea. I'm not familiar with creating helm chart from scratch.
helm chart is maintained in the other repository. Someone who wants to add AWS ES service charts should send a PR to support it. |
Check this fluent/fluentd-kubernetes-daemonset#317 |
Check: fluentd-elasticsearch helm chart now support this with sidecar AWS signer proxy container. |
I stumbled across this post as I was troubleshooting an issue I was having with the fluentd-elasticsearch daemonset. I used Helm to install it onto my cluster. I updated the chart with a kube2iam annotation that assigns the pod an IAM role that allows it to post to my ES cluster. However, when I try to specify the role in the ES access policy I see the following in the fluentd logs:
When I exec into the container and curl the metadata endpoint, I can see that the pod is getting the role I've assigned to it, but I still can't seem to post to ES.
My access policy looks like this:
Do I need to add something to the configmap that the chart create in order for fluentd to use the role assigned to the pod?
The text was updated successfully, but these errors were encountered: