Skip to content

Commit 02c14ce

Browse files
JoeAldingerJoeAldinger
JoeAldinger
authored and
JoeAldinger
committed
OSDOCS-6269: ovn-k interconnect 4.14
1 parent 4b49830 commit 02c14ce

4 files changed

+222
-266
lines changed

‎modules/nw-ovn-kubernetes-list-database-contents.adoc

Lines changed: 86 additions & 132 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,7 @@
66
[id="nw-ovn-kubernetes-list-database-contents_{context}"]
77
= Listing the OVN-Kubernetes northbound database contents
88

9-
To understand logic flow rules you need to examine the northbound database and understand what objects are there to see how they are translated into logic flow rules.
10-
The up to date information is present on the OVN Raft leader and this procedure describes how to find the Raft leader and subsequently query it to list the OVN northbound database contents.
9+
Each node is controlled by the `ovnkube-controller` container running in the `ovnkube-node` pod on that node. To understand the OVN logical networking entities you need to examine the northbound database that is running as a container inside the `ovnkube-node` pod on that node to see what objects are in the node you wish to see.
1110

1211
.Prerequisites
1312

@@ -16,14 +15,12 @@ The up to date information is present on the OVN Raft leader and this procedure
1615
1716
.Procedure
1817

19-
. Find the OVN Raft leader for the northbound database.
20-
+
2118
[NOTE]
2219
====
23-
The Raft leader stores the most up to date information.
20+
To run ovn `nbctl` or `sbctl` commands in a cluster you must open a remote shell into the `nbdb` or `sbdb` containers on the relevant node
2421
====
2522

26-
.. List the pods by running the following command:
23+
. List pods by running the following command:
2724
+
2825
[source,terminal]
2926
----
@@ -33,201 +30,158 @@ $ oc get po -n openshift-ovn-kubernetes
3330
.Example output
3431
[source,terminal]
3532
----
36-
NAME READY STATUS RESTARTS AGE
37-
ovnkube-master-7j97q 6/6 Running 2 (148m ago) 149m
38-
ovnkube-master-gt4ms 6/6 Running 1 (140m ago) 147m
39-
ovnkube-master-mk6p6 6/6 Running 0 148m
40-
ovnkube-node-8qvtr 5/5 Running 0 149m
41-
ovnkube-node-fqdc9 5/5 Running 0 149m
42-
ovnkube-node-tlfwv 5/5 Running 0 149m
43-
ovnkube-node-wlwkn 5/5 Running 0 142m
33+
NAME READY STATUS RESTARTS AGE
34+
ovnkube-control-plane-8444dff7f9-4lh9k 2/2 Running 0 27m
35+
ovnkube-control-plane-8444dff7f9-5rjh9 2/2 Running 0 27m
36+
ovnkube-control-plane-8444dff7f9-k64b7 2/2 Running 2 (11m ago) 27m
37+
ovnkube-node-55xs2 8/8 Running 0 26m
38+
ovnkube-node-7r84r 8/8 Running 0 16m
39+
ovnkube-node-bqq8p 8/8 Running 0 17m
40+
ovnkube-node-mkj4f 8/8 Running 0 26m
41+
ovnkube-node-mlr8k 8/8 Running 0 26m
42+
ovnkube-node-wqn2m 8/8 Running 0 16m
4443
----
4544

