Closed paltaa closed 3 months ago
The logic is comparing the others bit to ensure that it's 0: st.Mode().Perm()&otherFilter != 0000
If this is failing, the most likely explanation is something had gone wrong in setting the permission of the secret file.
Hey! It was my bad, the secret was expected to have the name of the file, not mount the entire secret as key value pairs, so my secret looks like:
apiVersion: v1
data:
secret-keys.yaml: | KEY VALUE PAIRS HERE
kind: Secret
metadata:
name: livekit-api-keys
namespace: livekit
type: Opaque
And now its working correctly, closing the issue but wont delete it in case someone else have this issue in the future.
Values for tha values.yaml
storeKeysInSecret:
enabled: true
existingSecret: "livekit-api-keys"
livekit:
port: 7880
log_level: debug
keys: {}
key_file: secret-keys.yaml
thanks for providing the solution! this example will def help folks.
Hey, ive set
storeKeysInSecret
to use a secret created withVaultSecretOperator
. The secret is being created correctly but livekit is in crashloopBackoff with error:key file others permissions must be set to 0
Now after checking th deployment template i can see that
defaultMode
has permission0600
But then after checking livekit code:
The function is checking for permissions
0000