Shulou(Shulou.com)06/01 Report--

This article will explain in detail what the new features of the Kubernetes1.4 version are, and the content of the article is of high quality, so the editor will share it for you as a reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

Main New Features of Kubernetes1.4

It takes only two commands to create a kubernetes cluster, enhanced support for stateful applications, increased cluster federation API support, container security control, enhanced Kubernetes infrastructure, including scheduling, and has been able to achieve 90% command line operations through Kubernetes DashBoard UI.

Two commands to create a cluster

In order to start Kubernetes, the user needs to provide a compute node, install Kubernetes, and start the cluster. Users crave an easy, portable way to deploy Kubernetes clusters on any cloud (public cloud, private cloud, or bare metal). To this end:

Kubernetes 1.4introduces the kubeadm command, which simplifies cluster startup to two commands, eliminating the need for complex kube-up scripts. Once Kubernetes is installed, kubeadm init starts the master node, and kubeadm join can merge the node into the cluster.

By streamlining the installation process, by packaging Kubernetes and its dependencies, users of major Linux distributions, including Ubuntu Xenial and Red Hat, can use familiar apt-get and yum to install Kubernetes.

Additional deployments, such as for an overlay network, use the daemonset approach to simplify the operation to a single command.

Simplifying this uses the new certified API, which uses kubelet TLS bootstrap, and the new API discovery.

Enhanced support for stateful applications

When cloud native applications are built and run in containers, more common stateful applications such as batch processing, databases, and KV storage require additional features to be compatible with containers. In Kubernetes 1.4, we introduced a number of features to simplify the deployment of these applications, including:

ScheduledJob alpha version, users can run batch tasks at regular intervals.

The Init-Container beta version, which emphasizes serialization dependencies before running one or more containers before starting the main container, such as starting a database or multi-tier application

Upgrade dynamic PVC to beta version. This feature allows cluster administrators to expose multiple storage providers and allows users to choose which storage provider to use through a new storage API.

Curated and Pretest Helm Charts, for common stateful applications such as MariaDB, MySQL, and Jenkins, Curated and Helm Charts can be used using a command from Helm Package Manager version 2.

Added Cluster Alliance API

What our users around the world want is to be able to build applications on divided regions and clouds, so we provide:

In the federated ReplicaSets Beta version, replica sets can now create replicas across regions and clouds in all or part of the cluster. The entire federated replica statistics and relative cluster weight / replica statistics are consistently maintained, and the federated ReplicaSet controller ensures that you have these Pods in each region / cloud.

The federated Services beta version, and secrets,events and namespaces are also added to the federated API.

The federated Ingress Alpha version, launched by GCP, allows users to create a global load balancer for L7 and deploy cross-cluster federated services in GCP through VIP load. Through GCP's federated Ingress, external clients are accessed through a separate IP address, and requests are sent to the nearest available cluster in the federation.

Support container security control

The administrator of a multi-tenant cluster needs to be able to provide a set of permissions between different tenants, infrastructure components, and end users of the system. Therefore, the following support is provided:

Pod security policy, a new object that enables cluster administrators to control the creation and validation of Pod/Containers security contexts, and administrators can combine service accounts,groups with users with some restrictions to define a security context.

AppArmor support has been added to enable administrators to run a more secure deployment, providing better auditing and system monitoring. Users can configure the container by setting a simple field in the AppArmor configuration file.

Enhance the Kubernetes infrastructure, including scheduling

We continue to add scheduler, storage, and client capabilities to Kubernetes-based users and biosphere. These include:

Scheduler, which introduces inter-pod affinity and anti-affinity Alpha versions, allows users to customize how Kubernetes combines or allocates Pods, as well as the priority scheduling capabilities of cluster add-ons, such as DNS, Heapster, and Kube Dashboard.

The Disruption SLOs,Pod interrupt budget is introduced to limit the impact of pod deleted by the cluster at any time, such as node upgrades.

Storage, a new volume plug-in, is added for Quobyte and Azure Data Disk.

Client: Swagger 2.0 supports adding and non-Go clients.

90% of command line operations can already be achieved through Kubernetes DashBoard UI.

Finally, a 90% matching Dashboard UI can provide easy management.

For a complete list of updates, we can see release note on Github. In addition to the deep impression brought by Kubernetes development, what is more important is the community contributor. Not only is it important for version 1.4, but it will be even more important in the future.

So much for sharing about the new features of the Kubernetes1.4 version. I hope the above content can be of some help to you and learn more. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.