Users of the self hosted controller can use the following configuration options:
This option is designed and optimized for production use with a "highly available" (i.e. multi master Kubernetes cluster) deployment configuration with three Kubernetes master nodes and at least one worker node.
Users can always expand the initial deployment anytime by adding worker nodes to the cluster as required.
Single Node Option¶
This option is primarily designed for non-production use (e.g. testing and demos). This allows the entire controller software stack to be provisioned on a single node cluster.
This option is designed for environments where "BOTH" the controller and the managed cluster need to be operated in the same instance/VM.
This option will deploy a minimal version of the controller requiring fewer resources.