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
Hey! I'm trying to set up an instance with remote logging and I want to store the logs in gcs.
The docs (and some examples) suggest using the standard JSON with keys, however I want to use Workload Identity and an annotated SA, if it's possible.
The thing is - I'm a bit lost.
I'm installing with helm, so I set up remote logging:
Now, the chart creates like 7 serviceaccounts by default and I have no idea which one is used by pod responsible for writing logs. So, is it even possible? Is this example correct? Which SA should be annotated with the SA name to impersonate?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hey! I'm trying to set up an instance with remote logging and I want to store the logs in gcs.
The docs (and some examples) suggest using the standard JSON with keys, however I want to use Workload Identity and an annotated SA, if it's possible.
The thing is - I'm a bit lost.
I'm installing with helm, so I set up remote logging:
Then, the envvar with the connection:
And, finally the secret with connstring providing the project id:
Now, the chart creates like 7 serviceaccounts by default and I have no idea which one is used by pod responsible for writing logs. So, is it even possible? Is this example correct? Which SA should be annotated with the SA name to impersonate?
Beta Was this translation helpful? Give feedback.
All reactions