Open waldner opened 2 years ago
This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days
The issue is still relevant.
This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days
The issue is still relevant.
This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days
The issue is still relevant.
any solution to this issue ?
Is there any solution available?
This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days
This is still an issue.
This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days
This is still an issue.
This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days
This is still an issue.
This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days
This is still an issue.
This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days
This is still an issue.
Running
fluentd-kubernetes-daemonset:v1.14.6-debian-elasticsearch7-1.0
inside a k8s cluster behind a proxy. The container has theHTTP_PROXY
/HTTPS_PROXY
(and their lowercase version) variables set, which are honored; however, the proxy should not be used to connect to the k8s API, so I setNO_PROXY
(andno_proxy
) tokubernetes,10.43.0.1,kubernetes.default.svc
, yet it looks like the API is not being accessed directly. Here are some errors from the log:On another cluster running without the proxy (everything else the same), no error is produced.