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 have setup a self-hosted infisical instance on my kubernetes cluster. I deployed the app and also the secret manager.
I tried to update a secret value of a specific app of my infrastructure and it worked flawlessly. I tried with a second app and nothing happens. The kubernetes secret value is not updated and of course the app is not redeployed.
After searching in the infisical logs, I found something in the secrets operator.
It seems the secrets operator is only watching the first app I deployed with an infisical secret CRD. Even though the other secrets were created as expected, they are never updated when changes are made in infisical.
@ByFishh@0xmemorygrinder, I've been unable to reproduce this. Would either one of you be available for a chat? We have a community slack where you can find me as "Daniel (Infisical)".
Alternatively you can book a time directly in my calendar!
Describe the bug
I have setup a self-hosted infisical instance on my kubernetes cluster. I deployed the app and also the secret manager.
I tried to update a secret value of a specific app of my infrastructure and it worked flawlessly. I tried with a second app and nothing happens. The kubernetes secret value is not updated and of course the app is not redeployed.
After searching in the infisical logs, I found something in the secrets operator.
It seems the secrets operator is only watching the first app I deployed with an infisical secret CRD. Even though the other secrets were created as expected, they are never updated when changes are made in infisical.
To Reproduce
Expected behavior
Every infisical secret crd should be watched, not the first one
Screenshots
Always the same deployement is watched, even if I have a lot of others
Platform you are having the issue on:
on-premise k8s cluster, ubuntu 24 OS
The text was updated successfully, but these errors were encountered: