General Kubernetes

What is Kubernetes? The Engine of the Digital World, Simply Explained

22. Jul 2025

1. For the Curious but Non-Technical – What Are Containers, and What Is Kubernetes?

Imagine Switzerland’s world-famous logistics system: trains, trucks, planes, and, well, not too many ships – all reliably moving goods through mountains, valleys, cities, and across borders.

Now picture a few freight trains: each wagon is loaded with a container, and each container holds a specific product – cheese from Gruyères, watches from Biel, or chocolate from Bern.

In the digital world, software containers work the same way. Each container carries a specific application or service, along with everything it needs to run – the code, settings, and dependencies – so it can be moved and operated anywhere, whether that’s a laptop, a data center, or the cloud.

But what if you had hundreds or thousands of these containers running at once – all needing to be loaded, routed, monitored, restarted if they fail, and scaled up when demand grows?

That’s where Kubernetes comes in.

Just like a logistics control center coordinates trains, planes, and trucks across Switzerland and beyond, Kubernetes coordinates software containers. It decides where they should run, makes sure they’re healthy, scales them up and down, and restarts them if something goes wrong – all automatically.

Originally developed by Google, Kubernetes was inspired by the company’s internal system “Borg” and released as open source in 2014. Today, it’s maintained by the Cloud Native Computing Foundation and backed by a global community.

And even if you’ve never heard of Kubernetes before, it’s likely already part of your life. From online banking to e-commerce shops to streaming services – many of the apps you use every day are running on Kubernetes behind the scenes.

Just one example:

In short:

  • A container is a standardized software package that runs anywhere
  • Kubernetes is the smart system that operates thousands of containers efficiently

Without Kubernetes, companies would have to manage each container manually – like sending cargo across Switzerland without signals, schedules, or a central control tower.

A few ideas on how to explain Kubernetes in one sentence: 😊

2. A bit more technical – What Kubernetes actually does

Modern applications are no longer monolithic – they’re modular, cloud-native, and increasingly built around DevOps workflows. Instead of installing software directly on static servers, teams now package their applications into containers – lightweight, isolated units that include everything an app needs to run.

Now imagine you’re running:

  • 50 services
  • 500 containers
  • Across multiple environments (development, testing, production)
  • In a mix of public cloud, private servers, and edge locations

Managing that manually is not just difficult – it’s nearly impossible. That’s where Kubernetes comes in.

Kubernetes solves problems like:

  • Automatically starting and stopping containers based on real-time demand.
  • Restarting containers when something goes wrong.
  • Ensuring services are available and responsive.
  • Rolling out updates without downtime.
  • Distributing workloads to avoid overloading servers.

Real-world examples:

  • In retail: online shops use Kubernetes to handle traffic spikes, such as those on Black Friday. Kubernetes scales up – and then back down again to save costs.
  • In finance: Banks use Kubernetes to run apps that need high security and zero downtime, while continuously deploying new features.
  • In healthcare: Patient data platforms use Kubernetes to ensure compliance, redundancy, and secure access.
  • In SaaS: Tech companies use Kubernetes to ship updates faster, run multiple versions in parallel, and reduce infrastructure overhead.

Without Kubernetes, teams would still rely on scripts and manual steps to deploy and maintain software – slowing down innovation and increasing the risk of failure.

3. For the Tech-Curious – Clusters, Distributions, and What VSHN Does

What is a Kubernetes Cluster?

A single Kubernetes system is called a cluster. It includes:

  • Control plane: the brains of the operation, deciding what should run where.
  • Worker nodes: the servers where containers actually run.
  • Services and tools to keep things secure, observable, and resilient.

You can have a small cluster on your laptop or a massive multi-cluster setup across global data centers.

What is a Kubernetes Distribution?

Kubernetes is open source, but it comes in different versions called distributions – similar to how Linux has different flavors like Ubuntu or Red Hat. These are tailored variants of Kubernetes with added features, support, or integration.

