Fix broken links. (#9755)
- /docs/concepts/services-networking/service/#type-nodeport => /docs/concepts/services-networking/service/#nodeport - /docs/concepts/services-networking/service/#type-loadbalancer => /docs/concepts/services-networking/service/#loadbalancer - https://github.com/kubernetes/ingress-nginx/blob/master/docs/ingress-controller-catalog.md => https://github.com/kubernetes/ingress-nginx/
This commit is contained in:
committed by
k8s-ci-robot
parent
8c02f4caa4
commit
5f19d7ced8
@@ -138,7 +138,7 @@ underlying Kubernetes services (once these have been allocated - this
|
||||
may take a few seconds). For inter-cluster and inter-cloud-provider
|
||||
networking between service shards to work correctly, your services
|
||||
need to have an externally visible IP address. [Service Type:
|
||||
Loadbalancer](/docs/concepts/services-networking/service/#type-loadbalancer)
|
||||
Loadbalancer](/docs/concepts/services-networking/service/#loadbalancer)
|
||||
is typically used for this, although other options
|
||||
(e.g. [External IP's](/docs/concepts/services-networking/service/#external-ips)) exist.
|
||||
|
||||
|
||||
@@ -279,11 +279,11 @@ kubefed init fellowship \
|
||||
`kubefed init` exposes the federation API server as a Kubernetes
|
||||
[service](/docs/concepts/services-networking/service/) on the host cluster. By default,
|
||||
this service is exposed as a
|
||||
[load balanced service](/docs/concepts/services-networking/service/#type-loadbalancer).
|
||||
[load balanced service](/docs/concepts/services-networking/service/#loadbalancer).
|
||||
Most on-premises and bare-metal environments, and some cloud
|
||||
environments lack support for load balanced services. `kubefed init`
|
||||
allows exposing the federation API server as a
|
||||
[`NodePort` service](/docs/concepts/services-networking/service/#type-nodeport) on
|
||||
[`NodePort` service](/docs/concepts/services-networking/service/#nodeport) on
|
||||
such environments. This can be accomplished by passing
|
||||
the `--api-server-service-type=NodePort` flag. You can also specify
|
||||
the preferred address to advertise the federation API server by
|
||||
|
||||
Reference in New Issue
Block a user