openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OSDOCS-16338: fixes cluster mentions MicroShift

Browse Source
This commit is contained in:
“Shauna Diaz”
2025-09-30 07:55:42 -04:00
committed by openshift-cherrypick-robot
parent bd98da653c
commit 4a0bd7b8b1
143 changed files with 348 additions and 353 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
microshift_networking/microshift-cni.adoc
View File

@@ -6,7 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
toc::[]
The OVN-Kubernetes Container Network Interface (CNI) plugin is the default networking solution for the {microshift-short} node. OVN-Kubernetes is a virtualized network for pods and services that is based on Open Virtual Network (OVN).
The OVN-Kubernetes Container Network Interface (CNI) plugin is the default networking solution for a {microshift-short} node. OVN-Kubernetes is a virtualized network for pods and services that is based on Open Virtual Network (OVN).
* Default network configuration and connections are applied automatically in {microshift-short} with the `microshift-networking` RPM during installation.
* A node that uses the OVN-Kubernetes network plugin also runs Open vSwitch (OVS) on the node.

2
microshift_networking/microshift-configuring-routes.adoc
View File

@@ -6,7 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
toc::[]
You can configure routes for services to have {microshift-short} cluster access.
You can configure routes for services to have {microshift-short} node access.
//OCP module, edit with care; Creating an insecure/http route
include::modules/microshift-nw-create-http-based-route.adoc[leveloffset=+1]

6
microshift_networking/microshift-networking-settings.adoc
View File

@@ -8,13 +8,13 @@ toc::[]
Learn how to apply networking customization and default settings to {microshift-short} deployments. Each node is contained to a single machine and single {microshift-short}, so each deployment requires individual configuration, pods, and settings.
Cluster Administrators have several options for exposing applications that run inside a cluster to external traffic and securing network connections:
{microshift-short} administrators have several options for exposing applications that run inside a node to external traffic and securing network connections:
* A service such as NodePort
* API resources, such as `Ingress` and `Route`
By default, Kubernetes allocates each pod an internal IP address for applications running within the pod. Pods and their containers can have traffic between them, but clients outside the cluster do not have direct network access to pods except when exposed with a service such as NodePort.
By default, Kubernetes allocates each pod an internal IP address for applications running within the pod. Pods and their containers can have traffic between them, but clients outside the node do not have direct network access to pods except when exposed with a service such as NodePort.
include::modules/microshift-configuring-ovn.adoc[leveloffset=+1]
@@ -31,7 +31,7 @@ include::modules/microshift-ovs-snapshot.adoc[leveloffset=+1]
[id="microshift-about-load-balancer-service_{context}"]
== The {microshift-short} LoadBalancer service for workloads
{microshift-short} has a built-in implementation of network load balancers that you can use for your workloads and applications within the cluster. You can create a `LoadBalancer` service by configuring a pod to interpret ingress rules and serve as an ingress controller. The following procedure gives an example of a deployment-based `LoadBalancer` service.
{microshift-short} has a built-in implementation of network load balancers that you can use for your workloads and applications within the node. You can create a `LoadBalancer` service by configuring a pod to interpret ingress rules and serve as an ingress controller. The following procedure gives an example of a deployment-based `LoadBalancer` service.
include::modules/microshift-deploying-a-load-balancer.adoc[leveloffset=+1]

2
microshift_networking/microshift_multiple_networks/microshift-cni-multus.adoc
View File

@@ -10,7 +10,7 @@ In addition to the default OVN-Kubernetes Container Network Interface (CNI) plug
include::modules/microshift-multus-intro.adoc[leveloffset=+1]
include::modules/microshift-install-multus-running-cluster.adoc[leveloffset=+1]
include::modules/microshift-install-multus-running-node.adoc[leveloffset=+1]
//OCP module, edit with conditionals and care
include::modules/nw-multus-bridge-object.adoc[leveloffset=+1]

2
microshift_networking/microshift_network_policy/microshift-network-policy-index.adoc
View File

@@ -6,7 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
toc::[]
Learn how network policies work for {microshift-short} to restrict or allow network traffic to pods in your cluster.
Learn how network policies work for {microshift-short} to restrict or allow network traffic to pods in your node.
include::modules/microshift-nw-network-policy-intro.adoc[leveloffset=+1]

2
microshift_networking/microshift_network_policy/microshift-viewing-network-policy.adoc
View File

@@ -9,4 +9,4 @@ toc::[]
Use the following procedure to view a network policy for a namespace.
include::modules/nw-networkpolicy-view-cli.adoc[leveloffset=+1]
include::modules/nw-networkpolicy-view-cli.adoc[leveloffset=+1]