What happened
When using google.projects.filter to dynamically discover projects (e.g.
all child projects under an org/folder matching a label), the exporter only
evaluates that filter once, at startup. If a new child project is added
later (or an existing one is removed), the exporter keeps scraping the
original, stale project list — the only way to pick up the change is to
restart the pod.
This defeats the purpose of using a filter for dynamic discovery, especially
in Kubernetes, where pods run for long periods without restarting.
Expected behavior
Newly added (or removed) child projects matching google.projects.filter
should be picked up within a reasonable time, without requiring a restart.
I'm working on a fix for this and plan to submit a PR within the next couple of days.
What happened
When using
google.projects.filterto dynamically discover projects (e.g.all child projects under an org/folder matching a label), the exporter only
evaluates that filter once, at startup. If a new child project is added
later (or an existing one is removed), the exporter keeps scraping the
original, stale project list — the only way to pick up the change is to
restart the pod.
This defeats the purpose of using a filter for dynamic discovery, especially
in Kubernetes, where pods run for long periods without restarting.
Expected behavior
Newly added (or removed) child projects matching
google.projects.filtershould be picked up within a reasonable time, without requiring a restart.
I'm working on a fix for this and plan to submit a PR within the next couple of days.