This is the helm managed kubernetes deployment of kolab.
By default this will deploy a local k3s instance, but the templates should be compatible with any kubernetes distribution.
The default deployment will be completely self-contained, special care will need to be taken if external services are integrated (such as an existing mysql instance).
* disabled firewall (`systemctl stop firewalld`, I suppose it's possible to configure the firewall properly, but by default your cluster will fail in all sorts of interesting ways that are hard to troubleshoot.)
* stop conflicting docker deployments that are using the same ports
## Quickstart
-To just deploy a k3s deployment locally, run this.
+To just deploy a k3s deployment locally, run this (you will requires a username and password for registry access).
./kolabctl configure
- ./kolabctl deploy --k3s
+ ./kolabctl deploy --k3s $username $password
## kolabctl
The local deployment can be managed using kolabctl which simplifies various administrative tasks.
kolabctl is a thin wrapper around helm/kubectl/artisan, so it is not required to use kolabctl if you are more familiar with the underlying tools,
but it illustrates the various tasks.
## Deployment
### Configure
The deployment configuration is entirely contained in the values.yaml file.
-This step will require your pull secret
+This step will require your quay.io username and password