46-
.. Choose one of the master pods at random and run the following command:
45+
. Optional: To list the pods with node information, run the following command:
4746
+
4847
[source,terminal]
4948
----
50-
$ oc exec -n openshift-ovn-kubernetes ovnkube-master-7j97q \
51-
-- /usr/bin/ovn-appctl -t /var/run/ovn/ovnnb_db.ctl \
52-
--timeout=3 cluster/status OVN_Northbound
49+
$ oc get pods -n openshift-ovn-kubernetes -owide
5350
----
5451
+
5552
.Example output
5653
[source,terminal]
5754
----
58-
Defaulted container "northd" out of: northd, nbdb, kube-rbac-proxy, sbdb, ovnkube-master, ovn-dbchecker
59-
1c57
60-
Name: OVN_Northbound
61-
Cluster ID: c48a (c48aa5c0-a704-4c77-a066-24fe99d9b338)
62-
Server ID: 1c57 (1c57b6fc-2849-49b7-8679-fbf18bafe339)
63-
Address: ssl:10.0.147.219:9643
64-
Status: cluster member
65-
Role: follower <1>
66-
Term: 5
67-
Leader: 2b4f <2>
68-
Vote: unknown
69-
70-
Election timer: 10000
71-
Log: [2, 3018]
72-
Entries not yet committed: 0
73-
Entries not yet applied: 0
74-
Connections: ->0000 ->0000 <-8844 <-2b4f
75-
Disconnections: 0
76-
Servers:
77-
1c57 (1c57 at ssl:10.0.147.219:9643) (self)
78-
8844 (8844 at ssl:10.0.163.212:9643) last msg 8928047 ms ago
79-
2b4f (2b4f at ssl:10.0.242.240:9643) last msg 620 ms ago <3>
80-
----
81-
+
82-
<1> This pod is identified as a follower
83-
<2> The leader is identified as `2b4f`
84-
<3> The `2b4f` is on IP address `10.0.242.240`
85-
86-
.. Find the `ovnkube-master` pod running on IP Address `10.0.242.240` using the following command:
87-
+
88-
[source,terminal]
89-
----
90-
$ oc get po -o wide -n openshift-ovn-kubernetes | grep 10.0.242.240 | grep -v ovnkube-node
55+
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
56+
ovnkube-control-plane-8444dff7f9-4lh9k 2/2 Running 0 27m 10.0.0.3 ci-ln-t487nnb-72292-mdcnq-master-1 <none> <none>
57+
ovnkube-control-plane-8444dff7f9-5rjh9 2/2 Running 0 27m 10.0.0.4 ci-ln-t487nnb-72292-mdcnq-master-2 <none> <none>
58+
ovnkube-control-plane-8444dff7f9-k64b7 2/2 Running 2 (12m ago) 27m 10.0.0.5 ci-ln-t487nnb-72292-mdcnq-master-0 <none> <none>
59+
ovnkube-node-55xs2 8/8 Running 0 26m 10.0.0.4 ci-ln-t487nnb-72292-mdcnq-master-2 <none> <none>
60+
ovnkube-node-7r84r 8/8 Running 0 17m 10.0.128.3 ci-ln-t487nnb-72292-mdcnq-worker-b-wbz7z <none> <none>
61+
ovnkube-node-bqq8p 8/8 Running 0 17m 10.0.128.2 ci-ln-t487nnb-72292-mdcnq-worker-a-lh7ms <none> <none>
62+
ovnkube-node-mkj4f 8/8 Running 0 27m 10.0.0.5 ci-ln-t487nnb-72292-mdcnq-master-0 <none> <none>
63+
ovnkube-node-mlr8k 8/8 Running 0 27m 10.0.0.3 ci-ln-t487nnb-72292-mdcnq-master-1 <none> <none>
64+
ovnkube-node-wqn2m 8/8 Running 0 17m 10.0.128.4 ci-ln-t487nnb-72292-mdcnq-worker-c-przlm <none> <none>
9165
----
66+
67+
. Navigate into a pod to look at the northbound database by running the following command:
9268
+
93-
.Example output
9469
[source,terminal]
9570
----
96-
ovnkube-master-gt4ms 6/6 Running 1 (143m ago) 150m 10.0.242.240 ip-10-0-242-240.ec2.internal <none> <none>
71+
$ oc rsh -c nbdb -n openshift-ovn-kubernetes ovnkube-node-55xs2
9772
----
98-
+
99-
The `ovnkube-master-gt4ms` pod runs on IP Address 10.0.242.240.
10073

10174
. Run the following command to show all the objects in the northbound database:
10275
+
10376
[source,terminal]
10477
----
105-
$ oc exec -n openshift-ovn-kubernetes -it ovnkube-master-gt4ms \
106-
-c northd -- ovn-nbctl show
78+
$ ovn-nbctl show
10779
----
10880
+
10981
The output is too long to list here. The list includes the NAT rules, logical switches, load balancers and so on.
11082
+
111-
Run the following command to display the options available with the command `ovn-nbctl`:
112-
+
113-
[source,terminal]
114-
----
115-
$ oc exec -n openshift-ovn-kubernetes -it ovnkube-master-mk6p6 \
116-
-c northd ovn-nbctl --help
117-
----
118-
+
119-
You can narrow down and focus on specific components by using some of the following commands:
83+
You can narrow down and focus on specific components by using some of the following optional commands:
12084