Example Kubernetes distributions include:

  • Vanilla Kubernetes – the plain open source version.
  • Red Hat OpenShift – adds developer tools, hardened security, and enterprise support.
  • Rancher – focuses on multi-cluster and edge use cases.
  • EKS, AKS, GKE – managed Kubernetes services by AWS, Azure, and Google.

Each distribution serves different needs. Some focus on governance and compliance, others on developer experience or cost efficiency.

What VSHN Does with Kubernetes

At VSHN, Kubernetes is the backbone of everything we do.

We were the first Swiss Kubernetes Certified Service Provider (KCSP) and the first Swiss Red Hat Premier Certified CCSP Partner – official recognitions of our deep expertise and long-standing commitment to the Kubernetes ecosystem.

VSHN manages hundreds of Kubernetes clusters for customers of all sizes – from startups to banks and public institutions – running in public cloud, private cloud, on-premises, or Swiss or EU sovereign clouds like Exoscale, Cloudscale or IONOS.

We offer:

  • Managed OpenShift – We set up and operate your OpenShift cluster and take care of its entire lifecycle: security, monitoring, upgrades, and backups.
  • APPUiO – Expert hosting for expert software engineers. Our OpenShift Project-as-a-Service offering, ideal for getting started with Kubernetes at low cost. Try APPUiO for free at appuio.cloud/register with the code: K8s2025
  • Servala – Open Cloud Native Service Hub – Our newest platform lets you deploy fully managed services – like databases, developer tools, and monitoring – in just a few clicks, all powered by Kubernetes.

Over the years, we’ve developed automation frameworks, monitoring tools, and proven best practices to help our customers focus on building software – not managing infrastructure.

Out of this experience, we’ve also launched two Open Source projects:

  • K8up – A Kubernetes backup operator and CNCF Sandbox project.
  • Project Syn – A modular, secure toolbox to manage fleets of Kubernetes clusters.

Where do Red Hat, OpenShift, and VSHN fit in the railway analogy?

Let’s stay with our Swiss railway analogy.

  • Kubernetes is the Swiss railway infrastructure – tracks, switches, schedules, and the control center. It ensures all trains (containers) run safely and efficiently.
  • Red Hat OpenShift is the premium freight rail operator – it adds polished locomotives, cargo workflows, and integrated safety systems to the tracks.
  • VSHN is your logistics partner and train operator – we run and maintain the network, the trains, and even the cargo. We make sure everything is on time, scalable, and secure.

Even better: with our Solutions, we don’t just operate the trains – we help you load, monitor, and optimize the containers inside.

And Servala? Think of it as the logistics warehouse next to the railway yard – a place where you can grab pre-packed cargo (managed services) and deploy it directly onto your Kubernetes rail network with a few clicks.

In this picture:

  • Red Hat builds the system and provides the premium trains (OpenShift).
  • VSHN operates the system reliably for you (Managed OpenShift, VSHN Solutions).
  • You focus on your cargo (apps) – while we ensure everything runs like a Swiss clock.

Why You Should Care – Even If You’re Not a Dev

Kubernetes is behind many of the services you use every day:

  • Online banking
  • E-commerce shops
  • Streaming services
  • Public digital services

Kubernetes is also a key technology for teams adopting DevOps – helping developers and operations work together more efficiently through automation, self-service infrastructure, and repeatable workflows.

For businesses, Kubernetes enables:

  • Faster time to market – deploy features daily, not quarterly.
  • Higher reliability – systems recover automatically from failure.
  • Cost optimization – only use the resources you need, when you need them.
  • Vendor flexibility – avoid cloud lock-in by running your workloads anywhere.

TL;DR

In 2025, Kubernetes is no longer a luxury – it’s the foundation of modern IT. Not just for tech giants – but for any team that wants to work faster and better. Kubernetes automates the deployment, scaling, and reliable operation of modern applications – in the cloud, on-premises, or in hybrid environments.

At VSHN, we make Kubernetes simple, reliable, and accessible – so you can build great digital products.

Further Reading

Curious how Kubernetes can help your team? Get in touch with us – we’d love to show you.

Disclaimer: This text was partially written by a human.

Markus Speth

Marketing, Communications, People

Contact us

