Public container crashes looking for --config file about azure-resourcemanager-exporter

[theok-nice]

If you deploy the exporter in a k8s cluster, you have the option to create a configmap that contains a config file.
Make the configmap available in you pod and then use CONFIG: environment variable to point where the config file is mounted.

This way you can continue use the original container. You can also configure the exporter through the config file, as intended.

[jkroepke]

configure the rest of the app using environment variables

As I know, environment variables are not supported anymore to configure the collectors.

If you pass a blank config, all collectors should be disabled.

[sharninder]

Yes, that is exactly what I'm doing. My point was basically about the documentation not mentioning it vs what is actually published to docker hub.

[jkroepke]

The issue is that beta versions are published as "latest" tag. The lastest stable version still does not require a config

[sharninder]

Aah. Now I see it. So that is my problem. I think I'll just use the latest stable for now. Thanks @jkroepke

[mblaschke]

Still working on a final release which then also gets an updated README and a changelog.

reminder: please don't use latest :)

[mblaschke]

23.6.0 released which now needs the config file.