mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
correcting image name to fix PV1 build
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
4cb7e9831f
commit
6aac021d25
BIN
images/695_OpenShift_MetalLB_FRRK8s_integration_0624.png
Normal file
BIN
images/695_OpenShift_MetalLB_FRRK8s_integration_0624.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 49 KiB |
@@ -9,13 +9,13 @@ toc::[]
|
||||
:FeatureName: The `FRRConfiguration` custom resource
|
||||
include::snippets/technology-preview.adoc[]
|
||||
|
||||
FRRouting (FRR) is a free, open source internet routing protocol suite for Linux and UNIX platforms.
|
||||
`FRR-K8s` is a Kubernetes based DaemonSet that exposes a subset of the `FRR` API in a Kubernetes-compliant manner.
|
||||
As a cluster administrator, you can use the `FRRConfiguration` custom resource (CR) to configure `MetalLB` to use `FRR-K8s` as the backend.
|
||||
FRRouting (FRR) is a free, open source internet routing protocol suite for Linux and UNIX platforms.
|
||||
`FRR-K8s` is a Kubernetes based DaemonSet that exposes a subset of the `FRR` API in a Kubernetes-compliant manner.
|
||||
As a cluster administrator, you can use the `FRRConfiguration` custom resource (CR) to configure `MetalLB` to use `FRR-K8s` as the backend.
|
||||
You can use this to avail of FRR services, for example, receiving routes.
|
||||
If you run `MetalLB` with `FRR-K8s` as a backend, `MetalLB` generates the `FRR-K8s` configuration corresponding to the MetalLB configuration applied.
|
||||
|
||||
image::695_OpenShift MetalLB_FRRK8s integration_0624.png[MetalLB integration with FRR]
|
||||
image::695_OpenShift_MetalLB_FRRK8s_integration_0624.png[MetalLB integration with FRR]
|
||||
|
||||
// Activating integration of MetalLB and FRR-K8s
|
||||
include::modules/nw-metallb-configuring-frr-8ks.adoc[leveloffset=+1]
|
||||
|
||||
Reference in New Issue
Block a user