Our team of experts is available for you. In case of emergency also 24/7.

Contact us
Kubernetes Tech

Stay Ahead of the Game with Kubernetes

13. Jan 2023

Kubernetes is a powerful platform for deploying and managing containerized applications at scale, and it has become increasingly popular in Switzerland in recent years.

One way to approach it is outsourcing. This can be a strategic and cost-effective option for organizations that do not have the in-house DevOps expertise, know-how, or resources to manage their infrastructure and application operations efficiently.

Not every tech company is in the business of building platforms and operating Kubernetes clusters. Thus by partnering with an experienced partner, companies can tap into a wealth of knowledge and expertise to help them run their applications.

Some companies adopt Kubernetes and look to leverage its capabilities themselves. It’s essential to consider time, effort, and possible implications while utilizing the latest developments and continually adding value to the core business.

In all cases, it will be helpful to align with fundamentals. For this reason, I have compiled a quick guide to Kubernetes in 2023 and best practices in Switzerland.

  1. Understand the basics: Before diving into Kubernetes, have a solid understanding of the reasoning and concepts. This could include cloud infrastructure, networking, containers, how they liaise with each other, and how they can be managed with Kubernetes.
  2. Plan your deployment carefully: When deploying applications with Kubernetes, you must plan thoroughly and consider your workloads’ specific needs and requirements. This includes but is not limited to resource requirements, network connectivity, scalability, latency, and security considerations.
  3. Use appropriate resource limits: One of the critical benefits of Kubernetes is its ability to manage resources dynamically based on the needs of your applications. To take advantage of this, try to set appropriate resource limits for your application. This will help ensure that your application has the resources they need to run effectively while preventing them from consuming too many resources and impacting other applications.
  4. Monitor your application: It’s essential to monitor your applications and the underlying Kubernetes cluster to ensure they are running smoothly and to identify any issues that may arise. You want to analyze the alerts and react accordingly. You can use several tools and practices to monitor your applications, including log analysis, monitoring with tools like Prometheus and Grafana, and alerting systems.
  5. Use appropriate networking configurations: Networking is critical to any Kubernetes deployment, and choosing the proper network configuration is substantial. What about load balancing, service discovery, and network segmentation?
  6. Secure your application: Security is a top concern for many companies and organizations in Switzerland. You cannot proceed without ensuring that your Kubernetes deployment is secure. At this stage, your team is implementing network segmentation, using secure container runtime environments, and implementing advanced authentication and authorization systems.
  7. Consider using a managed Kubernetes service: For companies without the resources or needing DevOps expertise to manage their clusters, managed Kubernetes services can be a business-saving solution. With managed services, you can get a production-ready cluster, i.e., a fully-managed Kubernetes environment, allowing teams and software engineers to focus on developing new features and deploying their applications rather than managing the underlying infrastructure.
  8. Stay up-to-date with the latest developments: The Kubernetes ecosystem is constantly evolving, and it’s better to stay up-to-date with the latest developments and best practices. This may involve subscribing to newsletters like VSHN, VSHN.timer, or Digests, attending conferences and CNCF meetups, and following key players in the Kubernetes community.

By following best practices, IT leaders, stakeholders, and decision-makers can ensure that they use Kubernetes constructively and get the most out of the platform technology.

Aarno Aukia

Aarno is Co-Founder of VSHN AG and provides technical enthusiasm as a Service as CTO.

Contact us

Our team of experts is available for you. In case of emergency also 24/7.

Contact us
Kubernetes Tech

What is a Kubernetes distribution and what are the differences between Kubernetes and OpenShift?

30. Aug 2018

At VSHN and APPUiO.ch we rely on OpenShift as Kubernetes distribution. What a Kubernetes distribution is, why we use it and where the differences to ‘plain’ Kubernetes will be explained in this blog post.

What is Kubernetes?

The official description of Kubernetes is:

Kubernetes is a portable, extensible open-source platform for managing containerized workloads and services, that facilitates both declarative configuration and automation.

The most important part of this description is the fact that Kubernetes is a platform and not a ready off-the-shelf product. This is an important piece of information for understanding this article.

