Closed momilo closed 8 months ago
Hi @momilo,
Thanks for reporting this issue. We've prepared and validated (with the Topic.pubsub
managed resource) a fix for the logging issue reported here. However, I'm not sure of the memory leak issue.
Once the logging fix is available, could you please recheck if the memory leak issue still exists and maybe open a new bug with more details on the memory issue? Thank you very much.
Thank you very much, that is very helpful and it did indeed help us resolve the issue with logging. Alas, the memory leak issue persists - I've allowed myself to open a separate issue :-(.
Is there an existing issue for this?
Affected Resource(s)
xpkg.upbound.io/upbound/provider-gcp-pubsub
Resource MRs required to reproduce the bug
k describe provider provider-gcp-pubsub
k get pod provider-gcp-pubsub-4f8a71eab319-85688d99c-t5pwq -o=yaml -n=crossplane-system
Steps to Reproduce
What happened?
Observed:
--debug
flag or any other similar configuration[controller-runtime] log.SetLogger(...) was never called; logs will not be displayed.
does not appearExample logs:
The logs seem to be originally coming from
terraform-provider-google
, which I am guessing the crossplane provider is using underneath.There is no
--debug
orTF_ENV
set anywhere. I do not have anyControllerConfigs
.DeploymentRuntimeConfig
does not include anything relevant. In fact, I attempted addingTF_ENV=ERROR
orTF_ENV=OFF
to turn them off, but with no success.The bug was successfully replicated by a kind soul from Crossplane Slack's channel (see this thread)
Relevant Error Output Snippet
No response
Crossplane Version
1.15
Provider Version
1.0.0
Kubernetes Version
1.28
Kubernetes Distribution
GKE
Additional Info
No response