You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Kubernetes InCluster setting is not working when kapacitor is mounted on a docker base image that can't resolve against /etc/resolve.conf search domains.
curl -sSk -H "Authorization: Bearer $KUBE_TOKEN" https://kubernetes/
curl: (6) Could not resolve host: kubernetes
The host for kubernetes is hardcoded here. This is dependent on DNS working. All containers are mounted with ENV values with Kubernetes API IP via KUBERNETES_SERVICE_HOST. We should use this not knowing which container supports proper DNS resolution. The client-go app uses ENV values for IP resolution as well.
This issue was found as part of the error that popped up during TICK script initialization for the k8sAutoscale node. It required the following url to be resolved to get at scaling state.
The Kubernetes InCluster setting is not working when kapacitor is mounted on a docker base image that can't resolve against
/etc/resolve.conf
search domains.The host for
kubernetes
is hardcoded here. This is dependent on DNS working. All containers are mounted with ENV values with Kubernetes API IP viaKUBERNETES_SERVICE_HOST
. We should use this not knowing which container supports proper DNS resolution. Theclient-go
app uses ENV values for IP resolution as well.This issue was found as part of the error that popped up during
TICK
script initialization for thek8sAutoscale
node. It required the following url to be resolved to get at scaling state.The text was updated successfully, but these errors were encountered: