Kubernetes Cluster Requirements

This document describes the requirements Yaook imposes on a Kubernetes Cluster. In contrast to Kubernetes API Requirements, this document is focused on the services and resources which need to be defined inside a cluster. For requirements on the Kubernetes deployment itself, such as feature flags or Kubernetes versions, please see Kubernetes API Requirements instead.

Storage Classes

The Kubernetes cluster MUST have a default storage class set. This storage class MUST allow moving volumes between nodes.


In an upcoming release, the requirements will change to:

  • There MUST be a storage class which is host local (e.g. provided by the local-storage controller).

  • There MUST be a storage class which is not host local and can be moved between different nodes.



The networking SHOULD be provided by Calico. Other network layers may work, but are not officially supported and you are on your own.


The networking.k8s.io/v1 API MUST be implemented by a proper Ingress controller.

Load Balancer

Yaook itself does not require an external load balancer, but it is likely that your ingress controller (see above) will.


The cert-manager.io/v1 API MUST be implemented.


The monitoring.coreos.com/v1 Custom Resources MUST exist. The usage of these resources (e.g. by the Prometheus Operator) is optional.

Storage Provider

The following details additional storage requirements for individual services.


Cinder supports Ceph and/or Netapp as a block storage backend.


Glance supports Ceph or PVCs (via the file backend) as a storage backend. PVCs need to support ReadWriteMany as access method.


Gnocchi supports Ceph or S3 as a storage backend.


If Ceph should be used with Yaook it is RECOMMENDED to deploy the ceph cluster using Rook.io. It is OPTIONAL to run it in the same Kubernetes cluster as Yaook itself.