Following https://github.com/kubevirt/kubevirt/issues/14934
We can see that when using subdomain,
`nslookup vmi.subdomain` won't resolve.
Reason is that despite virt-launcher has default k8s ndots:5,
ndots option isn't populated to the guest, and depends on the local resolver.
If desired, cloud init can be used to override ndots.
- cloudInitNoCloud:
userData: |-
#cloud-config
bootcmd:
- nmcli connection modify "System eth0" ipv4.dns-options "ndots:2"
- nmcli connection up "System eth0"
name: cloudinitdisk
Update docs about ndots effect.
Signed-off-by: Or Shoval <oshoval@redhat.com>
We now provide these arch specific images under a single nightly
manifest allowing users to use the same set of commands to install our
nightly builds across amd64, arm64 and s390x.
Signed-off-by: Lee Yarwood <lyarwood@redhat.com>
Starting KubeVirt 1.6, the VM will be automatically migrated on
hotplug and hot-unplug scenarios.
[1] https://github.com/kubevirt/kubevirt/pull/14259
Signed-off-by: Orel Misan <omisan@redhat.com>
This adds documentation for the kubevirt.io/disablePCIHole64 annotation,
that allows to run legacy Windows versions on KubeVirt.
Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>
* net, ifaces: Fix ports documentation
The current documentation is incorrect. It indicates that the ports attribute
serves as some sort of firewall, when in fact is has a diffent effect on each
net binding. It is basically either a list of ports to forward or it has no effect
at all.
Signed-off-by: Nir Dothan <ndothan@redhat.com>
* net, ifaces: Fix broken example
It currently says 'configured via cloud init, as shown below',
the example below has no cloud init. Then in the bottom the note
inbdicates 'The IPv6 address for the VM and default gateway **must** be the ones
shown above', but nothing is showing above.
Hence resore the cloud-init part from the older documentation.
Signed-off-by: Nir Dothan <ndothan@redhat.com>
---------
Signed-off-by: Nir Dothan <ndothan@redhat.com>
* Update activating_feature_gates.md
Hi and thanks for this great project :)
I propose this modification because it took me some time to identify which value I should put on the yaml configuration to activate a specific Feature Gate.
I hope this change would help others.
Feel free to apply any modification if needed.
Signed-off-by: Pierre-Yves Aillet <pyaillet@users.noreply.github.com>
* Update docs/cluster_admin/activating_feature_gates.md
Fix after review
Co-authored-by: Itamar Holder <77444623+iholder101@users.noreply.github.com>
Signed-off-by: Pierre-Yves Aillet <pyaillet@users.noreply.github.com>
---------
Signed-off-by: Pierre-Yves Aillet <pyaillet@users.noreply.github.com>
Co-authored-by: Itamar Holder <77444623+iholder101@users.noreply.github.com>
These cleanups bring the documentation in line with the current
implementation of ssh and scp in virtctl.
Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>
Update the description for using individual configuration per VM to
match the actual implementation in KubeVirt.
Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>
* Add volume migration cancellation and recovery
Signed-off-by: Alice Frosi <afrosi@redhat.com>
* Fix the title for volume migration doc
Signed-off-by: Alice Frosi <afrosi@redhat.com>
* Add volume_migration to the storage pages
Signed-off-by: Alice Frosi <afrosi@redhat.com>
---------
Signed-off-by: Alice Frosi <afrosi@redhat.com>
This is a minor update to the Video and Graphics Device section, to clarify _not_ attaching a graphics device to a `VirtualMachineInstance`
Signed-off-by: Ben Chapman <5124569+Ben-Chapman@users.noreply.github.com>
Change [#11997](https://github.com/kubevirt/kubevirt/pull/11997/)
introduces new feature gates for virtiofs and dropped the support of
privileged sharing mode. It syncs the documentation to the mentioned
change:
* Users need to enable the feature gate
`EnableVirtioFsConfigVolumes` for sharing `configMaps`, `secrets`,
and `serviceAccounts`.
* Users need to enable the feature gate `EnableVirtioFsStorageVolumes`
for sharing `PVCs`.
* Dropped support of privileged sharing mode.
Moreover, change
[#13756](https://github.com/kubevirt/kubevirt/pull/13756) enables to
migrate VMs while sharing devices with virtiofs. Therefore, all mentions
to live migration has been dropped.
Signed-off-by: Javier Cano Cano <jcanocan@redhat.com>
Change the virtctl create vm examples to use the correct flag for adding
a sysprep volume to a created VM.
Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>
Currently, the passt binding plugin is registered using the LinkRefresh
migration method.
Unfortunately, the LinkRefresh method does not work well with all
guest OSes.
Add an explanation about this change and its consequences.
Signed-off-by: Orel Misan <omisan@redhat.com>
* compute, live-migrations: Fix typo
migrationConfiguration does not exist in schema. Correct it to migrations.
Signed-off-by: Nir Dothan <ndothan@redhat.com>
* compute, live-migrations: Improve grammer
Remove occurances of the word "being" which seems to have been overly used,
in order to make the text more concise
Signed-off-by: Nir Dothan <ndothan@redhat.com>
---------
Signed-off-by: Nir Dothan <ndothan@redhat.com>
* virtctl: Move Instancetype and Preference creation
Move the creation of instance types and preferences into their own page.
Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>
* virtctl: Minor enhancements to Instancetype and Preference creation
Apply minor enhancements to the instancetype and preference creation:
- Use code blocks for flags
- Be more specific about which resources are created
- Add colons to examples
- Reformat file to not exceed line length of 80
- Change heading levels to help the ToC
Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>
* virtctl: Overhaul virtctl create vm docs
Overhaul the virtctl create vm docs by:
- Adding documentation for generatin cloud-init user data
- Adding documentation for the access credential flag
- Adding documentation for the sysprep volume flag
- Updating and extending the examples
- Applying minor fixes throughout the file
Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>
---------
Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>
* interfaces and networks: additional organization and cleanup
technical commit to make up for changes that had "slipped out"
of PR https://github.com/kubevirt/user-guide/pull/843/
- virtio-net multiqueue: push to the bottom under Additional Notes
- MTU: move up above virtio-net multiqueue, under Aditional Notes
no changes in content only positioning
Signed-off-by: Nir Dothan <ndothan@redhat.com>
* networks: fix examples, links, multus primary net
- lose backend and frontend vocabulary
- inidicate that multus can be primary
- highlight advantages of pod network
- fix all yaml exmlpes in networks section such that it is closer to real VM schema
- fix multus links to the project that kubevirt actually uses
- chnage the bridge network+NAD example to a one that really works
Signed-off-by: Nir Dothan <ndothan@redhat.com>
* interfaces: highlight plugins, remove redundant
- highlight network biniding plugins
- iptables -> nftables in masqurade
- address ports as allow-list as opposed to port-forwarding
- remove macvtap core bindings
and reference the binding plugins instead
- remove slirp following removal in v1.3.0 by PR https://github.com/kubevirt/kubevirt/pull/11701
Signed-off-by: Nir Dothan <ndothan@redhat.com>
* interfaces: remove passt
Signed-off-by: Nir Dothan <ndothan@redhat.com>
* interfaces: refactor sriov
remove references to sriov-network-operator as it is not strictly required
and is not a part of kubevirt upstream
Signed-off-by: Nir Dothan <ndothan@redhat.com>
* modify all remaining broken VM spec yaml examples
All those example started with type: VM which doesn't exist included
a "shortened" path to domain and network.
make all of those closer to the real schema and add a comment to each indicating that the
example is incomplete
Signed-off-by: Nir Dothan <ndothan@redhat.com>
* convert HTML tables to Markdown tables
Signed-off-by: Nir Dothan <ndothan@redhat.com>
* vmi to vm: modify indications and examples
use VM instead of VMI wherever applicable as VM is the offical
user facing API.
Signed-off-by: Nir Dothan <ndothan@redhat.com>
* interfaces: shorten example manifests
small verbiage corrections
elaborate sriov prep
Signed-off-by: Nir Dothan <ndothan@redhat.com>
---------
Signed-off-by: Nir Dothan <ndothan@redhat.com>
rearrange sections such that reading through would be easier,
mainly by moving most restiriction and limitations to the bottom.
Main sections are: Networks, Interfcaes. Security, Limitations and Known Issues, Additional Notes
Later on links will be added from the sections in the top to their limitations in the bottom
Signed-off-by: Nir Dothan <ndothan@redhat.com>