📄️ Architecture
This page will walk through the architecture of the Carbide Secured Registry (CSR), including both of the pipelines related to the CSR, as well as typical usage of the images.
📄️ Carbide Helm Charts
Along with our secured images, we also provide helm charts through the CSR to install various components of the Carbide product suite. These charts include the necessary components to run STIGATRON, an airgapped copy of all Rancher product docs, and a custom build of Rancher with our white-labeling.
🗃️ configuration
2 items
📄️ Copying Images to a Registry
The Carbide Secured Registry (CSR) is not intended to be used as the primary registry for running Kubernetes clusters. Instead, follow these steps to copy the images from the CSR to your own registry for later use.
📄️ Downloading the Images
The Carbide Secured Registry (CSR) is not intended to be used as the primary registry for running Kubernetes clusters. Instead, follow these steps to download and package the images to move over an airgap to your own registry.
📄️ Enforcement
Policy enforcement engines can be used to validate your cluster images against our public key. This will ensure only the images from our hardened registry are allowed to run.
📄️ Introduction
What is the Carbide Secured Registry (CSR)?
📄️ Loading Images to a Registry
Once you've downloaded your desired images from the Carbide Secured Registry (CSR), follow these steps to load copy the content to your airgapped registry.
📄️ Prerequisites
Below are all the things you need to get started with the Carbide Secured Registry (CSR). As we improve and streamline the process, this list could evolve.
📄️ Release Cadence
Build Pipelines
📄️ RKE2/K3s Uninstall
K3s
📄️ Rancher Uninstall
This page will walk you through how to uninstall Carbide Registry Images from Rancher, both for its own components and downstream Rancher Kubernetes clusters (RKE2/K3s).
📄️ Validating Images
Images in the Caride Secured Registry (CSR) allow for signature validation and downloading artifacts with metadata about the image such as Software Bill of Materials (SBOMs), Vulnerability Scans, and Cryptographic Signatures.