Boot a machine from a block storage volume¶
Available since 2.18.0 TechPreview
Clouds that do not have enough space on hypervisors may require booting of cluster machines from a block storage volume. Using the option, the Cinder storage is used instead of the Nova storage.
To boot a machine for an OpenStack-based managed cluster from a volume:
Download your management cluster
kubeconfig
:Log in to the Container Cloud web UI with the
m:kaas:namespace@operator
orm:kaas:namespace@writer
permissions.Switch to the required project using the Switch Project action icon located on top of the main left-side navigation panel.
Expand the menu of the tab with your user name.
Click Download kubeconfig to download
kubeconfig
of your management cluster.Log in to any local machine with
kubectl
installed.Copy the downloaded
kubeconfig
to this machine.
Scale down the OpenStack provider on the required regional cluster:
kubectl --kubeconfig <pathToRegionalClusterKubeconfig> -n kaas scale deploy openstack-provider --replicas 0
Create a machine using the Container Cloud web UI as described in Add a machine.
Open the required
Machine
object for editing:kubectl --kubeconfig <pathToMgmtClusterKubeconfig> -n <projectName> edit machine <machineName>
In the
spec:providerSpec
section, define the following parameter to boot a server from a block storage volume based on the given image:bootFromVolume: enabled: true volumeSize: 120
Note
The minimal storage requirement is 120 GB per node. For details, see Requirements for an OpenStack-based cluster.
Scale up the OpenStack provider:
kubectl -n kaas scale deploy openstack-provider --replicas 3