Your Kubernetes, secure, sovereign and managed by Flying Circus
The managed Kubernetes services on the Flying Circus cloud platform offer many advantages. Benefit from a comprehensively integrated and automatically controllable Kubernetes cluster that interacts seamlessly with other cloud-native solutions and is professionally managed around the clock.
Our Managed Kubernetes Service offers you unbeatable precision and performance when orchestrating container applications in distributed production environments. Take advantage of pre-integrated tool functions and benefit from professional expertise to optimise the use of this sophisticated infrastructure. Security, transparency and control during operation are guaranteed, while administrative tasks are minimised. With its focus on digital sovereignty, Flying Circus application operation is perfect for company projects that rely on Kubernetes and for which scalability and security are important. The solution offers numerous advantages, including:
Björn Langer
Let's talk about your project!
As your first technical contact, I am committed to understanding your individual requirements and developing tailor-made approaches for the successful operation of your application. Our exchange also enables us to determine an initial price indication for your individual project. I look forward to talking to you!
Contact options
Experience and expertise
With years of experience in numerous customer projects, we know the challenges and requirements of individual applications. We think outside the box and pass our findings and knowledge back to you in order to work in partnership with you to ensure the successful operation and sustainable further development of your application.
Consultancy and project support
We offer customised solutions that are perfectly tailored to your specific needs. Within Kubernetes, topics such as ‘persistent storage’ or individual requirements for database operations often pose a challenge. With our platform operation, we have created an environment in which individual application components can be operated outside the Kubernetes cluster but within the virtual private cloud of the customer project.
FAQ – Frequently asked questions about Managed Kubernetes K3s
Managed Kubernetes K3s is an optimal solution for a wide range of applications and projects. It is particularly well suited for:
- Teams with limited Kubernetes resources: K3s simplifies the complexity of Kubernetes and enables teams with little Kubernetes knowledge to leverage the benefits of container orchestration.
- Smaller to medium-sized projects: K3s is ideal for applications that do not require the enormous resources of a large K8S Kubernetes cluster.
- Edge computing setups: Thanks to its low software storage requirements and low resource consumption, K3s is perfect for use on edge devices such as POS systems, digital billboards or IoT devices. It even runs on Raspberry Pi's!
- Development teams that want to quickly create and roll out prototypes: The easy installation and configuration of applications in K3s speeds up the development process and enables faster time to market.
A K3s cluster is leaner and offers a number of advantages over larger K8s Kubernetes or K9s clusters. For one thing, it is significantly less complex, which makes it easier to learn and simplifies application operation. In addition, a K3s cluster simply requires fewer computing resources (CPU, RAM, storage), which reduces hardware costs and increases the efficient use of existing resources. The leaner setup also proves its worth in many lightweight edge computing setups (see below for more information). In short, you get many of the benefits of a large Kubernetes cluster without the high complexity and enormous resource requirements.
Yes! K3s users often express concerns because, in its simplest form, K3s uses SQLite as the database for cluster status. This is often cited as an argument against using it in production cloud environments. However, this is a common misunderstanding. While K3s can use SQLite as the database for cluster status in its most minimal configuration, this is not the case in our managed cloud environments in a cluster configuration, for example. We use an etcd cluster by default for our K3s clusters, which runs seamlessly with the control plane nodes. Alternatively, you can use an external etcd cluster or create dedicated etcd nodes for even more control and scalability.
A K3s cluster with an appropriate database configuration, such as PostgreSQL, is an excellent solution for small to medium-sized projects. K3s is leaner and simpler than traditional Kubernetes distributions, making it ideal for use in smaller teams. Using an external database further reduces the load on the K3s cluster and enables centralised data management. This is particularly advantageous if a database infrastructure already exists or if a central database is to be used for multiple applications.
Yes. K3s' light weight and low resource requirements make it an ideal solution for local edge setups such as point-of-sale systems, digital billboards, or other edge computing devices. Unlike traditional Kubernetes distributions, which would often be too resource-intensive on such systems, K3s can be easily installed and run on small hardware platforms or even Raspberry Pi's. This enables decentralised data processing and storage directly at the point of use, improving response times and reducing dependence on central servers.
We know that every organisation and every company has its own preferences and requirements. K3s offers the option to customise the standard configuration. During installation, some services such as Traefik are initially installed as ingress controllers. If you prefer other tools, we can disable services at any time and replace them with your own preferences. Thanks to the flexibility of K3s, you don't have to compromise on your preferences or reinvent the wheel.
For many users, security plays a key role in managed services. Using Flannel as the standard CNI (Container Network Interface) can be a problem here, as Flannel does not support network policies. However, K3s offers a practical and simple solution. The K3s project has integrated a network policy controller that allows network policies to be used even when Flannel is in use. This controller can be enabled or disabled as needed, for example if you prefer Cilium or another CNI solution. With the right configuration, almost no compromises are necessary.