121-
. Run the following command to show the list of logical routers:
85+
.. Run the following command to show the list of logical routers:
12286
+
12387
[source,terminal]
12488
----
125-
$ oc exec -n openshift-ovn-kubernetes -it ovnkube-master-gt4ms \
89+
$ oc exec -n openshift-ovn-kubernetes -it ovnkube-node-55xs2 \
12690
-c northd -- ovn-nbctl lr-list
12791
----
12892
+
12993
.Example output
13094
[source,terminal]
13195
----
132-
f971f1f3-5112-402f-9d1e-48f1d091ff04 (GR_ip-10-0-145-205.ec2.internal)
133-
69c992d8-a4cf-429e-81a3-5361209ffe44 (GR_ip-10-0-147-219.ec2.internal)
134-
7d164271-af9e-4283-b84a-48f2a44851cd (GR_ip-10-0-163-212.ec2.internal)
135-
111052e3-c395-408b-97b2-8dd0a20a29a5 (GR_ip-10-0-165-9.ec2.internal)
136-
ed50ce33-df5d-48e8-8862-2df6a59169a0 (GR_ip-10-0-209-170.ec2.internal)
137-
f44e2a96-8d1e-4a4d-abae-ed8728ac6851 (GR_ip-10-0-242-240.ec2.internal)
138-
ef3d0057-e557-4b1a-b3c6-fcc3463790b0 (ovn_cluster_router)
96+
45339f4f-7d0b-41d0-b5f9-9fca9ce40ce6 (GR_ci-ln-t487nnb-72292-mdcnq-master-2)
97+
96a0a0f0-e7ed-4fec-8393-3195563de1b8 (ovn_cluster_router)
13998
----
14099
+
141100
[NOTE]
142101
====
143102
From this output you can see there is router on each node plus an `ovn_cluster_router`.
144103
====
145104

146-
. Run the following command to show the list of logical switches:
105+
.. Run the following command to show the list of logical switches:
147106
+
148107
[source,terminal]
149108
----
150-
$ oc exec -n openshift-ovn-kubernetes -it ovnkube-master-gt4ms \
151-
-c northd -- ovn-nbctl ls-list
109+
$ oc exec -n openshift-ovn-kubernetes -it ovnkube-node-55xs2 \
110+
-c nbdb -- ovn-nbctl ls-list
152111
----
153112
+
154113
.Example output
155114
[source,terminal]
156115
----
157-
82808c5c-b3bc-414a-bb59-8fec4b07eb14 (ext_ip-10-0-145-205.ec2.internal)
158-
3d22444f-0272-4c51-afc6-de9e03db3291 (ext_ip-10-0-147-219.ec2.internal)
159-
bf73b9df-59ab-4c58-a456-ce8205b34ac5 (ext_ip-10-0-163-212.ec2.internal)
160-
bee1e8d0-ec87-45eb-b98b-63f9ec213e5e (ext_ip-10-0-165-9.ec2.internal)
161-
812f08f2-6476-4abf-9a78-635f8516f95e (ext_ip-10-0-209-170.ec2.internal)
162-
f65e710b-32f9-482b-8eab-8d96a44799c1 (ext_ip-10-0-242-240.ec2.internal)
163-
84dad700-afb8-4129-86f9-923a1ddeace9 (ip-10-0-145-205.ec2.internal)
164-
1b7b448b-e36c-4ca3-9f38-4a2cf6814bfd (ip-10-0-147-219.ec2.internal)
165-
d92d1f56-2606-4f23-8b6a-4396a78951de (ip-10-0-163-212.ec2.internal)
166-
6864a6b2-de15-4de3-92d8-f95014b6f28f (ip-10-0-165-9.ec2.internal)
167-
c26bf618-4d7e-4afd-804f-1a2cbc96ec6d (ip-10-0-209-170.ec2.internal)
168-
ab9a4526-44ed-4f82-ae1c-e20da04947d9 (ip-10-0-242-240.ec2.internal)
169-
a8588aba-21da-4276-ba0f-9d68e88911f0 (join)
116+
bdd7dc3d-d848-4a74-b293-cc15128ea614 (ci-ln-t487nnb-72292-mdcnq-master-2)
117+
b349292d-ee03-4914-935f-1940b6cb91e5 (ext_ci-ln-t487nnb-72292-mdcnq-master-2)
118+
0aac0754-ea32-4e33-b086-35eeabf0a140 (join)
119+
992509d7-2c3f-4432-88db-c179e43592e5 (transit_switch)
170120
----
171121
+
172122
[NOTE]
173123
====
174124
From this output you can see there is an ext switch for each node plus switches with the node name itself and a join switch.
175125
====
176126

