Read the service account's namespace when POD_NAMESPACE is missing

[jpkrohling]

Resolves #721
Signed-off-by: Juraci Paixão Kröhling juraci@kroehling.de

[jpkrohling]

@derXear, would you be able to give this one a try? Just change your operator.yaml to use the following image: quay.io/jpkroehling/jaeger-operator:721-Empty-POD_NAMESPACE

[objectiser]

Would be good to have some tests?

[jpkrohling]

In theory yes, but this one here is part of the command, which is hard to test :-/

[objectiser]

Ok :)

[jpkrohling]

I tested this manually myself, but would be good to have a confirmation from @derXear that this indeed fixes the reported problem.

[jpkrohling]

@qlikcoe, @toomai, looks like you might have been affected by this as well: would you be open to help testing this fix here? Just update your operator.yaml to use the following image: quay.io/jpkroehling/jaeger-operator:721-Empty-POD_NAMESPACE. Your operator.yaml should not contain the POD_NAMESPACE env var, as this fix is about testing how the operator behaves in the absence of this env var.

[toomai]

Hi @jpkrohling,

I was indeed affected by this issue. After setting the image to jaeger-operator:721-Empty-POD_NAMESPACE and removing the env variable from the deployment, everything runs fine. I see the message the POD_NAMESPACE env var isn't set, trying to determine it from the service account info and the operator deploys the Jaeger configuration.
You should note that I am not yet in a production environment but that shouldn't change anything

Thank you for you reactivity and your work

[jpkrohling]

Thanks for the confirmation! I'm merging this one.