White Papers

Enterprise Container Platform Buyer’s Guide

Issue link: https://read.uberflip.com/i/1344952

Contents of this Issue


Page 5 of 10

© 2020 Mirantis Inc. All Rights Reserved. Information is subject to change. | www.mirantis.com Enterprise Container Platform Buyer's Guide 6 environments need to be secure while being easy to operate, which starts at the foundation of secure container runtime and a standard set of APIs and tools� Finally, the platform needs to provide a highly scalable operator experience that integrates well with storage, networking, logging and monitoring tools and provides a management plane for ongoing operations. Critical components and capabilities Build • Desktop solution for local container development • Developer tools for integration into the software development pipeline • Support for: » a wide variety of application f rameworks, languages, and technology stacks » a wide variety of inf rastructures and operating systems • Ability to address the full spectrum of existing and new applications • Built-in security to ensure developers use safe, pre-approved starting points for application development Share • Secure image repository with access controls • Public and private library of images, including images provided directly f rom ISVs • Ability to distribute images to disperse teams and edge environments • Support for detecting vulnerabilities in container-based applications and automatically gating applications to prevent unsafe code f rom reaching production Run • Secure container runtime • Highly scalable management plane • Support for distributed hybrid and multi- cloud scenarios • Support for required application security models, such as Active Directory authentication for Windows applications Questionnaire for container platform evaluation The aforementioned requirements around modern application building, sharing and running should provide you with high level assessment criteria of container platforms� To further help you evaluate container platforms in detail, we have included a list of questions 2 below: Runtime and orchestration • Does the platform support open container format standards like OCI and Helm? Is it flexible enough to support emerging standards like CNAB? » What to avoid: proprietary formats that only work on one platform • Does the platform use the Docker Engine or containerd, which are used by all the major public clouds and the majority of container platforms? » What to avoid: container runtimes that are used only within a single vendor's product or are tied to a particular operating system. • Does the platform use upstream Kubernetes distribution? What differentiating container orchestration features are supported? Do they provide management features that can be used by experts and non- experts alike? » What to avoid: platforms that fork or modify Kubernetes for their platform, or provide non-standard interfaces that could limit your ability to run your applications elsewhere� • What differentiating container networking and storage features are provided?

Articles in this issue

Links on this page

view archives of White Papers - Enterprise Container Platform Buyer’s Guide