mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
71 lines
1.8 KiB
Plaintext
71 lines
1.8 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * networking/metallb/metallb-operator-install.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="nw-metallb-operator-initial-config_{context}"]
|
|
= Starting MetalLB on your cluster
|
|
|
|
[role="_abstract"]
|
|
To start MetalLB on your cluster after installing the MetalLB Operator in {product-title}, you create a single MetalLB custom resource.
|
|
|
|
.Prerequisites
|
|
|
|
* Install the OpenShift CLI (`oc`).
|
|
|
|
* Log in as a user with `cluster-admin` privileges.
|
|
|
|
* Install the MetalLB Operator.
|
|
|
|
.Procedure
|
|
|
|
. Create a single instance of a MetalLB custom resource:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ cat << EOF | oc apply -f -
|
|
apiVersion: metallb.io/v1beta1
|
|
kind: MetalLB
|
|
metadata:
|
|
name: metallb
|
|
namespace: metallb-system
|
|
EOF
|
|
----
|
|
+
|
|
** For the `metdata.namespace` parameter, substitute `metallb-system` with `openshift-operators` if you installed the MetalLB Operator using the web console.
|
|
|
|
.Verification
|
|
|
|
Confirm that the deployment for the MetalLB controller and the daemon set for the MetalLB speaker are running.
|
|
|
|
. Verify that the deployment for the controller is running:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get deployment -n metallb-system controller
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME READY UP-TO-DATE AVAILABLE AGE
|
|
controller 1/1 1 1 11m
|
|
----
|
|
|
|
. Verify that the daemon set for the speaker is running:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get daemonset -n metallb-system speaker
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
|
|
speaker 6 6 6 6 6 kubernetes.io/os=linux 18m
|
|
----
|
|
+
|
|
The example output indicates 6 speaker pods. The number of speaker pods in your cluster might differ from the example output. Make sure the output indicates one pod for each node in your cluster.
|
|
|