Removal of "PodLogs" from 10-configmaps.yaml appears to have no effect

[gamename]

Taken from a Slack conv:

tennis [11:24 AM]
@timothysc Hi. I’ve removed the “PodLogs” line from 10-configmaps.yaml and I still get this in the log:

I0928 16:03:14.961899       1 pods.go:46] Collecting Pod Logs...
I0928 16:03:14.961952       1 queries.go:215] Running ns query (account-authn)
I0928 16:03:16.644295       1 pods.go:46] Collecting Pod Logs...
I0928 16:06:50.866586       1 queries.go:215] Running ns query (account-cdvr)
I0928 16:06:53.399190       1 pods.go:46] Collecting Pod Logs...
I0928 16:06:53.854836       1 queries.go:215] Running ns query (account-sd)
I0928 16:06:56.212353       1 pods.go:46] Collecting Pod Logs...
I0928 16:06:57.027177       1 queries.go:215] Running ns query (authorize-channel)
I0928 16:06:59.603169       1 pods.go:46] Collecting Pod Logs...
I0928 16:07:01.215041       1 queries.go:215] Running ns query (catalog-content)
I0928 16:07:03.811513       1 pods.go:46] Collecting Pod Logs...
E0928 16:07:05.847814       1 discovery.go:41] error querying resources under namespace catalog-content: the server rejected our request for an unknown reason (get pods consumptionurl-1-1-7-3784334805-0s7q5)
I0928 16:07:05.847839       1 queries.go:215] Running ns query (catalog-feed)
I0928 16:07:15.455583       1 pods.go:46] Collecting Pod Logs...
I0928 16:07:17.814393       1 queries.go:215] Running ns query (catalog-gracenote)
I0928 16:07:20.403349       1 pods.go:46] Collecting Pod Logs...

Is that expected?

timothysc [11:26 AM]
Hmm let me check, that seems odd.

tennis [11:27 AM]
Thanks

timothysc [11:34 AM]
What version are you running?
0.8.0?

tennis [11:34 AM]
latest. Pulled right from github

timothysc [11:34 AM]
hmm, It's possible there is a bug on master. I don't have time to dbl check atm. If you file an issue we'll be sure to take a look, b/c we plan to rev next week.

tennis [11:35 AM]
will do. Np.

[timothysc]

Will look into this shortly and it's on the release backlog too.

[timothysc]

@gamename We updated the defaults to remove pod log collection, and I verified that it didn't try to collect when not specified. Let us know if you see this issue on master.