What is a Kubernetes distribution?

To understand the differences between Kubernetes and OpenShift, first of all we have to clarify the term ‘Kubernetes distribution’: if Kubernetes is installed directly from the open source Kubernetes project, you ‘only’ get the core components (API server, controller manager, scheduler, Kubelet, kube-proxy). In order for Kubernetes to be really usable, you need a lot of other components like etcd, ingress controller, logging server, metrics collector (for example Prometheus), software defined network (SDN) and many more. This is very similar to Linux: the Linux kernel alone does not help much, you need a whole Linux distribution which provides a shell, package management, boot process and much more.

OpenShift is a Kubernetes distribution and makes Kubernetes a product

A ‘minimum viable Kubernetes distribution’ requires the following additional components and tools for productive operation:

  • Installation and upgrade mechanism: for an automated installation of all involved components.
  • SDN (software defined network): pods must be able to communicate with each other no matter where they are running. The SDN ensures that.
  • Ingress controller: to allow user access to applications running on the cluster.
  • Authentication: a central user and group database provides the authenticated and authorized access.
  • Security: Kubernetes executes containers via Docker or CRI-O. The security on the host system must be ensured accordingly.
  • Persistent storage: stateful applications such as databases require persistent storage.
  • Monitoring: constant monitoring of all cluster components and applications.
  • Backup: backup of cluster components and persistent data.

Optionally, further components are recommended:

  • Central logging with graphics and searchability
  • Application and cluster metrics including alerting

OpenShift as Kubernetes distribution

Essentially, OpenShift relies 100% on Kubernetes, but as a Kubernetes distribution, it comes with everything needed for a Kubernetes cluster. To name just the most important functions:

  • Operations tools: an official and supported way via Ansible allows the entire lifecycle of OpenShift to be executed. This includes the automated installation, as well as upgrades to newer versions of OpenShift.
  • Router: the OpenShift router (ingress controller) – based on HAProxy – ensures that access to applications within the cluster is made possible via HTTP(S).
  • Multi-tenancy: multi-tenancy is built-in the core on OpenShift projects, RBAC and other concepts to allow the use of the platform by various stakeholders.
  • Authentication: the most different authentication backends are supported, above all LDAP, Active Directory (AD) and others.
  • Metrics: the bundled metrics component collects all available data (RAM, CPU, network) of the applications running on the cluster and visualizes them in the web console.
  • Central logging: all lines logged by the application on stdout are automatically collected by the central logging component and are made available to the user via the web console.
  • Security: the platform is designed for maximum security. For example, security measures in the kernel of Red Hat Enterprise Linux like SELinux ensure that the security of the containers is guaranteed. Further measures such as ‘security context constraints’ (SCC) and the prevention of root containers ensure further security.
  • Builds and pipelines: directly in the cluster integrated build and pipeline capabilities enable a fully integrated CI / CD workflow.
  • Web console: all operations on the cluster are visually displayed to the user of the platform in a web console and allow an easy and quick access to the use of Kubernetes.
  • SDN: the included software defined networking provides connectivity between the pods running on the platform and for an adequate network security with network policies.
  • Container registry: Docker / container images are stored in the bundled registry and used for deployment onto the worker nodes.

All these built-in functionalities can be added to any Kubernetes cluster, but only with a lot of effort. Comparable to building your own Linux distribution, as for example  Linux From Scratch demonstrates. Kubernetes has a similar guide called Kubernetes The Hard Way.

OpenShift as PaaS

The strength of Kubernetes lies in the container orchestration. In addition, OpenShift offers classic Platform-as-a-Service (PaaS) functionalities. One of these is the automatic building and deployment of application code directly from a Git repository. Nevertheless, as a user of the platform and thanks to its great flexibility, you always have the choice of whether you want to use the integrated build functions, or rather build outside the cluster. This can be chosen for each deployment, so both types can be used on one cluster.

OpenShift as upstream to Kubernetes

