The configuration file of the Kupboard is created in the
yaml format. The configuration file contains a variety of information, including versions, meta-information, global variables, and the entire cluster configuration.
The default name of the configuration file is
kupboard.yaml. This can be created by a project or service. If you use a name other than
kupboard.yaml, you must specify the name of the configuration file (with the extension omitted), such as
--config <config-name> when using the kupboard commands.
Basically the configuration has 4 sections
version can be a configuration version. It can be also a version of project or deployment.
metadata must have
company. You can also add meta information that you want.
namea name of project or service
companya company name
projecta project name
vars section, you can define many variables that you can refer to by kupboard and kollection.
The variables in
Project Information are required for the service operation. To use the Harbor registry, a valid ssl certification should be prepared. If you're not using the registry, you can ignore these variables.
kube_registry_password should be 8-20 characters long with at least 1 uppercase, 1 lowercase and 1 number. Check out Harbor Package for more information.
Secrets variables are used to access various open source packages. If you're not using open source packages, you can ignore these variables.
The configuration of the cluster can be customized as you want. If you want to configure it for test or demo, you can configure it with six servers as above, but you can configure three gateway servers and four or more servers in the service clutter to install a variety of solutions. If you want to build a separated Data plane, you can configure an additional storage cluster. However, the admin cluster must have 1 admin server and the cluster names cannot change.
You can also add clusters with names you want as shown in the following example.
The servers in the cluster section have a naming convention such as
<cluster-name>-node#. For example, the first server in the admin cluster is
admin-node1 and the second server in the service cluster is