Introducing Red Hat OpenShift 4
Some days before on 8th May 2019 at Red Hat Summit Red Hat celebrate the announcement of Red Hat OpenShift 4, which will be available next month.
A big thank you to our customers for more than 1,000 organizations around the world, our partners, the community of Kubernetes in general and our Red Hat teams for all the progress we have made together on the platform.
In this first important release, since make four years Red Hat redesigned by full OpenShift 3 in Kubernetes, Red Hat go beyond Kubernetes and the fully integrated platform that Red Hat offer through OpenShift, and Red Hat redefined Kubernetes for the company through full stack automation.
Making the vision of Red Hat and CoreOS
This represents the realization of the vision and the plans that Red Hat present with the team of CoreOS shortly after the Red Hat acquisition closed almost 15 months ago But it also represents years of work by both companies that innovate in the communities of Kubernetes and containers, providing that innovation to business customers in a consumable form and listening to their comments and challenges.
It was amazing to see how quickly our teams came together, with a unified mission, to offer a fully integrated platform OpenShift4 that combines the best ideas and innovations of both companies Today, there are many providers that try to offer their own Kubernetes solutions But nobody can match the experience, the experience and the innovation of Kubernetes of level business that Red Hat contributes through OpenShift .
Kubernetes in the Core with Full Stack Automation
OpenShift 4 is Kubernetes In its core and in this version Red Hat have completely redesigned the way Red Hat install, update and manage the platform, while Red Hat incorporate the advanced administration and automation of day 2 to the services of applications that run on the platform These advances are based on many new innovations in the ecosystem of Kubernetes, none larger than operators of Kubernetes .
Operators automate the lifecycle management of containerized applications with Kubernetes With Operators, administrators can extend the API of Kubernetes to encode operational knowledge and workflows to manage complex applications directly in those services, so that they run smoothly in Kubernetes For the customers of OpenShift and the ISV partners, this allows them to bring the same level of administration and automation found in public cloud services to their own services, while providing a consistent operating model to run these services in the hybrid cloud.
Given the OpenShift It is a platform completely in containers that consists of many different components, Red Hat also take advantage of the Operators to promote the installation and updates of OpenShift and all its services This includes basic services Kubernetes, together with Prometheus, Grafana, Elasticsearch, networks defined by software, storage, registration and other components that make up the OpenShift Platform kubernetes .OpenShift 4 is a platform run by an operator that offers full stack automation from top to bottom Since Kubernetes, to the central services that support the Cluster OpenShift, to the application services implemented by the end users; Everything is managed throughout its life cycle with the operators.
Trusted Enterprise Kubernetes
Deliver one solution of Kubernetes for trustworthy companies means delivering trusted container content, a trusted container platform, and a trusted Linux host infrastructure to run it This has been our focus with OpenShift 3, which base in the solid foundation of Red Hat Enterprise Linux, and provides a OpenShift more secure and reliable Distribution of Kubernetes and delivery of certified container images through the Catalog of Red Hat containers.
When Red Hat Red Hat arranged to build OpenShift 4, Red Hat wanted to address the challenges that customers still faced by installing the platform consistently and keeping it updated with the latest security patches and releases of Kubernetes in fast movement Red Hat also wanted to facilitate the implementation of complex applications in the platform and manage them throughout the life cycle To do this, Red Hat need to consistently unify and manage all aspects of the platform, both day 1 and day 2.
Installation challenges and update of Kubernetes of full stack
This started with rethinking how Red Hat installed the platform OpenShift on day 1. To install OpenShift 3.x, a user first manually configures the underlying infrastructure layer, whether they are running OpenShift in the public cloud or on your own center data Then they deploy Red Hat Enterprise Linux instances and execute the installer OpenShift 3.x, which takes advantage Ansible, to automate the implementation and configuration of control plane Kubernetes, work nodes and integrated platform services From the second day, the platform OpenShift it is managed and updated separately from the underlying RHEL infrastructure, although both must remain synchronized with compatible versions.
This creates a couple of challenges First, the burden of configuring the provider’s infrastructure and installing the RHEL operating system is a separate activity of OpenShift Installation of Kubernetes ; Creating more work for the administrator of the platform Second, updates or changes made by Linux administrators may be incompatible with the platform layer Kubernetes, which could cause problems during the updates of the platform OpenShift These challenges are not exclusive to OpenShift, are present in any platform Kubernetes, which has led Red Hat and the community of Kubernetes to explore new innovations to face them.
With this in mind, Red Hat set out to offer a better installation experience and full stack update with OpenShift Four.
Full stack automation delivery
OpenShift 4 unifies the operations through the layers of the platform, to provide complete stack automation from the underlying infrastructure, to the RHEL operating system, to the OpenShift Platform Kubernetes and its integrated services OpenShift 4 uses Kubernetes to provision and scale their clusters of Kubernetes, taking advantage of the new installer OpenShift The new installer first asks you what infrastructure you want to implement OpenShift and will provide you with the credentials to access that infrastructure Depending on your choice, then configure that infrastructure in your name and, starting from a single node of Kubernetes, start a Cluster of Kubernetes complete and high availability in minutes.
This installation process includes provisioning of the Linux host operating system OpenShift will run, taking advantage of Red Hat Enterprise LinuxCoreOS RHEL CoreOS offers a fully immutable and optimized Linux operating system host for containers that is delivered and installed as a component of OpenShift RHEL CoreOS is RHEL, which leverages the latest core and core libraries of RHEL 8, but is delivered as an immutable host image Therefore, it benefits from the compatibility, reliability and innovation offered by the RHEL team.
To carry out the installation, the installer OpenShift takes advantage of vendor-specific machine controllers that automate the provisioning of hosts compatible with Kubernetes These drivers not only support the initial installation of the Cluster Kubernetes, but also give you the ability to add and remove work nodes, to scale the cluster’s capacity over time to meet user demand This ability to scale automatically cluster resources means that customers can optimize the use of the infrastructure to meet demand and better control costs.
In addition to the “infrastructure” approach provided by the installer “that offers OpenShift 4, the installer will also enable an “infrastructure provided by the user” mode for users who want to configure their own infrastructure of center data or cloud or manage your Linux operating system separately using your existing traditional systems.Distribution of RHEL This gives administrators more flexibility in closed environments where it may be necessary.
The extension of Automation of Install updates
The objective of OpenShift 4 was not only to simplify the initial installation, but also the updates, taking advantage of the same approach driven by the operator combined with an air-guided update model In OpenShift 4, the clusters are implemented with telemetry to inform about the status of the cluster over time.
If those clusters are connected to Red Hat, users can be notified when there are critical updates or new versions available and get them immediately Since the operators are supporting the components of the platform OpenShift, will drive the updates of any component that requires updates, including Kubernetes and the host RHEL CoreOS Disconnected clusters that run in airspace environments will extract those updates from a local content registry, which Red Hat are developing now, but will take advantage of the same automation driven by the operator to implement them Ultimately, the goal is to reduce friction in the updating process, so that clusters of OpenShift They can be more secure and updated.
A cloud experience, everywhere.
OpenShift 4 can be implemented in all major public and private cloud platforms with a few clicks, so that users can be up and running quickly The heterogeneous support is anticipated in the coming months in the main public cloud providers, including Amazon Web Services (AWS), Microsoft Azure, Google Cloud, IBM Cloud, private cloud platforms developed by Red Hat OpenStack, virtualization platforms such as VMWare and Red Hat Virtualization and even the smallest. – Metallic infrastructure.
The management of several clusters of across multiple clouds
While OpenShift 4 simplifies the installation and updates of your Cluster Kubernetes, Red Hat know that most of the customers of OpenShift have multiple clusters and, in many cases, these clusters are deployed in multiple sites infrastructure of cloud or local To help make this easier to administer, OpenShift 4 introduces a new unified hybrid cloud console at cloud.redhat.com This console will allow clients to see and manage multiple clusters of OpenShift .
Users can register the clusters of OpenShift existing, as well as provisioning new clusters of OpenShift in multiple clouds and infrastructure footprints on site they can see which version they are running their clusters and manage the updates and, in the future, get access to metrics from various clusters, control panels and more.
Enable services in the hybrid cloud with Operators and OperatorHub
Ultimately, our goal is to allow the customers of OpenShift offer an experience similar to the cloud everywhere This objective is not only for clusters of OpenShift, but also extends to the services that run on those clusters Its developers and end users want to consume those services everywhere, with the same experience in the cloud In order to simplify the administration process of these distributed services, Red Hat present the operators of Kubernetes, which have been fundamental to the way Red Hat provides services, but have also extended to our ISV ecosystem.
Recently Red Hat launched OperatorHub.io with partners such as AWS, Google Cloud and Microsoft to provide a community record where users can find operators of Kubernetes cured You can also access the Operator Hub content through the console OpenShift 4. OpenShift 4 will also include certified operators through Red Hat OpenShift Operator Certification This program allows ISV partners to jointly build and certify their operators with Red Hat and unify support for operators in OpenShift, for our joint clients.
With the Operator Lifecycle Manager (OLM) in OpenShift 4, the operators help to provide the administration capacity, the traceability and the responsibility to which the developers have become accustomed in the public cloud, at the same time that they unify said service offers in both the public and private cloud IT teams can establish policies using operators that help provide the governance and oversight of the resources that are often required in the regulated industries, without having to manually provision these resources for the developer teams.
Train Developers to Innovate
The objective of OpenShift is to help developers to innovate more quickly, to address the needs of the business The development of native applications in the cloud brings new challenges As developers adopt the architectures of microservice, the management of the communication between each service, the protection of those services and the improvement of the traceability from service to service to solve problems is an absolute necessity These are the challenges that the open source project of Istio seeks to address.
the Service mesh OpenShift 4 taking Istio and combines it with other key projects, such as Jaeger for tracking and Kiali for visualization, to provide better management and traceability capabilities implementations of microservices Developers can focus on developing business logic, allowing the service mesh to manage how it works communicate every microservice in function of the policies they define They can also take advantage of tracking and viewing capabilities to debug problems when they occur.
Development approaches have not stopped evolving, and without server is another way in which developers seek to create applications, taking advantage of the function as a service based on offers The construction functions that take advantage of a model without server they allow the possibility of scaling to zero and only consume computing resources when they are executed, which can be an effective way to control operational costs, particularly in the public cloud The offers from FaaS they were first started by public cloud providers like AWS, but have the potential to block their applications in a single cloud environment For this reason, Red Hat is working to bring these capabilities to a hybrid cloud environment through Knative .
Knative is an open source project in which Red Hat is collaborating with the community Kubernetes to boost upward development that allows capabilities hybrid without server Using the framework Knative enabled in OpenShift, users can extend Kubernetes to build, implement and manage Applications without server, admitting implementations in containers and without server from a single control plane of Kubernetes .
To meet with developers where they live, they can code and interact with OpenShift from their embedded developer environmentsfavorites (IDE) using add-ins for environments such as VSCode, IntelliJ and Eclipse Through Red Hat CodeReady Workspaces, developers can take advantage of an IDE based on a fully integrated web browser that allows developers to easily collaborate on the code CodeReadyWorkspaces is based on the draft Eclipse Che and it’s fully compatible with Red Hat for the development of OpenShift .
For those developers who simply live on the command line, Red Hat has also created a command line interface (CLI), called odo, designed to improve the way in which the code is stores in containers and is implemented in OpenShift the developers can use odo to build applications and iterate quickly in the code.
Platforms are nothing without the content they provide to build applications OpenShift 4 offers a large amount of middleware, databases, storage and other certified Red Hat runtimes and our ISV partners All this content is ready for the container and will be backed by operators to promote better management and automation This includes solutions for application integration, messaging and automation of the Red Hat Middleware portfolio It will also include OpenShift of storage containers, which will be fully operator driven Ceph leverage and the Torre project in OpenShift 4. Developers can access all through OperatorHub.io this content, or OperatorHub embedded in its console OpenShift
OpenShift 4: Enterprise Kubernetes Renewed
OpenShift 4 renews the promise Red Hat made 4 years ago when Red Hat launched the first platform Kubernetes business of the industry withOpenShift 3. It is designed to offer a unified experience in the hybrid cloud by boosting installation and updates automatic in all implementations of Kubernetes, With the technology of Kubernetes The operators OpenShift 4 is still based on a Red Hat Enterprise Linux kernel, and is delivered in a new immutable form such as Red Hat Enterprise Linux CoreOS and is fully integrated and managed as a component of the platform OpenShift .
Operators extend this automation to any service running on the platform, including certified Red Hat operators and our ecosystem of ISV partners OpenShift 4 will also provide a host of new developer services and capabilities needed to create native applications in the cloud and consistently deploy them to any compatible local, private, or public cloud infrastructure Red Hat OpenShift 4 Kubernetes for the Enterprise, designed to drive the transformation of the business and unite its development teams in a single platform.
It is programmed that Red Hat OpenShift 4 is available next month, but in the meantime you can prove it.