FishOS benefits for a Kubernetes Managed Platform
Kubernetes view for Service Consumers and Operators
Kubernetes is an open source system for the automation of deployments, scaling, and management of containerized applications. For Service Consumers such as developers in enterprises, Kubernetes’ support for programmable, agile, and rapidly deployable environments with a self-service degree of control is very valuable.
FishOS enables Operators in enterprises to easily provide multi-tenanted Kubernetes environments, with proven security assurances, allowing for a faster and simpler way to develop applications.
With FishOS, Service Consumers also gain from persistent block storage, software-defined storage and software-defined networking. While FishOS supports a broad range of storage options, FishOS provides Ceph as the default storage option. With the integration between Ceph and Kubernetes in FishOS, users can benefit from persistent storage without any additional complexities.
FishOS Benefits for a Kubernetes management platform
Sardina FishOS offers a full cloud Kubernetes platform, delivering the following benefits:
- A suite of automation tools to address in a reliable manner the full lifecycle of Kubernetes platform
- Agile resources on demand
- Greater efficiency
- Optimized TCO and reduced hardware cost
- High cloud service reliability and scalability for container applications and clusters
- Auto healing system with Health Engine feature
- Smooth deployment and Zero-Downtime Upgrade
- Access to a set of cloud operations, including log management, system monitoring, capacity planning with scalable and highly available push-based monitoring handling both metrics data and log data
- Remove the complexity of deploying, operating and upgrading
- Storage orchestration, supporting a broad range of storage options
Our recommendation
FishOS supports both running Kubernetes clusters within VMs and on bare metal servers. Typically, in organizations where the Service Consumer and Operator are loosely coupled, in relative terms, it would make sense to run Kubernetes clusters within VMs, so as to benefit from the strong security segregation of VMs, as well as reliability and resilience afforded by VMs. These greater security, reliability, and resilience benefits come at the price of KVM overhead, typically seen as approximately 4% of peak system performance. Is 4% too high a price to pay?
Conversely, in organizations with the tightly coupled relationship between the Service Consumer and Operator, it would viable to run Kubernetes clusters on bare metal servers, to gain better performance, though potentially being exposed in the event of any security escape, or encountering downtime in the event of faults in the data center.
