...
- Note that a separate cluster template for k8s needs to be created for each project.
- Use "Calico" as a network driver. "flannel" seem to have a issue.
- It is handy to have a ingress controller. Add a label of 'ingress_controller="octavia"' to enable the octavia ingress controller. Other type of ingress controllers are not tested yet.
- From the Container Infra section, use the template to create the k8s cluster of the size you want.
- A single master is only configured and tested for now.
- You can add additional worker nodes later (you can delete some of them), but I don't think you can change the flavor of the nodes.
- creating a k8s cluster may take tens of minutes and it may fail. Just delete the failed one and recreate one.
- The ssh key-pair is usually not important. Just use the default.
- Use the existing network and keep cluster api private.
- Note that a cluster will be also be created under the Cluster Infra → KASI cluster section.
Step 2. Setup connection to the created k8s cluster
...
- Once you have a file with above contents (the file is named as 'sc-cinder.yaml' in this example)
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
> kubectl apply -f sc0cinder.yaml > kubectl get storageclass NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE standard (default) kubernetes.io/cinder Delete Immediate false 7d1h |
...