You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add a glossary entry for MetalLB and state
the accepted usage.
* s/may/might/ and s/their/an/ in two spots
because it was flagged by textlint.
Helpful feedback from Max.
Copy file name to clipboardExpand all lines: contributing_to_docs/term_glossary.adoc
+12-3Lines changed: 12 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -299,7 +299,7 @@ load balancing and proxy layer via a public DNS entry. The Ingress resource may
299
299
further specify TLS options and a certificate, or specify a public CNAME that
300
300
the OpenShift Ingress Controller should also accept for HTTP and HTTPS traffic.
301
301
An administrator typically configures their Ingress Controller to be visible
302
-
outside the cluster firewall, and may also add additional security, caching, or
302
+
outside the cluster firewall, and might also add additional security, caching, or
303
303
traffic controls on the service content.
304
304
305
305
''''
@@ -352,6 +352,15 @@ Usage: Kubernetes API server
352
352
353
353
== M
354
354
355
+
''''
356
+
=== MetalLB
357
+
358
+
Usage: MetalLB, MetalLB Operator, MetalLB project
359
+
360
+
MetalLB is an open source project that provides a way to add services of type `LoadBalancer` to clusters that are not installed on infrastructure from a cloud provider. MetalLB primarily targets on-premise, bare-metal clusters, but any infrastructure that does not include a native load-balancing capability is a candidate.
361
+
362
+
"MetalLB" always has the first letter and last two letters capitalized in general text. Do not use "Metallb."
363
+
355
364
''''
356
365
=== minion
357
366
@@ -547,10 +556,10 @@ Usage: route(s)
547
556
548
557
OpenShift-specific API object that allows developers to expose services through
549
558
an HTTP(S) aware load balancing and proxy layer via a public DNS entry. The
550
-
route may further specify TLS options and a certificate, or specify a public
559
+
route might further specify TLS options and a certificate, or specify a public
551
560
CNAME that the OpenShift Ingress Controller should also accept for HTTP and
552
561
HTTPS traffic. An administrator typically configures their Ingress Controller to
553
-
be visible outside the cluster firewall, and may also add additional security,
562
+
be visible outside the cluster firewall, and might also add additional security,
554
563
caching, or traffic controls on the service content.
0 commit comments