TELCODOCS-1867 - remove configuration step#82163
TELCODOCS-1867 - remove configuration step#82163michaelryanpeter merged 1 commit intoopenshift:mainfrom
Conversation
openshift-ci
bot
added
the
size/M
|
🤖 Fri Sep 20 13:03:46 - Prow CI generated the docs preview: https://82163--ocpdocs-pr.netlify.app/ |
slovern
force-pushed
the
TELCODOCS-1867-II
branch
from
724bcae to
69bfc51
Compare
| 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. | ||
| As a cluster administrator, you can use the `FRRConfiguration` custom resource (CR) to configure the way `MetalLB` uses `FRR-K8s`. |
There was a problem hiding this comment.
this is more "to leverage the FRR instance beyond the features offered by MetalLB"
There was a problem hiding this comment.
Changed to: "As a cluster administrator, you can use the FRRConfiguration custom resource (CR) to avail of some of the FRR services not provided by MetalLB, for example, receiving routes."
slovern
force-pushed
the
TELCODOCS-1867-II
branch
2 times, most recently
from
6990134 to
66ac8e1
Compare
|
/lgtm |
|
/label peer-review-needed |
openshift-ci
bot
added
the
peer-review-needed
|
/label telco |
|
/lgtm |
|
@gkopels: changing LGTM is restricted to collaborators DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
mburke5678
added
the
peer-review-in-progress
| 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. | ||
| As a cluster administrator, you can use the `FRRConfiguration` custom resource (CR) to avail of some of the FRR services not provided by MetalLB, for example, receiving routes. |
There was a problem hiding this comment.
Not sure "avail" is the best word here. (I see that it was already there before you came along.)
| As a cluster administrator, you can use the `FRRConfiguration` custom resource (CR) to avail of some of the FRR services not provided by MetalLB, for example, receiving routes. | |
| As a cluster administrator, you can use the `FRRConfiguration` custom resource (CR) to take advantage of some of the FRR services not provided by MetalLB, for example, receiving routes. |
| As a cluster administrator, you can use the `FRRConfiguration` custom resource (CR) to avail of some of the FRR services not provided by MetalLB, for example, receiving routes. | |
| As a cluster administrator, you can use the `FRRConfiguration` custom resource (CR) to access some of the FRR services not provided by MetalLB, for example, receiving routes. |
|
@slovern One suggestion. Otherwise LGTM |
mburke5678
added
peer-review-done
slovern
force-pushed
the
TELCODOCS-1867-II
branch
from
66ac8e1 to
7f08bef
Compare
|
New changes are detected. LGTM label has been removed. |
|
thanks for the review @mburke5678 |
|
@slovern: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/label merge-review-needed |
openshift-ci
bot
added
the
merge-review-needed
|
/label merge-review-in-progress |
openshift-ci
bot
added
the
merge-review-in-progress
|
/cherrypick enterprise-4.17 |
|
@michaelryanpeter: new pull request created: #82231 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
thanks for the merge @michaelryanpeter |
7 participants
Version(s): 4.17
Issue: https://issues.redhat.com//browse/TELCODOCS-1867
Link to docs preview: Configuring the integration of MetalLB and FRR-K8s
QE review:
Additional information: This is the removal of the section Activating the integration of MetalLB and FRR-K8s as this is now the default backend and does not require activation.