I have deployed gitea and drone with the official charts.
Every time the gitea pods get restarted i need to restart the drone server too, otherwise it is no longer able to authenticate against gitea.
What are i’m missing here?
I have deployed gitea and drone with the official charts.
Every time the gitea pods get restarted i need to restart the drone server too, otherwise it is no longer able to authenticate against gitea.
What are i’m missing here?
Hello viceice,
Kindly confirm if during the gitea pods restart do you see any changes in the client_id and client_secret keys which can break the authentication.
Regards
I can confirm that client_id
and client_secret
are not changed on gitea restart.
As a workaround i simply delete the current drone pod and let it recreate by deplyoment. No config changes are necessary.
I found the issue, oauth2.JWT_SECRET
needs to be a static value at gitea config.
So now i’t’s working as expected