Will Beason
Will Beason
(Edited the above post for YAML formatting). @bj-1795 In the future please use [markdown formatting for YAML/code](https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#quoting-code) so it shows up properly.
I have replicated the issue. I believe there's something wrong with `input.review.operation` - it doesn't seem to be interpreted properly. Unfortunately I haven't found docs on how it is supposed...
On our end, there's no reason to reject a suite file just because it doesn't have a name. We don't use that field, so having validation for it doesn't make...
Added bug to gator beta milestone: https://github.com/open-policy-agent/gatekeeper/issues/1756 Defining the requirements for making Suites into fully following the KRM model is nontrivial, so rather than an immediate fix I'd rather make...
That makes a lot of sense - under normal circumstances there aren't appreciable gains for running Constraints in parallel. In this case, it makes a lot of sense since we...
This will be fixed with the ongoing compiler sharding work in frameworks. Since each ConstraintTemplate will get its own Rego compiler, one failing to compile means the others will still...
Since Helm doesn't allow templating CRDs (https://github.com/helm/helm/issues/7083), I don't know if there's anything we can do. @ritazh ?
Another (potentially easier) option than debugging this is to dynamically create Namespace names for our tests - use a test utility method that bases the Namespace name on the name...
I agree. It's only potentially bad if we end up creating thousands of Namespaces, but I don't know what the resource requirements for empty Namespaces are on the dummy API...