Skip to content
Discussion options

You must be logged in to vote

I'm closing this because it was discovered during some followup investigation that the automountServiceAccountToken: false property was set on the serviceAccount for the improved-robot fleet.

This is the root cause of the error and changing that property to true has fixed our problems.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by jrkarnes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant