, the whole essence of which continues the course towards automation and optimization of work with the cloud environment.
Recall that in May 2019 we introduced Red Hat OpenShift 4, the next generation of our Kubernetes platform, which we redesigned to simplify the management of containerized applications in production environments.
Designed as a self-managed platform with auto-update and lifecycle management features in a hybrid cloud, the solution is built on proven Red Hat Enterprise Linux and Red Hat Enterprise Linux CoreOS. In version 4.2, the focus was on making the platform more developer friendly. In addition, we have made it easier for cluster administrators to manage the platform and applications by offering migration tools from version 3 to version 4 of OpenShift, as well as by implementing support for offline configurations.
Where is the speed?
Version 4.2 greatly simplifies working with Kubernetes, offering a new OpenShift management console mode optimized for developer tasks, as well as new tools and plugins for building containers, organizing CI / CD pipelines, and implementing serverless systems. All this helps programmers focus more on their main task - creating application code, without being distracted by the peculiarities of Kubernetes.
View application topology in the developer console.
New developer mode of the OpenShift console
New developer tools in OpenShift 4.2:
- The web console helps developers focus on what matters most by displaying only the information and configurations they need. An improved topology view and application build UI makes it easy to create, deploy, and visualize containerized applications and cluster resources.
- ΠΠ½ΡΡΡΡΠΌΠ΅Π½ΡΠ°ΡΠΈΠΉ is a special command line interface for developers that simplifies the development of applications on the OpenShift platform. With a git push-like interaction, this CLI helps developers to effortlessly build applications on the OpenShift platform without having to understand the intricacies of Kubernetes.
- for Microsoft Visual Studio Code, JetBrains IDE (including IntelliJ), and Eclipse Desktop IDE provides easy tool integration and allows you to develop, build, debug, and deploy OpenShift applications in a developer-familiar IDE.
- Red Hat OpenShift Deployment Extension for Microsoft Azure DevOps. Provides users of this DevOps toolkit with the ability to deploy their applications to Azure Red Hat OpenShift or any other OpenShift clusters on the Microsoft Azure DevOps platform.
Plugin for Visual Studio
Full OpenShift on a laptop
, which are pre-built OpenShift clusters optimized for deployment on a workstation or laptop, allowing you to develop cloud applications locally.
Service Mesh
Our solution , built on the basis of free software projects by Istio, Kiali and Jaeger and a special , simplifies the development, deployment and maintenance of applications on the OpenShift platform by providing the necessary tools and taking over the automation of cloud applications based on modern architectures such as microservices. The solution frees programmers from the need to independently deploy and maintain specialized network services required for the applications and business logic being created.
, , designed for the developer literally "from and to" and offers features such as tracing, metrics, visualization and observation of network communications, as well as one-click installation and configuration of the service mesh. In addition, the solution offers operational management and security benefits, such as encryption of traffic between servers within the data center and integration with an API gateway. .
Extended visualization of cluster traffic using Kiali tools within the OpenShift Service Mesh
Serverless computing
Our other solution , helps you deploy and run applications that easily scale up and down on demand down to zero. Based on the Knative project and available in Technology Preview, this solution can be activated on any OpenShift 4 cluster using the appropriate Kubernetes operator, which makes it easy to get started and install the components required to deploy serverless applications or features on OpenShift. The developer mode of the OpenShift console, which appeared in version 4.2, allows you to use serverless options in standard development processes, such as Import from Git or Deployan Image, in other words, you can create serverless applications directly from the console.
Setting up serverless deployment in the OpenShift console
In addition to integration with the developer console, the new version of OpenShift has other improvements in terms of serverless. In particular, it is kn - the Knative command line interface, which provides a convenient and understandable work, allows you to group objects necessary for applications; take snapshots of code and configurations, as well as the ability to map network endpoints to specific versions or services. All of these features, available in the Technology Preview through the OpenShift Serverless operator, help developers get comfortable with the serverless architecture and deploy their applications in the hybrid cloud flexibly without being locked into specific infrastructures.
Cloud CI/CD Pipelines
Continuous integration and delivery (CI/CD) are key development practices today that increase the speed and reliability of software deployment. A good CI/CD toolkit allows development teams to streamline and automate feedback processes, which is critical to successful agile development. In OpenShift, you can use the classic Jenkins or our new solution as such a toolkit. .
Jenkins is the de facto standard today, but we're linking the future of container CI/CD to Tekton's free software project. Therefore, OpenShift Pipelines is built on the basis of this project and better supports such typical approaches for cloud solutions as pipeline-as-code (βpipeline as codeβ) and GitOps. In OpenShift Pipelines, each step runs in its own container, so resources are only used during the execution of that step, allowing developers full control over their delivery channels, plugins, and access control without using a central CI/CD server.
OpenShift Pipelines is currently in Developer Preview and is available as a corresponding operator that can be used in any OpenShift 4 cluster. Jenkins can be used in both OpenShift 3 and 4.
Red Hat OpenShift Pipelines
Hybrid cloud container management
The automated installation and upgrade of OpenShift brings the hybrid cloud as close as possible to the canonical cloud in terms of user experience. OpenShift 4.2 was previously available for major public clouds, private clouds, virtualization platforms, and bare-metal servers, but version XNUMX adds two more new public clouds to the list - Microsoft Azure and Google Cloud Platform, as well as OpenStack private clouds .
The OpenShift 4.2 installer has been improved for various target environments, and for the first time it has been trained to work with isolated (not connected to the Internet) configurations. Sandboxed installation and mandatory proxy mode with the ability to provide your own certificate chains (CA bundle) help ensure compliance with regulatory standards and internal security protocols. Standalone installation mode allows you to always have the latest version of the OpenShift Container Platform where there is no Internet access or in environments with strict image testing policies.
In addition, deploying a full OpenShift stack using Red Hat Enterprise Linux CoreOS, a lightweight version of Red Hat Enterprise Linux, allows you to have a cloud ready in less than an hour from installation.
Red Hat OpenShift allows you to unify the process of creating, deploying and managing containerized applications in the cloud and on on-premises infrastructures. With a simpler, more automated, and faster deployment, OpenShift 4.2 is now available on AWS, Azure, OpenStack, and GCP platforms, enabling organizations to efficiently manage their Kubernetes platforms in the hybrid cloud.
Easy migration from OpenShift 3 to OpenShift 4
New workload migration tools make it easier to migrate to OpenShift 4.2 from previous versions of the platform. Transferring workloads from an old cluster to a new one is now much faster, easier, and with a minimum of manual steps. The cluster administrator just needs to select the source OpenShift 3.x cluster, mark the desired project (or namespace) on it, and then specify what to do with the corresponding persistent volumes - copy them to the target OpenShift 4.x cluster or migrate. The applications then continue to run on the original cluster until the administrator terminates them.
OpenShift 4.2 supports various migration scenarios:
- The data is copied using an intermediate repository based on the Velero project. This option allows you to migrate with a change of storage system, when, for example, Gluster is used in the original cluster, and Ceph is used in the new one.
- The data remains in the current repository, but it connects to a new cluster (persistent volume switchover).
- Copying Filesystems with Restic.
The right of the first night
Often, our users would like to be able to try out planned OpenShift innovations long before a new release is released. . Please note that these builds are not intended for production use, are not supported, are poorly documented, and may not be fully functional. The quality of these builds increases as we get closer to the final version.
Nightly builds allow customers and partners to experience new features early in development, which can be useful for planning deployments or integrating OpenShift with developers' own ISV solutions.
Note to OKD Community Members
Work has begun on OKD 4.0, an open source Kubernetes distribution built by the development community that underpins Red Hat OpenShift. We invite everyone to give their assessment of the current state , Fedora CoreOS (FCOS) and Kubernetes as part of the OKD Working Group or follow the progress on the website .
Note:
The word "partnership" in this publication does not mean a legal partnership or any other form of legal relationship between Red Hat, Inc. and any other legal entity.
Source: habr.com