Shulou(Shulou.com)05/31 Report--

Most people do not understand the knowledge points of this article "which Kubernetes can meet the needs of micro-services", so the editor summarizes the following contents, detailed content, clear steps, and has a certain reference value. I hope you can get something after reading this article. Let's take a look at this "Kubernetes can meet the needs of micro-services" article.

First, Kubernetes can meet the Maslow needs of micro-services.

This method of describing requirements is very important and has been used in many other areas, such as employee engagement, cloud computing, software development, DevOps, and so on. So the same applies to micro-services, where a clear list of requirements must be met for the success of micro-services. List is as follows:

Demand hierarchy of micro-services

Once the main issues of microservices are listed (there may be a different order for everyone), you will find that the Kubernetes container orchestration engine does a good job of covering a large portion of these requirements. I also added Kubernetes to the figure.

First, for the basic layer, some computing resources are required and, ideally, a scalable standard operating environment managed by the infrastructure service cloud provider. Other prerequisites are automated CI/CD processes and artifact registries, and Kubernetes can help us run and manage. We still need some specialized software, such as built Jenkins, and artifact repositories, such as on-demand Sonatype Nexus for Docker and Maven for Docker Hub.

Kubernetes can help manage multiple isolated environments (namespaces), manage resources (quotas and limits), storage allocation (persistent volumes), perform deployment and rollback (deployment), automatic scheduling (scheduling), service discovery and load balancing (services), resilience and fault tolerance (pod health check).

For some requirements, we need some additional tools, such as Docker or rkt for container implementation, and elastic libraries within the application (such as Netflix's Hystrix) combined with Kubernetes resiliency features. Kubernetes can then manage application configuration and help run the best centralized logging, metrics collection, and tracking software, which becomes important as the number of services increases.

According to the nature of micro-services, enterprises have some specific needs. For API-driven microservices, a specialized API management solution is required, and service security can also be handled (not provided by Kubernetes). But Kubernetes can easily help enterprises run stateful services (stateful settings), batch jobs (job), and scheduling jobs (cron job).

With all these features provided by one platform, users can perform smarter activities, such as automatic scaling and self-repairing of applications and infrastructure, through automatic placement, automatic restart, automatic replication, automatic scaling.

For all these requirements met by Kubernetes, all the team has left is to streamline the development process, embrace the DevOps culture to achieve rapid delivery, and achieve anti-vulnerability at the organizational level.

8 things you need to know about Kubernetes

This is a question-and-answer session between computer Weekly and Carlos Sanchez. Sanchez is an engineer at CloudBees and CloudBees is a provider of continuous delivery and integration software services. Jenkins, an open source continuous integration tool, is the focus of CloudBees services.

Computer Weekly's open source insiders (Computer Weekly Open Source Insider, CWOSI) asked eight questions most relevant to Kubernetes in an attempt to unravel the core of the issue, as Kubernetes experienced a big increase in popularity in 2017.

CWOSI # 1: for those who don't know Kubernetes, how do you summarize and define this technology?

Sanchez: Kubernetes is an open source platform designed to automate container deployment, scaling, and manipulation. It is a technology that allows containers to run on large clusters. It supports the execution of isolated applications across large data centers.

CWOSI # 2: why does Kubernetes appear in your point of view-why do we need it?

Sanchez: Docker did succeed in making containers. In fact, Google has been running billions of containers for many years. Kubernetes learned from Google's experience that containers run on this scale, leading Google to introduce the technology to the open source world, making it easier for others to manage containers.

As for why we need Kubernetes, this is because containers are becoming more and more important for large and small organizations, empowering development teams to run in large-scale distributed environments to deliver software faster in DevOps and continuous delivery practices. In this case, anything that can simplify the effective operation and management of containers will be warmly welcomed by enterprises.

CWOSI # 3:Kubernetes is open source in nature, but how many developers are contributing code to a technology that is infrastructure in nature?

Sanchez: overall, there are more than 1400 contributors. Google, Red Hat and Microsoft are all included. Recently, Amazon and Alibaba have become the biggest companies involved in the technology. CNCF manages the entire technology.

CWOSI # 4: does containerization ultimately mean that each individual component is more responsible for verifying its purpose and ultimately delivering specific outputs or functions?

Sanchez: containers are usually associated with a micro-service architecture. Each component expects to complete a specific protocol. These components have a purpose, and they have inputs and outputs marked by this protocol and API. They must be able to perform their duties. They should be independent and play a specific role in the architecture, where hundreds of services coexist.

CWOSI # 5: when you don't need Kubernetes … When enterprises do not need large-scale or across multiple machines?

Sanchez:Kubernetes is a complex system. If the enterprise has the scale to justify the deployment, then it makes sense to adopt this technology. For example, if you only use one or two virtual machines, or if there are no higher requirements, the enterprise may not need Kubernetes, and Docker will suffice on its own. In other words, the current cloud services offered by Google or Azure make it easy for us to start with Kubernetes and large-scale.

CWOSI # 6: can you explain Kubernetes pod to us?

A Sanchez:Kubernetes pod is actually a set of containers running on the same host. These containers have certain characteristics. For example, they share the same cyberspace and resources. A real Kubernetes pod is made up of containers that need to coexist.

CWOSI # 7: how easy is it to let Kubernetes go wrong and put the wrong implementations together?

Sanchez: this goes back to installation-- this is complex software that requires specialized expertise. That's why people use Google's Kubernetes engine or Azure container service.

In other words, there are more and more tools, whether open source or commercial, such as kops, kube-aws, or kubeadm, that can help with the correct installation. If you do not use one of the installers to simplify installation, you may make mistakes in the process.

CWOSI # 8: how do you think Kubernetes will develop in the next few years?

Sanchez: more and more Kubernetes products will enter the market from different vendors, not only cloud providers, but also operating system providers. Kubernetes will become the actual operating system of the cluster. In addition, Kubernetes will evolve into a standard API that allows enterprises to run the cluster architecture.

We see cloud providers destroying infrastructure so that enterprises can run Kubernetes without having to run servers. Therefore, we will see vendors providing Kubernetes as a service, and enterprises will be able to run containers in the cloud without having to worry about machines. AWS has announced its intention to provide this service, and this trend will continue to be implemented by other suppliers.

The above is the content of this article on "what needs can Kubernetes meet the needs of micro services". I believe we all have a certain understanding. I hope the content shared by the editor will be helpful to you. If you want to know more about the relevant knowledge, please follow the industry information channel.

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.