Propose: Kubernetes Deployment about cloudprober HOT 6 CLOSED

Thanks for this @DazWilkin.

Here is logic for discovering port for the default server:

If port is not in the config, and environment variable CLOUDPROBER_PORT is not defined, cloudprober will use 9313 (DefaultServerPort).

What error do you get when you don't specify the environment variable CLOUDPROBER_PORT.

from cloudprober.

I looked at cloudprober.go but it wasn't immediately obvious to me why it doesn't work.

Curiously, the container works outside of Kubernetes.

If I exclude the environment variable from the deployment file on Kubernetes, it generates:

cloudprober.go:164] Error initializing cloudprober. Err: failed to parse default port from the env var: CLOUDPROBER_PORT=tcp://10.102.246.132:9313

If I include:

env:
- name: CLOUDPROBER_PORT
  value: "9313"

It works.

from cloudprober.

Apparently Kubernetes automatically sets the environment variable "_PORT"
https://kubernetes.io/docs/concepts/services-networking/service/#environment-variables

This is colliding with the Cloudprober's default port environment variable name, CLOUDPROBER_PORT.

CLOUDPROBER_SERVICE_PORT would have been more compatible with Kubernetes. I'll document it for now and possibly change the environment variable name later.

from cloudprober.

IDNKT!

I've confirmed this is the root-cause in my case.

I renamed the service in my deployment (cloudprober→xcloudprober) and removed the env for CLOUDPROBER_PORT and the deployment succeeded.

from cloudprober.

Filed #252 to modify CLOUDPROBER_PORT parsing to work with Kubernetes.

from cloudprober.

Closing this issue now.

In case someone adopts the ConfigMap proposal described by Daz at the top, I'd also recommend to look at #149 (comment) for how to rollout ConfigMap updates.

from cloudprober.