-
Updated
Jun 14, 2022 - AGS Script
pod-security-policy
Here are 22 public repositories matching this topic...
-
Updated
Apr 13, 2021 - Shell
-
Updated
Jul 5, 2022 - TypeScript
Implement e2e tests
Right now the policy doesn't have e2e tests.
-
Updated
Jun 24, 2022 - TypeScript
Is your feature request related to a problem?
From a user in #kubewarden Slack channel on k8s:
When verifying cosigned images, I can create a deployment without getting an "actual feedback" on my cli, I only see the failed verify when fetching the events, or looking on the replicaset.
Example:
0s Warning FailedCreate replicaset/signtest-deployment-7b956c8
Create e2e tests
Implement real e2e tests for the policy
Create e2e tests
Implement real e2e tests for the policy
Create e2e tests
Implement real e2e tests for the policy
-
Updated
Jun 22, 2022 - Rust
-
Updated
Jul 31, 2021 - Python
Create e2e tests
Implement real e2e tests for the policy
-
Updated
Mar 22, 2022 - Go
-
Updated
Jul 10, 2021 - Shell
Add e2e tests
The policy is missing real e2e tests
-
Updated
Feb 14, 2022 - Go
-
Updated
Mar 20, 2021 - Python
Create e2e tests
Implement real e2e tests for the policy
Create e2e tests
Implement real e2e tests for the policy
Create e2e tests
Implement real e2e tests for the policy
-
Updated
Feb 14, 2022 - Go
Improve this page
Add a description, image, and links to the pod-security-policy topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the pod-security-policy topic, visit your repo's landing page and select "manage topics."

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

Is your feature request related to a problem?
Currently,
settings.RuleStrategy.ruleis a String. This makes it possible to createRuleStrategystructs such as:Which are incorrect, and we later in the code validating the settings struct so they are not accepted.
Solution you'd like
Simplify the code by refactori