Skip to content

Commit

Permalink
Remove equals from heading which breaks our links.
Browse files Browse the repository at this point in the history
  • Loading branch information
erictune committed Jul 20, 2015
1 parent b4fb938 commit 844c823
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/user-guide/services.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,8 +49,8 @@ Documentation for other releases can be found at
- [DNS](#dns)
- [Headless services](#headless-services)
- [External services](#external-services)
- [Type = NodePort](#type--nodeport)
- [Type = LoadBalancer](#type--loadbalancer)
- [Type NodePort](#type-nodeport)
- [Type LoadBalancer](#type-loadbalancer)
- [Shortcomings](#shortcomings)
- [Future work](#future-work)
- [The gory details of virtual IPs](#the-gory-details-of-virtual-ips)
Expand Down Expand Up @@ -375,7 +375,7 @@ accessed. Valid values for this field are:
Note that while `NodePort`s can be TCP or UDP, `LoadBalancer`s only support TCP
as of Kubernetes 1.0.

### Type = NodePort
### Type NodePort

If you set the `type` field to `"NodePort"`, the Kubernetes master will
allocate a port from a flag-configured range (default: 30000-32767), and each
Expand All @@ -391,7 +391,7 @@ This gives developers the freedom to set up their own load balancers, to
configure cloud environments that are not fully supported by Kubernetes, or
even to just expose one or more nodes' IPs directly.

### Type = LoadBalancer
### Type LoadBalancer

On cloud providers which support external load balancers, setting the `type`
field to `"LoadBalancer"` will provision a load balancer for your `Service`.
Expand Down

0 comments on commit 844c823

Please sign in to comment.