openshift / release
Release tooling for OpenShift
AI Architecture Analysis
This repository is indexed by RepoMind. By analyzing openshift/release in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Embed this Badge
Showcase RepoMind's analysis directly in your repository's README.
Repository Overview (README excerpt)
Crawler viewOpenShift Release Tooling This repository holds OpenShift cluster manifests, component build manifests and CI workflow configuration for OpenShift component repositories for both OKD and OCP. CI Workflow Configuration To setup a CI workflow for a new repository, use . See the Contributing CI Configuration to the openshift/release Repository document for detailed information about how to contribute to this repository. Configuration files for CI workflows live under and are split into the following categories: • contains configuration for the , detailing builds and tests for component repositories. • contains configuration for , detailing job triggers. In almost all cases, this configuration is generated automatically from the config. For manual edits, see this section of the contribution document and the upstream configuration document. Prefer the config whenever possible. • contains the registry of reusable test steps and workflows. See the documentation for this content here. • **[LEGACY]** contains black-box test workflows for use by the . The parent directory's README documents how to use them. See the template document for general information on template tests. Templates are legacy and new ones should not be added. Multi-stage tests using steps from the shared registry should be used instead. Cluster and Service Configuration Manifests Core Services and Configuration _Only folder is applied to the cluster api.ci._ Except user secret management, no services are running on . Additional Services and Configuration (legacy) _This folder is no longer applied to the cluster api.ci which is going to be offline soon._ Cluster Configuration Manifests (legacy) Manifests for cluster provisioning and installation live under . The OpenShift CI cluster is configured with the manifests under . (**legacy**: do not add new services here. Use or instead.) Clusters that are created by the testing infrastructure for validating OpenShift are configured with the profiles under . For directions on how to set up clusters for development, see the README. Legacy Service Configuration Manifests for services that are in development, experimental, legacy or not critical in some other way are present in the directory. Compared to the core services and services configuration, these projects do not need to follow any common structure or conventions other than clear ownership. They must not interfere with the core services in any way. Additionally, manifests for building container images for component repositories live under . This purpose is deprecated; authors of components built by manifests in this directory should remove them and ensure that their component is appropriately built by the instead. Tooling Build Manifests Manifests for building container images for tools live under . These tools are either useful in managing this repository or are otherwise useful commonly across component repositories.