# Tech preview: Get your own Kubernetes container orchestration platform in cPouta

DevFeed: [Tech preview: Get your own Kubernetes container orchestration platform in cPouta](<https://devfeed.tech/articles/tech-preview-get-your-own-kubernetes-container-orchestration-platform-in-cpouta-19754.md>)

Original publisher: [Read original article](<https://cloud.blog.csc.fi/2017/08/tech-preview-get-your-own-kubernetes.html>)

Author: Unknown (noreply@blogger.com)

Published: 2017-08-18T11:26:00Z

Content type: release

Language: en

Sources: [CSC - IT Center For Science - Cloud Team](<https://devfeed.tech/sources/csc-it-center-for-science-cloud-team.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Orchestration](<https://devfeed.tech/topics/orchestration.md>), [container](<https://devfeed.tech/topics/container.md>), [Docker](<https://devfeed.tech/topics/docker.md>)

Tags: [commands](<https://devfeed.tech/tags/commands.md>), [container](<https://devfeed.tech/tags/container.md>), [cpouta](<https://devfeed.tech/tags/cpouta.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [new-feature](<https://devfeed.tech/tags/new-feature.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [preview](<https://devfeed.tech/tags/preview.md>)

## AI overview

This technology preview explains how users with cPouta access can launch a Kubernetes cluster using Magnum. It introduces container orchestration concepts and points readers to documentation describing the feature and its limitations.

## Source excerpt

Introduction You can now launch your own Kubernetes cluster in cPouta with just a few simple commands using a new tool called Magnum. If you already have access to cPouta, it should take about 10 minutes to get up and running. You can find documentation for this new feature in the container orchestration chapter of the Pouta user guide. This is a technology preview feature for now, so there are some limitations that you should be aware of. Those are listed at the end of the documentation page. Why use container orchestration? While Docker containers can be useful on their own, if all you have is a bunch of Linux machines with Docker installed you still have to do a lot of work yourself to make an application fault tolerant, to make it discoverable from the outside world, to make sure the containers stay healthy and to enable containers to communicate with each other. You also have to manage the Linux machines themselves by installing and configuring packages and doing other normal administrative tasks. Container orchestration engines do a lot of this work for you by providing common abstractions around replication, routing, storage and other aspects of running a containerized application. A container orchestration engine typically runs as a clustered application on multiple servers. The servers are separated into two categories: master nodes and slave nodes. The master nodes are responsible for receiving commands via an API and acting on these commands to start and manage containerized applications that run on the slave nodes. Fault tolerance can be achieved by running multiple copies of an application on multiple slave nodes and the COE provides abstractions that make this easy. If you are not already familiar with container orchestration platforms, I recommend looking through the excellent Awesome-Kubernetes list of curated links about the topic. There you will find many introductory articles on Kubernetes, links to various related projects and many other things.