177-
. Run the following command to show the list of load balancers:
127+
.. Run the following command to show the list of load balancers:
178128
+
179129
[source,terminal]
180130
----
181-
$ oc exec -n openshift-ovn-kubernetes -it ovnkube-master-gt4ms \
182-
-c northd -- ovn-nbctl lb-list
131+
$ oc exec -n openshift-ovn-kubernetes -it ovnkube-node-55xs2 \
132+
-c nbdb -- ovn-nbctl lb-list
183133
----
184134
+
185135
.Example output
186136
[source,terminal]
187137
----
188138
UUID LB PROTO VIP IPs
189-
f0fb50f9-4968-4b55-908c-616bae4db0a2 Service_default/ tcp 172.30.0.1:443 10.0.147.219:6443,10.0.163.212:6443,169.254.169.2:6443
190-
0dc42012-4f5b-432e-ae01-2cc4bfe81b00 Service_default/ tcp 172.30.0.1:443 10.0.147.219:6443,169.254.169.2:6443,10.0.242.240:6443
191-
f7fff5d5-5eff-4a40-98b1-3a4ba8f7f69c Service_default/ tcp 172.30.0.1:443 169.254.169.2:6443,10.0.163.212:6443,10.0.242.240:6443
192-
12fe57a0-50a4-4a1b-ac10-5f288badee07 Service_default/ tcp 172.30.0.1:443 10.0.147.219:6443,10.0.163.212:6443,10.0.242.240:6443
193-
3f137fbf-0b78-4875-ba44-fbf89f254cf7 Service_openshif tcp 172.30.23.153:443 10.130.0.14:8443
194-
174199fe-0562-4141-b410-12094db922a7 Service_openshif tcp 172.30.69.51:50051 10.130.0.84:50051
195-
5ee2d4bd-c9e2-4d16-a6df-f54cd17c9ac3 Service_openshif tcp 172.30.143.87:9001 10.0.145.205:9001,10.0.147.219:9001,10.0.163.212:9001,10.0.165.9:9001,10.0.209.170:9001,10.0.242.240:9001
196-
a056ae3d-83f8-45bc-9c80-ef89bce7b162 Service_openshif tcp 172.30.164.74:443 10.0.147.219:6443,10.0.163.212:6443,10.0.242.240:6443
197-
bac51f3d-9a6f-4f5e-ac02-28fd343a332a Service_openshif tcp 172.30.0.10:53 10.131.0.6:5353
198-
tcp 172.30.0.10:9154 10.131.0.6:9154
199-
48105bbc-51d7-4178-b975-417433f9c20a Service_openshif tcp 172.30.26.159:2379 10.0.147.219:2379,169.254.169.2:2379,10.0.242.240:2379
200-
tcp 172.30.26.159:9979 10.0.147.219:9979,169.254.169.2:9979,10.0.242.240:9979
201-
7de2b8fc-342a-415f-ac13-1a493f4e39c0 Service_openshif tcp 172.30.53.219:443 10.128.0.7:8443
202-
tcp 172.30.53.219:9192 10.128.0.7:9192
203-
2cef36bc-d720-4afb-8d95-9350eff1d27a Service_openshif tcp 172.30.81.66:443 10.128.0.23:8443
204-
365cb6fb-e15e-45a4-a55b-21868b3cf513 Service_openshif tcp 172.30.96.51:50051 10.130.0.19:50051
205-
41691cbb-ec55-4cdb-8431-afce679c5e8d Service_openshif tcp 172.30.98.218:9099 169.254.169.2:9099
206-
82df10ba-8143-400b-977a-8f5f416a4541 Service_openshif tcp 172.30.26.159:2379 10.0.147.219:2379,10.0.163.212:2379,169.254.169.2:2379
207-
tcp 172.30.26.159:9979 10.0.147.219:9979,10.0.163.212:9979,169.254.169.2:9979
208-
debe7f3a-39a8-490e-bc0a-ebbfafdffb16 Service_openshif tcp 172.30.23.244:443 10.128.0.48:8443,10.129.0.27:8443,10.130.0.45:8443
209-
8a749239-02d9-4dc2-8737-716528e0da7b Service_openshif tcp 172.30.124.255:8443 10.128.0.14:8443
210-
880c7c78-c790-403d-a3cb-9f06592717a3 Service_openshif tcp 172.30.0.10:53 10.130.0.20:5353
211-
tcp 172.30.0.10:9154 10.130.0.20:9154
212-
d2f39078-6751-4311-a161-815bbaf7f9c7 Service_openshif tcp 172.30.26.159:2379 169.254.169.2:2379,10.0.163.212:2379,10.0.242.240:2379
213-
tcp 172.30.26.159:9979 169.254.169.2:9979,10.0.163.212:9979,10.0.242.240:9979
214-
30948278-602b-455c-934a-28e64c46de12 Service_openshif tcp 172.30.157.35:9443 10.130.0.43:9443
215-
2cc7e376-7c02-4a82-89e8-dfa1e23fb003 Service_openshif tcp 172.30.159.212:17698 10.128.0.48:17698,10.129.0.27:17698,10.130.0.45:17698
216-
e7d22d35-61c2-40c2-bc30-265cff8ed18d Service_openshif tcp 172.30.143.87:9001 10.0.145.205:9001,10.0.147.219:9001,10.0.163.212:9001,10.0.165.9:9001,10.0.209.170:9001,169.254.169.2:9001
217-
75164e75-e0c5-40fb-9636-bfdbf4223a02 Service_openshif tcp 172.30.150.68:1936 10.129.4.8:1936,10.131.0.10:1936
218-
tcp 172.30.150.68:443 10.129.4.8:443,10.131.0.10:443
219-
tcp 172.30.150.68:80 10.129.4.8:80,10.131.0.10:80
220-
7bc4ee74-dccf-47e9-9149-b011f09aff39 Service_openshif tcp 172.30.164.74:443 10.0.147.219:6443,10.0.163.212:6443,169.254.169.2:6443
221-
0db59e74-1cc6-470c-bf44-57c520e0aa8f Service_openshif tcp 10.0.163.212:31460
222-
tcp 10.0.163.212:32361
223-
c300e134-018c-49af-9f84-9deb1d0715f8 Service_openshif tcp 172.30.42.244:50051 10.130.0.47:50051
224-
5e352773-429b-4881-afb3-a13b7ba8b081 Service_openshif tcp 172.30.244.66:443 10.129.0.8:8443,10.130.0.8:8443
225-
54b82d32-1939-4465-a87d-f26321442a7a Service_openshif tcp 172.30.12.9:8443 10.128.0.35:8443
139+
7c84c673-ed2a-4436-9a1f-9bc5dd181eea Service_default/ tcp 172.30.0.1:443 10.0.0.3:6443,169.254.169.2:6443,10.0.0.5:6443
140+
4d663fd9-ddc8-4271-b333-4c0e279e20bb Service_default/ tcp 172.30.0.1:443 10.0.0.3:6443,10.0.0.4:6443,10.0.0.5:6443
141+
292eb07f-b82f-4962-868a-4f541d250bca Service_openshif tcp 172.30.105.247:443 10.129.0.12:8443
142+
034b5a7f-bb6a-45e9-8e6d-573a82dc5ee3 Service_openshif tcp 172.30.192.38:443 10.0.0.3:10259,10.0.0.4:10259,10.0.0.5:10259
143+
a68bb53e-be84-48df-bd38-bdd82fcd4026 Service_openshif tcp 172.30.161.125:8443 10.129.0.32:8443
144+
6cc21b3d-2c54-4c94-8ff5-d8e017269c2e Service_openshif tcp 172.30.3.144:443 10.129.0.22:8443
145+
37996ffd-7268-4862-a27f-61cd62e09c32 Service_openshif tcp 172.30.181.107:443 10.129.0.18:8443
146+
81d4da3c-f811-411f-ae0c-bc6713d0861d Service_openshif tcp 172.30.228.23:443 10.129.0.29:8443
147+
ac5a4f3b-b6ba-4ceb-82d0-d84f2c41306e Service_openshif tcp 172.30.14.240:9443 10.129.0.36:9443
148+
c88979fb-1ef5-414b-90ac-43b579351ac9 Service_openshif tcp 172.30.231.192:9001 10.128.0.5:9001,10.128.2.5:9001,10.129.0.5:9001,10.129.2.4:9001,10.130.0.3:9001,10.131.0.3:9001
149+
fcb0a3fb-4a77-4230-a84a-be45dce757e8 Service_openshif tcp 172.30.189.92:443 10.130.0.17:8440
150+
67ef3e7b-ceb9-4bf0-8d96-b43bde4c9151 Service_openshif tcp 172.30.67.218:443 10.129.0.9:8443
151+
d0032fba-7d5e-424a-af25-4ab9b5d46e81 Service_openshif tcp 172.30.102.137:2379 10.0.0.3:2379,10.0.0.4:2379,10.0.0.5:2379
152+
tcp 172.30.102.137:9979 10.0.0.3:9979,10.0.0.4:9979,10.0.0.5:9979
153+
7361c537-3eec-4e6c-bc0c-0522d182abd4 Service_openshif tcp 172.30.198.215:9001 10.0.0.3:9001,10.0.0.4:9001,10.0.0.5:9001,10.0.128.2:9001,10.0.128.3:9001,10.0.128.4:9001
154+
0296c437-1259-410b-a6fd-81c310ad0af5 Service_openshif tcp 172.30.198.215:9001 10.0.0.3:9001,169.254.169.2:9001,10.0.0.5:9001,10.0.128.2:9001,10.0.128.3:9001,10.0.128.4:9001
155+
5d5679f5-45b8-479d-9f7c-08b123c688b8 Service_openshif tcp 172.30.38.253:17698 10.128.0.52:17698,10.129.0.84:17698,10.130.0.60:17698
156+
2adcbab4-d1c9-447d-9573-b5dc9f2efbfa Service_openshif tcp 172.30.148.52:443 10.0.0.4:9202,10.0.0.5:9202
157+
tcp 172.30.148.52:444 10.0.0.4:9203,10.0.0.5:9203
158+
tcp 172.30.148.52:445 10.0.0.4:9204,10.0.0.5:9204
159+
tcp 172.30.148.52:446 10.0.0.4:9205,10.0.0.5:9205
160+
2a33a6d7-af1b-4892-87cc-326a380b809b Service_openshif tcp 172.30.67.219:9091 10.129.2.16:9091,10.131.0.16:9091
161+
tcp 172.30.67.219:9092 10.129.2.16:9092,10.131.0.16:9092
162+
tcp 172.30.67.219:9093 10.129.2.16:9093,10.131.0.16:9093
163+
tcp 172.30.67.219:9094 10.129.2.16:9094,10.131.0.16:9094
164+
f56f59d7-231a-4974-99b3-792e2741ec8d Service_openshif tcp 172.30.89.212:443 10.128.0.41:8443,10.129.0.68:8443,10.130.0.44:8443
165+
08c2c6d7-d217-4b96-b5d8-c80c4e258116 Service_openshif tcp 172.30.102.137:2379 10.0.0.3:2379,169.254.169.2:2379,10.0.0.5:2379
166+
tcp 172.30.102.137:9979 10.0.0.3:9979,169.254.169.2:9979,10.0.0.5:9979
167+
60a69c56-fc6a-4de6-bd88-3f2af5ba5665 Service_openshif tcp 172.30.10.193:443 10.129.0.25:8443
168+
ab1ef694-0826-4671-a22c-565fc2d282ec Service_openshif tcp 172.30.196.123:443 10.128.0.33:8443,10.129.0.64:8443,10.130.0.37:8443
169+
b1fb34d3-0944-4770-9ee3-2683e7a630e2 Service_openshif tcp 172.30.158.93:8443 10.129.0.13:8443
170+
95811c11-56e2-4877-be1e-c78ccb3a82a9 Service_openshif tcp 172.30.46.85:9001 10.130.0.16:9001
171+
4baba1d1-b873-4535-884c-3f6fc07a50fd Service_openshif tcp 172.30.28.87:443 10.129.0.26:8443
172+
6c2e1c90-f0ca-484e-8a8e-40e71442110a Service_openshif udp 172.30.0.10:53 10.128.0.13:5353,10.128.2.6:5353,10.129.0.39:5353,10.129.2.6:5353,10.130.0.11:5353,10.131.0.9:5353
173+
226174
----
227175
+
228176
[NOTE]
229177
====
230178
From this truncated output you can see there are many OVN-Kubernetes load balancers. Load balancers in OVN-Kubernetes are representations of services.
231179
====
232180

233-
181+
. Run the following command to display the options available with the command `ovn-nbctl`:
182+
+
183+
[source,terminal]
184+
----
185+
$ oc exec -n openshift-ovn-kubernetes -it ovnkube-node-55xs2 \
186+
-c nbdb ovn-nbctl --help
187+
----

0 commit comments

Comments
 (0)