What a coincidence. I just wrote yesterday a tutorial how to use k3sup together with Kontena Lens (https://kontena.io/lens) to manage and monitor Kubernetes clusters: https://medium.com/@laurinevala/from-zero-to-kubernetes-dash...

Disclaimer would be welcomed that you are author at Kontena and working at the company selling this propriety tool.

Kontena Pharos (https://github.com/kontena/pharos-cluster) aims to make installation of Kubernetes as easy as possible. Works on any cloud or on-premises, also ARM64 supported.

It handles HA-setup, etcd member replacements, hardened configuration for enhanced security (follows NIST SP800-190 recommendations). You can easily extend the installation with addons of your own or from any Kubernetes ecosystem project

(Disclaimer: I'm one of the contributors)

Kontena, Inc. | https://www.kontena.io | New York & Helsinki | onsite and/or remote

Kontena is creating an open source, developer friendly container & microservices platform. If you'd like to spend your days tinkering with Docker containers and hacking bleeding edge microservice architectures for one of the most popular open source project in Linux container ecosystem, check our current open positions:

Developer Advocate (New York) - https://www.kontena.io/jobs/developer-advocate

Kontena Platform Developer (New York) - https://www.kontena.io/jobs/kontena-platform-developer

UI/UX Lead Developer (Helsinki) - https://www.kontena.io/jobs/ui-ux-lead-developer

Product Manager (Helsinki) - https://www.kontena.io/jobs/product-manager

Thanks for pointing that out. It's definitely outdated information and we will fix that.

Hi, I'm one of the co-founders of Kontena. Our target from day zero has been that you can start with small setup and scale up later if needed. So it's totally okay to run only one node with Kontena. Of course if you want to gain HA setup, minimum of 3 nodes is recommended.

This definitely sounds interesting. What would my job be after I manage to make the setup work: Backing up the database?

Yes, backing up the database is one thing. After the setup you can just concentrate on your applications. Btw we are introducing hosted version of the Kontena platform soon, which will make the setup even easier. If you are interested in that option, you can join waiting list already: https://www.kontena.io/invite

Mattermost seems to be a new Hello World of Docker examples. Just made yesterday an example how to deploy Mattermost to production with Kontena: https://github.com/kontena/examples/tree/master/mattermost

Totally agreed with this and that was also our vision when we started to create Kontena (https://github.com/kontena/kontena)

Kontena does not replace Docker. It's a management and orchestration layer on the top of Docker. With Kontena you can manage and deploy your Docker applications.

Kontena applications can be described in YAML file (kontena.yml). Kontena.yml extends docker-compose.yml format by introducing some new attributes only supported in Kontena, for example scale of a service and deploy specific attributes.

A Service definition describes the container image, networking, scaling and stateful/stateless attributes for your application. Services may be linked together to create desired architecture. Each service is automatically assigned with internal DNS address that can be used inside your application for inter-Service communications.

The summary of Kontena key features:

* Scheduler with affinity filtering

* Built-in private Docker image registry

* Remote VPN access for workload services

* Virtual Networking Built-In

* Ready made load-balancing service

* Log and statistics aggregation with streaming

* Access control and roles for Kontena users

I agree, some comparison is definitely needed. We will put some comparison not only to Deis and docker-compose but to other related services too to our website as soon as possible.

Yes it does. Additionally if your service has more than 1 instance then Kontena will replace each instance one-by-one when deploying. You can even define that Kontena will wait for given port before moving to next instance.

Oh wow, that's awesome. I'm sold :)

Thanks!

Edit: btw, you should probably advertise this more on the home page, I'm pretty sure zero downtime is a big no go for many when it comes to docker-compose, especially rails users used to it with unicorn.

That's true. There are still lot's of hidden features that we should mention somewhere. We are currently improving our documentation, so hopefully things are better soon.

And thanks for feedback, it is always appreciated and motivating us to make it better!