Orchestrating and Deploying Containers
Orchestrating and Deploying Containers
The most important elements of orchestrating and deploying containers are security and configuration.
Join the DZone community and get the full member experience.Join For Free
Learn how to migrate and modernize stateless applications and run them in a Kubernetes cluster.
To understand the current and future state of containers, we gathered insights from 33 IT executives who are actively using containers. We asked, "What are the most important elements to orchestrating and deploying containers?"
Here's what they told us:
- Orchestration of Containers:
- Configuration Management – Inserting state information into a container for a customer;
- Scaling – Ability to handle high volumes of load and extreme robustness during peak hours/times.
- Deployment of Containers:
- Delivery – It should be highly available so using a centralized registry is the better choice;
- Management – What is running on containers? How many containers are running? How many resources are being used?
- Cost – Ability to easily spin off multiple containers in an environment can significantly reduce the operating cost of the company. People using containers want access to storage in containers. Flaws that existed are still out there. People need to understand how to layer containers following best practices. Storage plugs into containers easily.
- Enable containers to learn persistent workloads for large distributed data centers. Easy to spin up and take down and scale based on your application. Provide one big scalable storage cluster. Create multiple virtual disks and manage the data within. Some clients just getting started with a container with 15 to 100s of TBs of data. Now use for stateful applications.
- Microservices SQL and .Net into a containerized React NoSQL. For containers, we move to a containerized environment to be more robust, save money in the long run. Self-documenting with Docker files. Simplifies the deployment process. Super easy to organize.
- Everyone is doing something with containers. The momentum has picked up in the last 12 months. Typically, K8s is the winner in what people are using. Docker is central but the avenue of access is dominated by K8s. Mesos Containerizer is still there and very large container operations tend to use Mesos rather than K8s. Microsoft is the on-premise hybrid approach that’s available now too. Run on-prem and in the cloud. K8s is the language everyone is speaking in using OpenShift and GCS.
- The most important element is operationalization. It is a recipe for disaster to adopt a container platform in a vacuum within a single engineering team or worse, a single individual. For both success and business value to be possible, the solutions implemented should be clearly documented and augmented with service management principles. Teams should be on-boarded such that they understand the process to implement, scale, troubleshoot, and even locate running applications, particularly during service impacting events.
- We lead with open source given our portfolio and how we go to market. It's a bigger transition modernizing how applications are delivered. Moving away from a traditional ITIL model of self-service to a DevOps, CD model. Getting agility that enables self-service. Create a CI/CD pipeline for developers to pump in code on one side, go through a unified pipeline, and as part of that what gets baked is a container that’s dropped into a registry whether its Cloud registry or Antifactory or something else and it becomes the convenient unit to drop into your platform, K8s, Nomad, Stargate, or UCS. Don’t lose the forest for the trees. Sometimes that happens with containers. You are going through a process shift and containers are just a piece of the puzzle.
- Containers address multiple use cases on the sliding spectrum of virtualization. 1) Process containers, such as OCI compliant containers, require careful scheduling, provisioning, and orchestration, as well as ongoing coordination to address use cases, such as micro-service based cloud-native application development and operations. K8s stands out as the clear winner in the open source ecosystem as a way to achieve standard operational paradigms regarding OCI container orchestration. 2) Machine containers resemble virtual machines in their behavior, but without the overhead of full virtualization. LXC containers using the LXD hypervisor can be managed locally or within an LXD cluster, which is natively included. 3) Snap application containers deliver secure, over the air updates and device management to address the challenge of immutability, verifiability, and authenticity of the contained application. 4) Independent of the container format and use case, varying levels of isolation carry varying levels of security and external protection requirements, for example through namespace isolation, mandatory access control (MAC) through AppArmor, and other system-level security protections.
- The most important elements are auto-scaling, high availability and rolling upgrade. These aspects are real benefits.
Here’s who we spoke to:
- Tim Curless, Solutions Principal, AHEAD
- Gadi Naor, CTO and Co-founder, Alcide
- Carmine Rimi, Product Manager, Canonical
- Sanjay Challa, Director of Product Management, Datical
- OJ Ngo, CTO, DH2i
- Shiv Ramji, V.P. Product, DigitalOcean
- Antony Edwards, COO, Eggplant
- Anders Wallgren, CTO, Electric Cloud
- Armon Dadgar, Founder and CTO, HashiCorp
- Gaurav Yadav, Founding Engineer Product Manager, Hedvig
- Ben Bromhead, Chief Technology Officer, Instaclustr
- Jim Scott, Director, Enterprise Architecture, MapR
- Vesna Soraic, Senior Product Marketing Manager, ITOM, Micro Focus
- Fei Huang, CEO, NeuVector
- Ryan Duguid, Chief Evangelist, Nintex
- Ariff Kassam, VP of Products and Joe Leslie, Senior Product Manager, NuoDB
- Bich Le, Chief Architect, Platform9
- Anand Shah, Software Development Manager, Provenir
- Sheng Liang, Co-founder and CEO, and Shannon Williams, Co-founder, Rancher Labs
- Scott McCarty, Principal Product Manager - Containers, Red Hat
- Dave Blakey, CEO, Snapt
- Keith Kuchler, V.P. Engineering, SolarWinds
- Edmond Cullen, Practice Principal Architect, SPR
- Ali Golshan, CTO, StackRox
- Karthik Ramasamy, Co-Founder, Streamlio
- Loris Degioanni, CTO, Sysdig
- Todd Morneau, Director of Product Management, Threat Stack
- Rob Lalonde, VP and GM of Cloud, Univa
- Vincent Lussenburg, Director of DevOps Strategy; Andreas Prins, Vice President of Product Development; and Vincent Partington, Vice President Cloud Native Technology, XebiaLabs
Opinions expressed by DZone contributors are their own.