Skip to content

DOCPLAN-172: Fixed some minor style issues #110695

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
sjhala-ccs wants to merge 1 commit into
base: main
Choose a base branch
from
Open

DOCPLAN-172: Fixed some minor style issues #110695

Show file tree
Hide file tree
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
4 changes: 2 additions & 2 deletions virt/vm_networking/virt-accessing-vm-secondary-network-fqdn.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ include::_attributes/common-attributes.adoc[]
toc::[]

[role="_abstract"]
You can access a virtual machine (VM) that is attached to a secondary network interface from outside the cluster by using its fully qualified domain name (FQDN). To connect to a VM by using its external FQDN, you must configure the DNS server, retrieve the cluster FQDN, and then connect to the VM by using the `ssh` command.
You can access a virtual machine (VM) that is attached to a secondary network interface from outside the cluster by using its fully qualified domain name (FQDN). To connect to a VM by using its external FQDN, you must configure the DNS server, retrieve the cluster FQDN, then connect to the VM by using the `ssh` command.

:FeatureName: Accessing a VM from outside the cluster by using its FQDN
include::snippets/technology-preview.adoc[]
Expand All @@ -21,7 +21,7 @@ include::modules/virt-connecting-vm-secondarynw-using-fqdn.adoc[leveloffset=+1]
== Additional resources
// Hiding until OSDOCS-3691 is merged
ifndef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
* xref:../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc#configuring-ingress-cluster-traffic-load-balancer[Configuring ingress cluster traffic using a load balancer]
* xref:../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc#configuring-ingress-cluster-traffic-load-balancer[Configuring ingress cluster traffic by using a load balancer]
* xref:../../networking/networking_operators/metallb-operator/about-metallb.adoc#about-metallb[About MetalLB and the MetalLB Operator]
endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
* xref:../../virt/vm_networking/virt-configuring-viewing-ips-for-vms.adoc#virt-configuring-viewing-ips-for-vms[Configuring IP addresses for virtual machines]
4 changes: 2 additions & 2 deletions virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ include::_attributes/common-attributes.adoc[]
toc::[]

[role="_abstract"]
You can connect a VM to an OVN-Kubernetes custom secondary overlay network. A layer 2 topology connects workloads by a cluster-wide logical switch. The OVN-Kubernetes Container Network Interface (CNI) plugin uses the Geneve (Generic Network Virtualization Encapsulation) protocol to create an overlay network between nodes. You can use this overlay network to connect VMs on different nodes, without having to configure any additional physical networking infrastructure.
You can connect a VM to an OVN-Kubernetes custom secondary overlay network. A layer 2 topology connects workloads by a cluster-wide logical switch. The OVN-Kubernetes Container Network Interface (CNI) plugin uses the Geneve (Generic Network Virtualization Encapsulation) protocol to create an overlay network between nodes. You can use this overlay network to connect VMs on different nodes, without configuring any additional physical networking infrastructure.

ifndef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
[NOTE]
Expand Down Expand Up @@ -40,5 +40,5 @@ ifndef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
* xref:../../networking/multiple_networks/secondary_networks/creating-secondary-nwt-ovnk.adoc#configuration-ovnk-additional-networks_configuring-additional-network-ovnk[Creating secondary networks on OVN-Kubernetes]
* xref:../../networking/networking_operators/k8s-nmstate-about-the-k8s-nmstate-operator.adoc#k8s-nmstate-about-the-k8s-nmstate-operator[About the Kubernetes NMState Operator]
* xref:../../networking/multiple_networks/secondary_networks/configuring-multi-network-policy.adoc#configuring-multi-network-policy[Multi-network policy API]
* xref:../../networking/multiple_networks/primary_networks/about-primary-nwt-nad.adoc#about-primary-nwt-nad[Creating primary networks using a NetworkAttachmentDefinition]
* xref:../../networking/multiple_networks/primary_networks/about-primary-nwt-nad.adoc#about-primary-nwt-nad[Creating primary networks by using a network attachment definition]
endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
4 changes: 2 additions & 2 deletions virt/vm_networking/virt-exposing-vm-with-service.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,8 +23,8 @@ ifndef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
[role="_additional-resources"]
[id="additional-resources_creating-service-vm"]
== Additional resources
* xref:../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#configuring-ingress-cluster-traffic-nodeport[Configuring ingress cluster traffic using a NodePort]
* xref:../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc#configuring-ingress-cluster-traffic-load-balancer[Configuring ingress cluster traffic using a load balancer]
* xref:../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#configuring-ingress-cluster-traffic-nodeport[Configuring ingress cluster traffic by using a `NodePort`]
* xref:../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc#configuring-ingress-cluster-traffic-load-balancer[Configuring ingress cluster traffic by using a load balancer]
* xref:../../networking/networking_operators/metallb-operator/metallb-operator-install.adoc#metallb-operator-install[Installing the MetalLB Operator]
* xref:../../networking/ingress_load_balancing/metallb/metallb-configure-services.adoc#metallb-configure-services[Configuring services to use MetalLB]
endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
6 changes: 3 additions & 3 deletions virt/vm_networking/virt-networking-overview.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ The following figure illustrates the typical network setup of {VirtProductName}.
.{VirtProductName} networking overview
image::318_OpenShift_Virtualization_Networking_0423.png[{VirtProductName} networking architecture]

image:darkcircle-1.png[20,20] Pods and VMs run on the same network infrastructure which allows you to easily connect your containerized and virtualized workloads.
image:darkcircle-1.png[20,20] Pods and VMs run on the same network infrastructure so you can easily connect your containerized and virtualized workloads.

image:darkcircle-2.png[20,20] You can connect VMs to the default pod network and to any number of secondary networks.

Expand All @@ -30,7 +30,7 @@ image:darkcircle-4.png[20,20] Multus is a "meta" CNI plugin that enables a pod o

image:darkcircle-5.png[20,20] The default pod network is overlay-based, tunneled through the underlying machine network.

image:darkcircle-6.png[20,20] The machine network can be defined over a selected set of network interface controllers (NICs).
image:darkcircle-6.png[20,20] You can define the machine network over a selected set of network interface controllers (NICs).

image:darkcircle-7.png[20,20] Secondary VM networks are typically bridged directly to a physical network, with or without VLAN encapsulation. It is also possible to create virtual overlay networks for secondary networks.

Expand All @@ -43,7 +43,7 @@ Connecting VMs directly to the underlay network is not supported on {product-ros
====
Connecting VMs to user-defined networks with the `layer2` topology is recommended on public clouds.
====
image:darkcircle-8.png[20,20] Secondary VM networks can be defined on dedicated set of NICs, as shown in Figure 1, or they can use the machine network.
image:darkcircle-8.png[20,20] Secondary VM networks can be defined on dedicated set of NICs, as shown in figure 1, or they can use the machine network.
endif::openshift-dedicated[]

include::modules/virt-networking-glossary.adoc[leveloffset=+1]
Expand Down