Movatterモバイル変換


[0]ホーム

URL:


Skip to main content
GitHub Docs

Kubernetes admissions controller

Understand how you can use an admissions controller to enforce artifact attestations in your Kubernetes cluster.

About Kubernetes admission controller

Artifact attestations enable you to create unfalsifiable provenance and integrity guarantees for the software you build. In turn, people who consume your software can verify where and how your software was built.

Kubernetes admission controllers are plugins that govern the behavior of the Kubernetes API server. They are commonly used to enforce security policies and best practices in a Kubernetes cluster.

Using the open sourceSigstore Policy Controller project you can add an admission controller to your Kubernetes cluster that can enforce artifact attestations. This way, you can ensure that only artifacts with valid attestations can be deployed.

Toinstall the controller, we offertwo Helm charts: one for deploying the Sigstore Policy Controller, and another for loading the GitHub trust root and a default policy.

About image verification

When the Policy Controller is installed, it will intercept all image pull requests and verify the attestation for the image. The attestation must be stored in the image registry as anOCI attached artifact containing aSigstore Bundle which contains the attestation and cryptographic material (e.g. certificates and signatures) used to verify the attestation. A verification process is then performed that ensures the image was built with the specified build provenance and matches any policies enabled by the cluster administrator.

In order for an image to be verifiable, it must have a valid provenance attestation in the registry, which can be done by enabling thepush-to-registry: true attribute in theactions/attest-build-provenance action. SeeGenerating build provenance for container images for more details on how to generate attestations for container images.

About trust roots and policies

The Sigstore Policy Controller is primarily configured with trust roots and policies, represented by the Custom ResourcesTrustRoot andClusterImagePolicy. ATrustRoot represents a trusted distribution channel for the public key material used to verify attestations. AClusterImagePolicy represents a policy for enforcing attestations on images.

ATrustRoot may also contain aTUF repository root, making it possible for your cluster to continuously and securely receive updates to its trusted public key material. If left unspecified, aClusterImagePolicy will by default use the open source Sigstore Public Good Instance's key material. When verifying attestations generated for private repositories, theClusterImagePolicy must reference the GitHubTrustRoot.

Next steps

When you're ready to use an admission controller, seeEnforcing artifact attestations with a Kubernetes admission controller.


[8]ページ先頭

©2009-2025 Movatter.jp