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
* fix redirect end with slash /
Signed-off-by: Carlos Santana <csantana23@gmail.com>
* white background
Signed-off-by: Carlos Santana <csantana23@gmail.com>
* move previous announcement only home
Signed-off-by: Carlos Santana <csantana23@gmail.com>
Copy file name to clipboardExpand all lines: docs/reference/tools/container-image-security-enforcement.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,14 +48,14 @@ This will create a public and private key combination that can be used to sign a
48
48
#### Saving the private key in a vault
49
49
50
50
51
-
Once your key has been generated, the private key should be stored within a credentials vault, such as [Key Protect](../tools/key-protect.html) or [IBM HyperProtect Crypto Services](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-overview).
51
+
Once your key has been generated, the private key should be stored within a credentials vault, such as [Key Protect](key-protect.md) or [IBM HyperProtect Crypto Services](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-overview).
52
52
53
-
The private key should be placed in the vault as a base64 encoded string, which can be accessed by your [Tekton](../tools/tekton.html) pipeline during the image building task.
53
+
The private key should be placed in the vault as a base64 encoded string, which can be accessed by your [Tekton](tekton.md) pipeline during the image building task.
curl -X POST https://<region>.kms.cloud.ibm.com/api/v2/keys \
61
61
-H 'authorization: Bearer <IAM_token>' \
@@ -83,7 +83,7 @@ Both [Key Protect](https://cloud.ibm.com/apidocs/key-protect) and [Hyper Protect
83
83
84
84
#### Saving the public key
85
85
86
-
The public key needs to be made available to the cluster for verifying container image signatures by either creating a secret within the cluster, or making the public key available through [Artifactory](../tools/artifactory.html).
86
+
The public key needs to be made available to the cluster for verifying container image signatures by either creating a secret within the cluster, or making the public key available through [Artifactory](artifactory.md).
87
87
88
88
Use the following commands to make the public key available for policy enforcement by creating a secret within the cluster:
Copy file name to clipboardExpand all lines: mkdocs.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ site_description: >-
3
3
The Cloud-Native Toolkit is an open-source collection of assets that enable application development and support teams to deliver business value quickly using Red Hat OpenShift or Kubernetes
4
4
site_url: https://cloudnativetoolkit.dev
5
5
site_author: Cloud-Native Toolkit development team
0 commit comments