Overview: Deploy Red Hat Trusted Artifact Signer using Google Cloud and Cosign
Organizations can face significant challenges in validating the authenticity of their deployed container images within their production environments. Cryptographic signing of container images helps to verify the integrity of the container and ensures that it has not been tampered with since its deployment into production. Verification of the container image signature also confirms that the expected software owner, whose identity was certified at the moment of signing, is the published container image running in production. Red Hat Trusted Artifact Signer (RHTAS), a cryptographic signature and validation tool based on the Sigstore project, helps confront these challenges.
In this learning path, we will install the Red Hat Trusted Artifact Signer Operator, configure Google Cloud as our OpenID Connect (OIDC) provider, and sign and verify a container image. We will use code-signed certificates with short-lived signing keys bound to Google Cloud OAuth accounts. This keyless signing approach offers simplicity due to the lack of a key management infrastructure.
Prerequisites:
- Red Hat OpenShift Container Platform 4.17 or later.
- A Google Cloud user account to sign and verify a container image.
- A workstation with command-line access to use the
oc, andpodmanbinaries.
In this learning path, you will:
- Learn how to install the RHTAS Operator on Red Hat OpenShift.
- Deploy the RHTAS service with Google Cloud OAuth as the OIDC provider.
- Create a Google Cloud OAuth client identifier.
- Sign and verify a container image by using
cosign.
How long will this activity take?
- About 15–20 minutes