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
Apply is no problem, but here we should validate the patterns so we can't apply the tenant if the pattern is not compatible with go regexp (or just malformed).
Create Namespace (Will Timeout)
kubecdtl create ns oil-prod
...
Error from server (InternalError): Internal error occurred: failed calling webhook "[namespaces.capsule.clastix.io](http://namespaces.capsule.clastix.io/)": Post "[https://capsule-webhook-service.capsule-system.svc:443/namespaces?timeout=30s](https://capsule-webhook-service.capsule-system.svc/namespaces?timeout=30s)": EOF
Bug description
When the Regex Pattern for any forbidden annotation is not correct, the capsule controller panics on resource creation because of the faulty pattern.
How to reproduce
Steps to reproduce the behavior:
Apply is no problem, but here we should validate the patterns so we can't apply the tenant if the pattern is not compatible with go regexp (or just malformed).
Create Namespace (Will Timeout)
Controller Logs:
Expected behavior
For all the possible regex annotations:
capsule.clastix.io/forbidden-node-labels-regexp
capsule.clastix.io/forbidden-node-annotations-regexp
capsule.clastix.io/forbidden-namespace-labels-regexp
capsule.clastix.io/forbidden-namespace-annotations-regexp
Verify on apply that the given regexp patterns are valid. Otherwise fail on Tenant edit/create.
Logs
If applicable, please provide logs of
capsule
.In a standard stand-alone installation of Capsule,
you'd get this by running
kubectl -n capsule-system logs deploy/capsule-controller-manager
.Additional context
helm list -n capsule-system
)The text was updated successfully, but these errors were encountered: