...
| Name | OS | Master flavor | Node flavor |
|---|---|---|---|
| kubernetes-template | Fedora AtomicHost 29 | m1.small | t1m1.largesmall |
| kubernetes-template-ha | Fedora AtomicHost 29 | m1.small | m1.small |
| docker-swarm-template | Fedora AtomicHost 29 | m1.small | m1.small |
| docker-swarm-template-ha | Fedora AtomicHost 29 | m1.small | m1.small |
For more information, all templates can be listed with
...
For each template, you can override a few parameters when you create your cluster:
| Parameter | Comment |
|---|---|
| --docker-volume-size | Size of cinder volume housing docker images and volumes. Defaults to |
| 20GB for our public templates | |
| --master-flavor | Instance flavor of VMs running the master node. Defaults to m1.small for public templates |
| --flavor | Instance flavor of VMs runnin worker nodes. Defaults to t1. |
| small for public templates | |
| --labels | Override default labels for the give COE. Consult documentation for valid labels for each COE. Note the labels set in the public templates are there for a reason Also note that --labels does not merge, so if you want to add labels, please include the labels set in the template as well. |
Docker Swarm
This will create Docker Swarm cluster with one master node, and one worker node
...
Our public kubernetes template has a does not have the keystone auth module enabled by default. That But if you chosse to enable it via label overrides, that makes it possible to interact with your newly created cluster via the environment variables from your opencrc file. If you want that, configure kubectl to use openstack auth as follows:
| Code Block |
|---|
$ kubectl config set-credentials openstackuser --auth-provider=openstack $ kubectl config set-context --cluster=<yourclustername> --user=openstackuser openstackuser@<yourclustername> $ kubectl config use-context openstackuser@<yourclustername> |
The defaults doesn't really allow you to do much, and you will have to setup RBAC policies yourself, to your liking.
Scaling
TBA
Upgrading
TBA