origin
OpenShift Origin is the open-source upstream project for Red Hat's OpenShift container platform. It provides a conformance test suite and end-to-end testing framework for Kubernetes-based deployments, with support for CI/CD pipelines and container orchestration.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | openshift/origin |
| Owner | openshift |
| Primary language | Go |
| License | Apache-2.0 — OSI-approved |
| Stars | 8.7k |
| Forks | 4.8k |
| Open issues | 284 |
| Latest release | v3.11.0 (2018-10-11) |
| Last updated | 2026-07-08 |
| Source | https://github.com/openshift/origin |
What origin is
Go-based project that maintains the `openshift-tests` binary for conformance testing and e2e validation of OpenShift clusters. As of July 2020, it vendors Kubernetes from openshift/kubernetes fork and focuses on test exclusion rules, environmental selectors, and integration with upstream Kubernetes e2e tests.
Get the origin source
Clone the repository and explore it locally.
git clone https://github.com/openshift/origin.gitcd origin# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Determine which branch to use: main/release-4.6+ (openshift-tests only) vs. release-4.5 and below (includes hyperkube). Latest branches vendor from openshift/kubernetes, requiring familiarity with that dependency model.
- Build the openshift-tests binary via `make` and configure test exclusion rules using environment selectors (not annotations) to filter tests based on cluster configuration.
- Understand vendoring strategy: script `hack/update-kube-vendor.sh` manages k8s.io/kubernetes and staging repo dependencies. May encounter '410 Gone' errors; set `GOSUMDB=off` if needed.
- Plan for test execution using extended test framework in `test/extended/` directory; requires cluster access and proper test environment setup.
- Monitor both origin and openshift/kubernetes repositories for backports and carries to ensure your test suite stays in sync with your cluster version.
When to avoid it — and what to weigh
- Non-Kubernetes Environments — If your infrastructure does not run Kubernetes or OpenShift, this project will not be applicable. It is tightly coupled to Kubernetes and OpenShift architecture.
- Simple Container Deployments — Small teams running basic container workloads without complex orchestration needs may find the overhead of running a full conformance test suite unnecessary and complex.
- Limited Go Expertise — The codebase is in Go and requires understanding of Kubernetes internals, test frameworks, and potentially vendor management. Teams without Go or Kubernetes experience will face steep learning curves.
- Outdated Release Requirements — Latest release (v3.11.0) is from October 2018. If your organization requires recent features or active upstream support, review whether your OpenShift version aligns with current maintenance branches.
License & commercial use
Apache License 2.0 (Apache-2.0). Permissive OSI-approved license allowing commercial use, modification, and distribution with attribution and liability disclaimers.
Apache-2.0 is a permissive open-source license that explicitly permits commercial use without requiring source code disclosure. However, verify your specific OpenShift deployment model (community OKD vs. Red Hat OpenShift Enterprise) for commercial support and licensing agreements, which may be separate from this repository's license.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | High |
| DEV.co fit | Good |
| Assessment confidence | Medium |
As a test suite executed against live clusters, it requires sensitive cluster access. No specific security audit data provided. Ensure proper RBAC, network isolation, and credential handling when executing tests. Dependency on openshift/kubernetes fork requires monitoring for upstream security patches.
Alternatives to consider
CNCF Kubernetes Conformance Tests (sonobuoy)
Official CNCF tool for Kubernetes conformance testing. Lighter weight, vendor-neutral, and well-maintained. Suitable if you need standard k8s validation without OpenShift-specific extensions.
Red Hat OpenShift Test Framework (OCP documentation)
If using Red Hat OpenShift Enterprise, the official product documentation and commercial support include tested validation procedures. May be preferable for production systems with SLA requirements.
Kubernetes e2e tests (upstream k/k)
Upstream Kubernetes e2e test suite. Use directly if running vanilla Kubernetes and do not need OpenShift-specific conformance, test exclusions, or platform extensions.
Build on origin with DEV.co software developers
Evaluate whether origin's test suite fits your OpenShift deployment. For production systems, consider Red Hat's commercial support or alternatives like sonobuoy for vanilla Kubernetes.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
origin FAQ
Can I use this to test vanilla Kubernetes clusters?
Which OpenShift versions does this support?
Do I need to build from source?
What is the difference between this repo and openshift/kubernetes?
Work with a software development agency
Need help beyond evaluating origin? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source devops integrations — and maintain them long-term.
Need OpenShift Testing & Validation?
Evaluate whether origin's test suite fits your OpenShift deployment. For production systems, consider Red Hat's commercial support or alternatives like sonobuoy for vanilla Kubernetes.