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
The `policy-controller` enforce images matching the defined list of `ClusterImagePolicy` for the labeled namespaces.
41
+
42
+
Note that, by default, the `policy-controller` offers a configurable behavior defining whether to allow, deny or warn whenever an image does not match a policy in a specific namespace. This behavior can be configured using the `config-policy-controller` ConfigMap created under the release namespace, and by adding an entry with the property `no-match-policy`and its value `warn|allow|deny`.
43
+
By default, any image that does not match a policy is rejected whenever `no-match-policy` is not configured in the ConfigMap.
44
+
45
+
As supported in previous versions, you could create your own key pair:
46
+
19
47
```shell
20
48
export COSIGN_PASSWORD=<my_cosign_password>
21
49
cosign generate-key-pair
22
50
```
23
51
24
-
The previous command generates two key files `cosign.key`and`cosign.pub`. Next, create a secret to validate the signatures:
52
+
This command generates two key files `cosign.key`and`cosign.pub`. Next, create a secret to validate the signatures:
25
53
26
54
```shell
27
-
kubectl create namespace cosign-system
28
-
29
55
kubectl create secret generic mysecret -n \
30
56
cosign-system --from-file=cosign.pub=./cosign.pub
31
57
```
32
58
33
-
Install `policy-controller` using Helm and setting the value of the secret key reference to `mysecret` that you created above:
59
+
**IMPORTANT:** The `cosign.secretKeyRef` flag is not supported anymore. Finally, you could reuse your secret `mysecret` by creating a `ClusterImagePolicy` that sets it as listed authorities, as shown below.
0 commit comments