We rolled back a change we made to our authentication system. Any image pushes or config changes to a deployment that occurred after our rollback caused the deployment to fix itself, which is why so many people found their 403s resolved themselves after some time.
Resolved
We rolled back a change we made to our authentication system. Any image pushes or config changes to a deployment that occurred after our rollback caused the deployment to fix itself, which is why so many people found their 403s resolved themselves after some time.
Investigating
We are continuing to investigate this issue.
Investigating
It seems to be only in AWS clusters for now. We have a workaround we can apply while we investigate.