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

Gartner estimates that 75 per cent of organizations will be running containerized applications in production by 2022. There is no doubt that Kubernetes has become a popular way to organize containers. By following some Kubernetes best practices, you can ensure that their adoption does accelerate container deployment.

Below we extract the findings from Gartner's "Best practices for running containers and Kubernetes in production" report. The report notes that common problems related to security, automation, teamwork, and tool selection were found when running Kubernetes in production.

With regard to remediation, Gartner's best practices cover governance policies, defining use cases, leveraging container as a service (CaaS) or platform as a service (PaaS) platforms, and techniques for acquiring CI/ CD tools. Let's review these areas to see how the infrastructure and operations teams can make the most of containers and Kubernetes.

"companies often underestimate the amount of work required to operate containers in production," Gartner said. " Is your business ready to transfer containerized workloads to production? Container and Kubernetes have a steep learning curve, combining it with the relative technological immaturity of space and the lack of talent in the field, and this real-world problem will begin to emerge.

Gartner reminds the team to carefully consider whether they have the necessary roles and skills within them before adopting new technologies. This involves the enterprise building an appropriate DevOps team and considering how Kubernetes integrates with the rest of the enterprise infrastructure. On the technical side, this means determining the runtime and orchestration engine, and carefully selecting containerized workloads. Not to mention, the ROI of the enterprise should be tabulated in advance.

Common mistakes in this early stage include adopting complex workloads with large dependencies, quickly falling into vendor lock-in, and deploying containerization tools without establishing DevOps conventions. According to Gartner, the adoption of containers and Kubernetes requires the entire organization to be consistent, train and remember the needs of developers. Failure to understand these early realities can lead to some very serious consequences.

Here are some practical tips on six container platform strategies summarized by Gartner:

1. Adoption and application of DevSecOps

Gartner pointed out in the report: "Security is not an afterthought." "it needs to be embedded in the DevOps process." As we have said before, use DevSecOps to inculcate a company-wide safety culture and embrace security automation.

For Gartner, DevSecOps can be partially accomplished by applying image scanning in the CI/CD pipeline, and many open source tools (such as Anchore) can be used to audit Docker containers to automate the threat discovery process.

Security leaders should also follow CIS benchmarks, ensure proper access control and use third-party encryption services to protect sensitive information and credentials.

two。 Fine-grained monitoring

According to Gartner, traditional host-centric monitoring (such as CPU utilization, latency, network bandwidth, etc.) is simply not enough. DevOps must enter the functional monitoring of the container itself more finely.

When selecting a monitoring tool, the report recommends a real-time solution that reflects service-level applications, integrates it more deeply with Kubernetes's container coordinator, and provides fine logging with actionable output.

3. Reevaluate data persistence

Recently, the trend is towards stateful workloads on containers. If the application is redesigned, this may also affect the data stored procedure. For example, according to the Gartner-oriented report, for microservice-oriented stateful applications, "infrastructure and operations leaders need a storage platform that maximizes the availability, agility, and performance of the workload."

4. Optimize the network for K8s

Developers need to test portability from the development environment to the production style. Newer development paradigms must span both local and public clouds, and container networks often have to span multiple layers.

In this world, the network process must adapt. According to the Gartner report, "Network solutions need to be tightly integrated with Kubernetes's primitives and policy engines."

Gartner recommends that companies review their CaaS or software-defined network (SDN) tools to see if they support load balancing between Kubernetes networks and hosts in the cluster. Network is a bright spot of service grid technology, so it is also a choice.

5. Manage the container lifecycle

In order to speed up the application delivery process, automation tools are king. Gartner recommends that companies consider using infrastructure code (IaC) products for application release automation and tools for container lifecycle management. These will help set standards for the container base image and help automate the application workflow.

6. Correct arrangement

Finally, container choreography has its own set of best practices. Although Kubernetes has become a de facto container orchestration tool, there are still subtle differences in distribution methods. When comparing orchestration approaches, Gartner advises companies to consider factors, including scalability, operating system support, runtime stability, open source, and support for hybrid and multi-cloud.

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.