Skip to content
This repository has been archived by the owner on Feb 5, 2021. It is now read-only.

Feature request: Allow the container to use the credentials to talk to the Kubernetes API #35

Closed
anhnk opened this issue Aug 4, 2017 · 2 comments

Comments

@anhnk
Copy link

anhnk commented Aug 4, 2017

Howdy from down-under,

@lucaswilric and I are working on using this fluentd-kubernetes-sumologic container to forward our application logs to Sumologic. The problem we are having at the moment is the container is not authorised to talk to the Kubernetes API. Here is the log from one of the fluentd pods:

2017-08-03 01:49:19 +0000 [info]: reading config file path="/fluentd/etc/fluent.file.conf"
2017-08-03 01:49:19 +0000 [error]: config error file="/fluentd/etc/fluent.file.conf" error_class=Fluent::ConfigError error="Invalid Kubernetes API v1 endpoint [OUR_INTERNAL_DNS_CONTROLLER_NAME]:443/api: 401 Unauthorized"

We would like to request a feature to allow the container to use an SSL client certificate to talk to the Kubernetes API. Let me know if you need any other information.

Cheers,

@frankreno
Copy link
Contributor

@anhnk : thanks for the request. I am not sure when I will have time to work on this, but would gladly welcome a PR if you feel like taking this on.

frankreno added a commit that referenced this issue Oct 5, 2018
- [Add labels to k8s_metadata](#83)
- [Add source_host to conf.d/systemd/source.containers.conf](#84)
- minor refactoring and testing
- upgrade fluent-plugin-sumologic_output to latest (1.3.1)
- expose additional configuration options to provide more control over fluent-plugin-kubernetes_metadata_filter using default values (fixes #80 and #35)
@frankreno
Copy link
Contributor

fixed by b7fc18b

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants