Managed Kubernetes, for those who really need it.
We keep the cluster running and up to date. Your team only needs to know what has to run on it.
Short answer
Kubernetes is open source software that spreads containers across several servers, restarts them when they fail and rolls out new versions without interruption. Managed Kubernetes means the host runs the cluster itself. Jevana runs Kubernetes clusters on its own hardware in the Netherlands and keeps them updated. It is meant for development teams that already work with containers, not for a single website.
Do you need Kubernetes
| Situation | What fits |
|---|---|
| One application with a database | A managed server with containers. Kubernetes only adds work here |
| A handful of services that work together | Either will do. It depends on how often you deploy |
| Many small services, several teams, deploying daily | Kubernetes |
| Software from a supplier that requires Kubernetes | Kubernetes |
| The team wants to learn it | A test cluster, apart from production |
What we manage and what your team does
Us
- The cluster itself, and the servers underneath
- Updates to new Kubernetes versions, planned in
- Storage, network and the traffic coming in
- Backup of the configuration and of the data
- Monitoring of the cluster
Your team
- The containers and their settings
- When a new version goes live
- Who in the team may do what
- The application itself, and the faults in it
Honest about the limits
Kubernetes promises that a service keeps running when a server fails. That only holds if the cluster is spread over several physical machines. How that is set up for your environment belongs in the proposal, in plain words.
There are two of us, and we do not build a cluster for thousands of containers across three continents. What we do build is a clear cluster for a company with its own software, in the Netherlands, kept up by people you can reach.
Questions
What is Kubernetes?
Kubernetes is an open source platform that manages containers on a group of servers. You describe which services must run and in how many copies, and Kubernetes keeps it that way: it starts containers, spreads them, replaces what fails and rolls out new versions step by step. It was originally developed at Google and is now run by an independent foundation.
When do you not need Kubernetes?
You do not need Kubernetes for a website, an online shop or a single application with a database. There a managed server with a few containers is simpler, cheaper and easier to understand for whoever comes after you. Kubernetes pays off with many separate services, several teams or software that requires it. We advise against it when it does not fit.
What does managed mean with Kubernetes?
Managed means we run the cluster itself: the installation, the updates to new versions, the storage, the network, the certificates and the monitoring. Your team gets access to deploy services and does not have to deal with what lies underneath. Kubernetes releases a new version a few times a year, and old versions run out of support fast.
Can we leave later with our cluster?
Yes. Kubernetes is an open standard: the descriptions of your services work on any cluster that follows it, with us, at another host or in a public cloud. We use no proprietary additions that tie you in. Data in databases and storage goes with you through an export or a backup.
Goes well with
-
Managed hosting
Your own application hosted and managed: server, database, deployment and monitoring, on our hardware.
-
Forgejo Actions and runners
CI/CD next to your code: builds and tests on runners that run on our hardware.
-
Private cloud
A sealed-off environment of your own, with virtual servers and a network, on our hardware.
-
GitLab hosting
Your own GitLab on our hardware, for teams that want to stay with GitLab but not with its cloud.
Tell us what you run.
An introduction costs nothing. You talk straight away to one of the two people who will actually do the work.
or email info@jevana.systems