Kubernetes Pod replies "403 Forbiden" after a while about passwordpusher HOT 5 CLOSED

Hi @dhardy92 - it's most likely be due to the default throttling settings.

The default is to allow a max 100 requests per hour (for every client). This is to assure no single client can pummel the server with a million requests.

To fix, set the environment variable PWP__THROTTLING__HOURLY with a higher value or lower the frequency of the liveness probes.

On my side, I'll increase that default - it's too low for hourly. Filed #1107

Let me know if this resolves the issue for you. If it doesn't please send over the container logs and see if the site is still accessible from a browser.

from passwordpusher.

running for 1h now with PWP__THROTTLING__HOURLY=500 envar (3660/15s * 2 probes+slack) and no event about readinessProbe failing so far.
This seams to be the fix.
Thank you

from passwordpusher.

Hello @dhardy92, thanks for contributing to the Password Pusher community! We will respond as soon as possible.

from passwordpusher.

Note PWP__THROTTLING__DAILY=1000 is too low too.

from passwordpusher.

Doh - happy to hear that you are using it that much daily! I'll up the defaults. Your overrides will still be valid. Thanks for letting me know.

from passwordpusher.