Many developments in Kubernetes originally came from OpenShift. The best example is RBAC (role based access control). This feature has been part of OpenShift since the first release and has been gradually integrated into Kubernetes. RBAC has been an integral part of Kubernetes since Kubernetes version 1.6. The OpenShift ‘Route’ or the ‘DeploymentConfiguration’ object also played a key role in the current objects ‘Ingress’ and ‘Deployment’ in Kubernetes.
Since OpenShift is 100% based on Kubernetes, all Kubernetes native workloads are also supported, such as the ‘Deployment’ or the ‘Ingress’ object.
If you look more closely at the contributor statistics, you’ll find that Red Hat is one of the top 3 contributor companies, so Red Hat is crucial in the development of Kubernetes. With the purchase of the company CoreOS, Red Hat has acquired formidable Kubernetes know-how. The merger of OpenShift and Tectonic will be the next milestone of the Kubernetes distribution OpenShift.

Alternatives to OpenShift

OpenShift is not the only Kubernetes distribution on the market. A quick comparison shows the differences:

  • Cloud vendor Kubernetes: the big clouds offer their own Kubernetes distributions as a service. These are tailored to the respective cloud and are maintained by the providers. Installation on your own private cloud or on other public clouds is not possible.
  • Rancher: since version 2.0, Rancher focuses 100% on Kubernetes and offers a multi-cluster management function as a major strength. With Rancher, Kubernetes clusters in the cloud (for example, on Amazon or Google) can be managed centrally, as well as Kubernetes clusters with the ‘Rancher Kubernetes Engine’ on your own VMs. With the web interface, setting up a new cluster is very easy and application deployments using Helm are also directly available.
  • Tectonic: this distribution lies great importance on cloud-native automation. Through Red Hat’s acquisition of CoreOS, Tectonic will be merged with OpenShift and many of its features will inserted into OpenShift.
  • Canonical / Ubuntu Kubernetes: platform based on Ubuntu, which uses Juju as installation tool. In partnership with Google and Rancher, a hybrid cloud solution will be offered in the future.
  • SUSE CaaS platform: a very new platform based on SUSE MicroOS. Salt is used to ensure configuration management. Under the following link you can participate in the beta program: SUSE CaaS Platform Beta.

Further Kubernetes distributions include:

One very important aspect to consider is the cloud and / or vendor lock-in. Many of the Kubernetes distributions have their own characteristics, which may not be compatible with each other. Using the example of ‘cloud vendor’ distributions: these can only be used in the corresponding cloud. However, if you want to pursue a hybrid cloud approach, this is not possible due to the lock-in. In contrary, a self-installable distribution like OpenShift makes this option possible.
Pure open source distributions without manufacturer support are not recommended for productive environments, as this is of great advantage for a complex platform like Kubernetes.

APPUiO – Swiss Container Platform

The attentive reader may have noticed that there are some discrepancies between the ‘minimum viable Kubernetes distribution’ and OpenShift. This is exactly where APPUiO comes in: we refine OpenShift into a comprehensive, production-ready Kubernetes distribution by offering managed services. We automatically monitor and secure the cluster status, take care of regular updates, fix bugs, provide persistent storage and help with our know-how to make the most out of the platform.

More information about Kubernetes and OpenShift

At the Cloud Native Meetup on August 28, 2018 in Zurich, we also talked about Kubernetes distributions: you can find the slides on Speaker Deck. You can also find more about OpenShift, Docker and Kubernetes here. Another recommendable blog post on this topic by Tomasz Cholewa: 10 most important differences between OpenShift and Kubernetes (English, technical).

How can we help?

Through our experience in operating OpenShift clusters around the world, we offer managed OpenShift clusters on almost any public, private or on-premise cloud. Or are you interested in another Kubernetes distribution than OpenShift? We gladly help you with the evaluation, integration and operation and support with our many years of Kubernetes experience.
Contact us, follow us on Twitter or take a look on our services.
We are looking forward to your feedback! 

Tobias Brunner

Tobias Brunner is working since over 20 years in IT and more than 15 years with Internet technology. New technology has to be tried and written about.

Contact us

Our team of experts is available for you. In case of emergency also 24/7.

Contact us