OpenShift Origin is a distribution of Kubernetes optimized for continuous application development and multi-tenant deployment. Origin adds developer and operations-centric tools on top of Kubernetes to enable rapid application development, easy deployment and scaling, and long-term lifecycle maintenance for small and large teams.
Features:
- Easily build applications with integrated service discovery and persistent storage.
- Quickly and easily scale applications to handle periods of increased demand.
- Support for automatic high availability, load balancing, health checking, and failover.
- Push source code to your Git repository and automatically deploy containerized applications.
- Web console and command-line client for building and monitoring applications.
- Centralized administration and management of an entire stack, team, or organization.
- Create reusable templates for components of your system, and iteratively deploy them over time.
- Roll out modifications to software stacks to your entire organization in a controlled fashion.
- Integration with your existing authentication mechanisms, including LDAP, Active Directory, and public OAuth providers such as GitHub.
- Multi-tenancy support, including team and user isolation of containers, builds, and network communication.
- Allow developers to run containers securely with fine-grained controls in production.
- Limit, track, and manage the developers and teams on the platform.
- Integrated Docker registry, automatic edge load balancing, cluster logging, and integrated metrics.
Learn More:
- Public Documentation
- Technical Architecture Presentation
- System Architecture design document
- The Trello Roadmap covers the epics and stories being worked on (click through to individual items)
For questions or feedback, reach us on IRC on #openshift-dev on Freenode or post to our mailing list.
If you have downloaded the client tools, place the included binaries in your PATH.
- For a quick install of Origin, see the Getting Started Install guide.
- For an advanced installation using Ansible, follow the Advanced Installation guide
- To build and run from source, see CONTRIBUTING.adoc
We highly recommend trying out the Origin walkthrough which covers the core concepts in Origin. The walkthrough is accompanied by a blog series on blog.openshift.com that goes into more detail. It's a great place to start.
The Origin API is located on each server at https://<host>:8443/oapi/v1. These APIs are described via Swagger v1.2 at https://<host>:8443/swaggerapi/oapi/v1. For more, see the API documentation.
If you're looking for more information about using Kubernetes or the lower level concepts that Origin depends on, see the following:
If you run into difficulties running Origin, start by reading through the troubleshooting guide.
-
How does Origin relate to Kubernetes?
Origin is a distribution of Kubernetes optimized for enterprise application development and deployment, used by OpenShift 3 and Atomic Enterprise. Origin embeds Kubernetes and adds additional functionality to offer a simple, powerful, and easy-to-approach developer and operator experience for building applications in containers. Our goal is to do most of that work upstream, with integration and final packaging occurring in Origin.
You can run the core Kubernetes server components with
openshift start kubernetes, usekubectlviaopenshift kube, and the Origin release zips include versions ofkubectl,kubelet,kube-apiserver, and other core components. You can see the version of Kubernetes included with Origin viaopenshift version. -
How does Atomic Enterprise relate to Origin and OpenShift?
Two products are built from Origin, Atomic Enterprise and OpenShift. Atomic Enterprise adds operational centric tools to enable easy deployment and scaling and long-term lifecycle maintenance for small and large teams and applications. OpenShift provides a number of developer-focused tools on top of Atomic Enterprise such as image building, management, and enhanced deployment flows.
-
What can I run on Origin?
Origin is designed to run any existing Docker images. Additionally, you can define builds that will produce new Docker images using a
Dockerfile.However, the real magic of Origin is Source-to-Image (S2I) builds, which allow developers to simply provide an application source repository containing code to build and run. It works by combining an existing S2I-enabled Docker image with application source to produce a new runnable image for your application.
We are continuing to grow the ecosystem of Source-to-Image builder images and it's straightforward to create your own. Some of our available images include:
Your application image can be easily extended with a database service with our database images:
-
Why doesn't my Docker image run on OpenShift?
Security! Origin runs with the following security policy by default:
- Containers run as a non-root unique user that is separate from other system users
- They cannot access host resources, run privileged, or become root
- They are given CPU and memory limits defined by the system administrator
- Any persistent storage they access will be under a unique SELinux label, which prevents others from seeing their content
- These settings are per project, so containers in different projects cannot see each other by default
- Regular users can run Docker, source, and custom builds
- By default, Docker builds can (and often do) run as root. You can control who can create Docker builds through the
builds/dockerandbuilds/custompolicy resource.
- By default, Docker builds can (and often do) run as root. You can control who can create Docker builds through the
- Regular users and project admins cannot change their security quotas.
Many Docker containers expect to run as root (and therefore edit all the contents of the filesystem). The Image Author's guide gives recommendations on making your image more secure by default:
- Don't run as root
- Make directories you want to write to group-writable and owned by group id 0
- Set the net-bind capability on your executables if they need to bind to ports <1024
Otherwise, you can see the security documentation for descriptions on how to relax these restrictions.
- Containers run as a non-root unique user that is separate from other system users
-
How do I get networking working?
The Origin and Kubernetes network model assigns each pod (group of containers) an IP that is expected to be reachable from all nodes in the cluster. The default setup is through a simple SDN plugin with OVS - this plugin expects the port 4679 to be open between nodes in the cluster. Also, the Origin master processes need to be able to reach pods via the network, so they may require the SDN plugin.
Other networking options are available such as Calico, Flannel, Nuage, and Weave. For a non-overlay networking solution, existing networks can be used by assigning a different subnet to each host, and ensuring routing rules deliver packets bound for that subnet to the host it belongs to. This is called host subnet routing.
-
Why can't I run Origin in a Docker image on boot2docker or Ubuntu?
Versions of Docker distributed by the Docker team don't allow containers to mount volumes on the host and write to them (mount propagation is private). Kubernetes manages volumes and uses them to expose secrets into containers, which Origin uses to give containers the tokens they need to access the API and run deployments and builds. Until mount propagation is configurable in Docker you must use Docker on Fedora, CentOS, or RHEL (which have a patch to allow mount propagation) or run Origin outside of a container. Tracked in this issue.
Some features from upstream Kubernetes are not yet enabled in Origin, for reasons including supportability, security, or limitations in the upstream feature.
Kubernetes Definitions:
- Alpha
- The feature is available, but no guarantees are made about backwards compatibility or whether data is preserved when feature moves to Beta.
- The feature may have significant bugs and is suitable for testing and prototyping.
- The feature may be replaced or significantly redesigned in the future.
- No migration to Beta is generally provided other than documentation of the change.
- Beta
- The feature is available and generally agreed to solve the desired solution, but may need stabilization or additional feedback.
- The feature is potentially suitable for limited production use under constrained circumstances.
- The feature is unlikely to be replaced or removed, although it is still possible for feature changes that require migration.
OpenShift uses these terms in the same fashion as Kubernetes, and adds four more:
- Not Yet Secure
- Features which are not yet enabled because they have significant security or stability risks to the cluster
- Generally this applies to features which may allow escalation or denial-of-service behavior on the platform
- In some cases this is applied to new features which have not had time for full security review
- Potentially Insecure
- Features that require additional work to be properly secured in a multi-user environment
- These features are only enabled for cluster admins by default and we do not recommend enabling them for untrusted users
- We generally try to identify and fix these within 1 release of their availability
- Tech Preview
- Features that are considered unsupported for various reasons are known as 'tech preview' in our documentation
- Kubernetes Alpha and Beta features are considered tech preview, although occasionally some features will be graduated early
- Any tech preview feature is not supported in OpenShift Container Platform except through exemption
- Disabled Pending Migration
- These are features that are new in Kubernetes but which originated in OpenShift, and thus need migrations for existing users
- We generally try to minimize the impact of features introduced upstream to Kubernetes on OpenShift users by providing seamless migration for existing clusters.
- Generally these are addressed within 1 Kubernetes release
The list of features that qualify under these labels is described below, along with additional context for why.
| Feature | Kubernetes | OpenShift | Justification |
|---|---|---|---|
| Third Party Resources | Alpha (1.3) | Not Yet Secure (1.2, 1.3) | Third party resources are still under active development upstream. Known issues include failure to clean up resources in etcd, which may result in a denial of service attack against the cluster. We are considering enabling them for development environments only. |
| Garbage Collection | Alpha (1.3) | Not Yet Secure (1.3) | Garbage collection will automatically delete related resources on the server, and thus given the potential for data loss we are waiting for GC to graduate to beta and have a full release cycle of testing before enabling it in Origin. At the current time, it is possible for a malicious user to trick another user into deleting a sensitive resource (like a quota or limit resource) during deletion, which must be addressed prior to enablement. |
| Pet Sets | Alpha (1.3) | Tech Preview (1.3) | Pet Sets are still being actively developed and no backwards compatibility is guaranteed. Also, Pet Sets allow users to create PVCs indirectly, and more security controls are needed to limit the potential impact on the cluster. |
| Init Containers | Alpha (1.3) | Tech Preview (1.3) | Init containers are properly secured, but are not officially part of the Kubernetes API and may change without notice. |
| Federated Clusters | Beta (1.3) | Tech Preview (1.3) | A Kubernetes federation server may be used against Origin clusters with the appropriate credentials today. Known issues include tenant support in federation and the ability to have consistent access control between federation and normal clusters. No Origin specific binary is being distributed for federation at this time. |
| Deployment | Alpha (1.2) Beta (1.3) |
Disabled Pending Migration (1.2) Tech Preview (1.3) |
OpenShift launched with DeploymentConfigs, a more fully featured Deployment object. The upstream Deployments are enabled in OpenShift as a tech preview so users can create both Deployments and DeploymentConfigs. We plan to provide migration from Deployment Config to Deployment in future when the feature parity with the upstream Deployment object is reached. Deployment Configs are currently a superset of Deployment features. |
| Replica Sets | Beta (1.2) Beta (1.3) |
Disabled Pending Migration (1.2) Tech Preview (1.3) |
Replica Sets perform the same function as Replication Controllers, but have a more powerful label syntax. We are working upstream to enable a migration path forward for clusters with existing Replication Controllers deployed to be automatically migratable to Replica Sets, in order to ease the transition for clients and tooling that depend on RCs. |
| Ingress | Alpha (1.1) Beta (1.2, 1.3) |
Disabled Pending Migration (1.2) Tech Preview (1.3) |
OpenShift launched with Routes, a more full featured Ingress object. The upstream Ingress are enabled in OpenShift as a tech preview, so users can create both Ingress and Route resources. We plan to provide migration from Route to Ingress in future when the feature parity with the upstream Ingress is reached. Routes are currently a superset of Ingress features. |
| PodSecurityPolicy | Alpha (1.2) Beta (1.3) |
Disabled Pending Migration (1.3) Not Yet Secure (1.3) |
OpenShift launched with SecurityContextConstraints, and then upstreamed them as PodSecurityPolicy. We plan to enable upstream PodSecurityPolicy so as to automatically migrate existing SecurityContextConstraints. PodSecurityPolicy has not yet completed a full security review, which will be part of the criteria for tech preview. SecurityContextConstraints are a superset of PodSecurityPolicy features. |
| PodAntiAffinitySelectors | Alpha (1.3) | Not Yet Secure (1.3) Tech Preview (1.4?) |
End users are not allowed to set PodAntiAffinitySelectors that are not the node name due to the possibility of attacking the scheduler via denial of service. |
| NetworkPolicy | Beta (1.3) | Tech Preview (1.3) | OpenShift's default network plugins (redhat/openshift-ovs-subnet and redhat/openshift-ovs-multitenant) do not support NetworkPolicy yet, but if you use a third-party network plugin, it might. |
Please contact us if this list omits a feature supported in Kubernetes which does not run in Origin.
You can develop locally on your host or with a virtual machine, or if you want to just try out Origin download the latest Linux server, or Windows and Mac OS X client pre-built binaries.
First, get up and running with the Contributing Guide.
All contributions are welcome - Origin uses the Apache 2 license and does not require any contributor agreement to submit patches. Please open issues for any bugs or problems you encounter, ask questions on the OpenShift IRC channel (#openshift-dev on freenode), or get involved in the Kubernetes project at the container runtime layer.
See HACKING.md for more details on developing on Origin including how different tests are setup.
If you want to run the test suite, make sure you have your environment set up, and from the origin directory run:
# run the verifiers, unit tests, and command tests
$ make check
# run a command-line integration test suite
$ hack/test-cmd.sh
# run the integration server test suite
$ hack/test-integration.sh
# run the end-to-end test suite
$ hack/test-end-to-end.sh
# run all of the tests above
$ make test
You'll need etcd installed and on your path for the integration and end-to-end tests to run, and Docker must be installed to run the end-to-end tests. To install etcd you should be able to run:
$ hack/install-etcd.sh
Some of the components of Origin run as Docker images, including the builders and deployment tools in images/builder/docker/* and 'images/deploy/*`. To build them locally run
$ hack/build-images.sh
To hack on the web console, check out the assets/README.md file for instructions on testing the console and building your changes.
Origin is licensed under the Apache License, Version 2.0.