Skip to content

fix: add small guide for ctrl as VM in libvirt #324

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mrbojangles3 wants to merge 1 commit into
base: master
Choose a base branch
from
+25 −1
Open

fix: add small guide for ctrl as VM in libvirt #324

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 25 additions & 1 deletion docs/install-upgrade/install.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,10 @@ There are utilities that assist this process such as [etcher](https://etcher.bal

## Install Control Node

This control node should be given a static IP address. Either a lease or statically assigned.
This control node should be given a static IP address. Either a lease or
statically assigned. Running the control node as a virtual machine isn't
officially supported but there are recommendations [in this
section](#controller-as-virtual-machine).
Comment on lines +89 to +92

1. Configure the server to use UEFI boot **without** secure boot

Expand Down Expand Up @@ -121,6 +124,27 @@ interface. It runs a DHCP server, as well as a small HTTP server.
The `external` network allows the user to access the control node via their local
IT network. It provides SSH access to the host operating system on the control node.

### Controller as Virtual Machine

These instructions are provided for `libvirt`, adapt as needed for the chosen
hypervisor:

- Ensure the hardware specs match [the control node](./requirements.md#control-node)
- Disable secure boot:
```xml
<os firmware='efi'>
<firmware>
<feature enabled='no' name='secure-boot'/>
</firmware>
</os>
```
Comment on lines +133 to +140
- Configure the `efi` firmware and `q35` machine type
- Configure the virtual machine for auto start when the host system boots up.
- Configure both NICs as `virtio`
- Ensure a console device is present
- Use VirtIO devices wherever possible


### Fabric Manages Switches

Now that the install has finished, you can start interacting with the Fabric using `kubectl`, `kubectl fabric` and `k9s`, all pre-installed as part of the Control Node installer.
Expand Down
Loading