kyverno: reintroduce resource limits (!337) · Merge requests · repos / cloud / toolforge / Toolforge deploy · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption, please take a look at our documentation.

How to register an account on GitLab. To prevent spam, new accounts are locked until approved by an admin or the approver bot. You can also file an unlock request to expedite access.

Support: mw:GitLab, how to host a project on GitLab, #wikimedia-gitlab on libera.chat, #GitLab on Phabricator.

Arturo Borrero Gonzalez requested to merge arturo-258-kyverno-reintroduce into main Jun 17, 2024

Previous to this patch, we had disabled all resource limits for kyverno. We believe this was part of the reason we suffered a kubernetes-wide outage.

Introduce some resource limits, which are otherwise pretty permissive.

Bug: T367386 Signed-off-by: Arturo Borrero Gonzalez aborrero@wikimedia.org