You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experiencing exactly the same issue described in #313 (which was fixed in #312):
I've configured credentials for a bucket in the GCS output section, the k8s cluster is generating logs and sending them to falco and then to falcosidekick.
The latter has the following in its logs GCPStorage - Upload to bucket OK, debug mode show the proper payload but nothing is created on the bucket.
Trying to output those same logs with a default loki config works flawlessly.
How to reproduce it
Configure the GCP Bucket output in sidekick.
Generate a debug event.
Observe GCPStorage - Upload to bucket OK
Observe no new objects or API calls in the target GCP bucket
Expected behaviour
Logs should be written in the target GCP bucket when falcosidekick says it uploaded successfully.
Screenshots
Environment
GKE, 9 nodes on Google container-OS. Falco and falcosidekick both installed with official helm chart with sidekick.enabled=true.
We're using argocd to manage helm.
Falco version:
helm chart is falco-4.2.2 so falco is 0.37.1 and falcosidekick is 2.28.0
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm experiencing exactly the same issue described in #313 (which was fixed in #312):
I've configured credentials for a bucket in the GCS output section, the k8s cluster is generating logs and sending them to falco and then to falcosidekick.
The latter has the following in its logs
GCPStorage - Upload to bucket OK
, debug mode show the proper payload but nothing is created on the bucket.Trying to output those same logs with a default loki config works flawlessly.
How to reproduce it
Expected behaviour
Logs should be written in the target GCP bucket when falcosidekick says it uploaded successfully.
Screenshots
Environment
GKE, 9 nodes on Google container-OS. Falco and falcosidekick both installed with official helm chart with sidekick.enabled=true.
We're using argocd to manage helm.
helm chart is falco-4.2.2 so falco is 0.37.1 and falcosidekick is 2.28.0
Additional context
The text was updated successfully, but these errors were encountered: