Orchestrating and Deploying Containers

To gather insights on the current and future state of containers, we talked to executives from 26 companies. We asked, "What are the most important elements of orchestrating and deploying containers?" Here's what they told us:

Security

• Security, monitoring, and management are frequently cited by enterprise architects as the top elements for container orchestration. On a container platform, there are 4 major elements that container orchestration must address: networking, storage, security, and management. With today’s fast-growing ecosystem, all these elements have pretty solid solutions available and each is rapidly evolving. Keeping up with new orchestration functions is an additional important element to consider. 
• 1) Focus on open standards. Look to the CNCF and K8s container standards. Able to run on-premises and take to the cloud. K8ss provides mobility and agility when to run your workload, avoid vendor lock-in. 2) Focus on the developer experience. Build, deploy, operate container applications. An integration platform is important. The container provides a common factor with which to connect the DevOps cycle. 3) Differentiate by looking underneath at performance, security, enterprise-grade infrastructure, and scalability. 
• Extension of how to improve the quality of software by breaking into smaller pieces. Use containers to deliver. Protect images in registries. See issues in images and protect as build. See issues in images and protect as build. Add security to DevOps. 
• Need K8ss to take advantage of Docker. You still need a compliance and security platform. CNCF outlines the pathway to containerization. 1) Next generation microservices applications. 2) Containerization of legacy applications. Dev/test workloads, move to containers to save on infrastructure. Don’t rebase and rewrite. Take jar files and put in containers.

Hybrid Environments

• People tend to look at containers and management of containers. K8s is the defacto standard. Need to solve the data layer by using a fabric to support stateful containers. The ability to do this incrementally without having to prioritize the order. Be able to support container and non-containers. Ensure simple deployment. 
• It depends on the customer. For container leading customers like Silicon Valley start-ups we help with more advanced concepts around orchestration of K8s at scale in hybrid environments providing observation and monitoring. Lagging container customers, like financial services companies, want to move to K8s but 99% of their apps are running in a virtual machine (VM) and we’re looking at a five-year journey to move from VM to K8s, so you need to provide support for both. How to start taking stateless web apps from VM to K8s. 
• As software is eating the world, DevOps and containers are becoming more important. There are always new things in the works to simplify the use of containers. 1) Vendors need to be on top of technology, so their products will meet your needs and solve your problems. 2) Do not use public cloud, containers, and DevOps technologies in isolation. You need to have a holistic view into the hybrid cloud landscape.

Other

• The most important elements are the simplification of deployment scenarios. Container orchestration can be quite forgiving in regard to accepting incomplete or sub-optimal inputs, however, even small deviations can have negative operational impacts. The complexity of the Docker CLI (command line interfaces) lends itself to the introduction of human error through forgetting CLI strings, and there is no pre-validation of commands prior to execution.

  
  
  from DZone.com Feed https://ift.tt/2tXpfrR