Red Hat OpenShift Container Platform
Everything you need to manage your development lifecycle, including standardized workflows, support for multiple environments, continuous integration, and release management.
OpenShift is for developers
Red Hat OpenShift is a Kubernetes distribution focused on developer experience and application security that's platform agnostic. OpenShift helps you develop and deploy applications to one or more hosts. These can be public facing web applications, or backend applications, including micro services or databases. Applications can be implemented in any programming language you choose. The only requirement is that the application can run within a container.
In terms of cloud service computing models, OpenShift implements the functionality of both a Platform as a Service (PaaS) and a Container as a Service (CaaS). Using OpenShift as a CaaS, you can bring a pre-existing container image built to the OpenShift Container Initiative (OCI) Image Specification (image-spec) and deploy it.
The PaaS capabilities of OpenShift build on top of the ability to deploy a container image, by providing a way for you to build in OpenShift your own container image direct from your application source code and have it deployed.
The application source code can include a
Dockerfile with instructions to build a container image. Or, you can use a Source-to-Image (S2I) builder, which takes your application source code and converts it into a container image for you, without you needing to know how to write instructions for building a container image.
New for developers in Red Hat OpenShift 4
Operators make it easy to get the software you need installed and running quickly. One click, or entry at the command line, is all you need—the Operator will manage it from there.
For example, you might want to use a Kafka cluster for your event-driven application. Instead of creating all of the dependencies, such as ZooKeeper, you can simply use the Operator to create your Kafka instance. All of the dependencies and connections are created for you. There are Operators for event handling, databases, monitoring, and dozens of other aspects. Focus on your code; let the Operator support your efforts.
OpenShift Pipelines with Tekton makes it simple to set up a CI/CD pipeline.
Not just any CI/CD pipeline, but one that is containerized. What does that mean? It means that you don’t provision and configure a server. It means that it runs on demand (thanks to OpenShift Serverless) and sits idle when not used. It means that you define your Tasks and Pipelines in the format that is familiar to you when you work with Kubernetes. It means that you get more work done with less effort.
Tasks can run in parallel and be fed from many sources: a Git repo, a container image, and more. Pipelines can be reused and shared since the resources are externalized. Builds are now a part of your regular OpenShift workflow. The developer can now develop the pipeline as well as the application.
OpenShift Service Mesh allows you to create routes for deployments, mimic errors, establish circuit breakers, and more, without changing your code.
No more external libraries are needed for important microservices features. With OpenShift Service Mesh you can trace and monitor your code, roll out new versions, change the routing, and even test error handling without ever touching your code. For the developer, this means your well-tested compiled code stays as-is, with no chance of introducing new defects after a build is finished.
The library of VS Code Extensions for OpenShift keeps growing.
You can debug your code, maintain your OpenShift pipelines, launch builds, test, and do every other necessary development activity directly from your VS Code IDE. Tight integration with OpenShift means that you can code, test, and debug locally while deploying to any cloud, anywhere.
Serverless applications are easier than ever thanks to OpenShift Serverless.
OpenShift Serverless takes Knative Serving and makes it easily available and usable to the developer. You can quickly take any application and make it into an on-demand serverless application by using OpenShift Serverless. Stateless and stateful applications both work seamlessly and allow you to focus on your existing coding languages and models instead of spending your time learning yet another Functions-as-a-Service implementation.
‘odo’, the command-line interface for developers.
No more time spent learning how the folks in Operations run your OpenShift cluster. Instead of needing three or four commands that you use over and over, why not simplify? That’s what ‘odo’ does: It provides you, the developer, with a simple command-line tool that relies on convention over configuration, a concept that developers everywhere embrace. It’s the OpenShift tool for developers, made by OpenShift developers.