docs
docs copied to clipboard
kubermatic
update kubevirt doc for topology spread constaint
Update kubevirt docs with TopologySpreadConstraint for VMs.
Signed-off-by: Sankalp Rangare [email protected]
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: sankalp-r
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [sankalp-r]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Maybe we should wait for the UI to update the screenshots ? or do you plan to do a follow PR ?
Maybe we should wait for the UI to update the screenshots ? or do you plan to do a follow PR ?
yes, I will add the screenshots in follow-up PR after UI is ready.
Maybe we should wait for the UI to update the screenshots ? or do you plan to do a follow PR ?
yes, I will add the screenshots in follow-up PR after UI is ready.
Ok, good then. We will also need an "upgrade" to KKP 2.22 section to describe the change to do in the MD for the deprecation (warning that it would spawn a new VM)
For the upgrade 2.21 to 2.22, do we already create a section like: https://docs.kubermatic.com/kubermatic/v2.21/tutorials-howtos/upgrading/upgrade-from-2.20-to-2.21/ ? Or add a section in this page containing the upgrade information, that we will move the to general section when creating the release ? Let's discuss this tomorrow.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mfranczy, sankalp-r
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [mfranczy,sankalp-r]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Do we want also to update https://docs.kubermatic.com/kubermatic/main/architecture/supported-providers/kubevirt/kubevirt/#kkp-machinedeployment-sample or maybe link to: https://github.com/kubermatic/machine-controller/blob/main/examples/kubevirt-machinedeployment.yaml to avoid changing this image each time ?
Do we want also to update https://docs.kubermatic.com/kubermatic/main/architecture/supported-providers/kubevirt/kubevirt/#kkp-machinedeployment-sample or maybe link to: https://github.com/kubermatic/machine-controller/blob/main/examples/kubevirt-machinedeployment.yaml to avoid changing this image each time ?
Updating it makes more sense, because if we add a link, then for the released-version, it will always point to the latest MC(main).
LGTM label has been added.