Skip to content

Commit cf21ccf

Browse files
author
mikemckiernan
authored
Merge pull request #34635 from mikemckiernan/feat-gloss-metallb
OSDOCS-2174: MetalLB glossary entry
2 parents bfe2615 + b9e27e9 commit cf21ccf

File tree

1 file changed

+12
-3
lines changed

1 file changed

+12
-3
lines changed

contributing_to_docs/term_glossary.adoc

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -299,7 +299,7 @@ load balancing and proxy layer via a public DNS entry. The Ingress resource may
299299
further specify TLS options and a certificate, or specify a public CNAME that
300300
the OpenShift Ingress Controller should also accept for HTTP and HTTPS traffic.
301301
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
303303
traffic controls on the service content.
304304

305305
''''
@@ -352,6 +352,15 @@ Usage: Kubernetes API server
352352

353353
== M
354354

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+
355364
''''
356365
=== minion
357366

@@ -547,10 +556,10 @@ Usage: route(s)
547556

548557
OpenShift-specific API object that allows developers to expose services through
549558
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
551560
CNAME that the OpenShift Ingress Controller should also accept for HTTP and
552561
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,
554563
caching, or traffic controls on the service content.
555564

556565
== S

0 commit comments

Comments
 (0)