Fixed link rendering issue due to newline location
A newline between `[]` and `()` caused markdown rendering issues when parsed with `kramdown` (Jekyll's markdown parser) strangely enough this was not present on github.com but only on kubernetes.io. This change moves the newline between _in_ and `rkt.go` to preserve the line length somewhat.
This commit is contained in:
@@ -22,8 +22,8 @@ must be running on the node.
|
||||
|
||||
rkt uses the [Container Network Interface (CNI)](https://github.com/appc/cni)
|
||||
to manage container networking. By default, all pods attempt to join a network
|
||||
called `rkt.kubernetes.io`, which is currently defined [in `rkt.go`]
|
||||
(https://github.com/kubernetes/kubernetes/blob/v1.2.0-alpha.6/pkg/kubelet/rkt/rkt.go#L91).
|
||||
called `rkt.kubernetes.io`, which is currently defined [in
|
||||
`rkt.go`](https://github.com/kubernetes/kubernetes/blob/v1.2.0-alpha.6/pkg/kubelet/rkt/rkt.go#L91).
|
||||
In order for pods to get correct IP addresses, the CNI config file must be
|
||||
edited to add this `rkt.kubernetes.io` network:
|
||||
|
||||
@@ -216,4 +216,4 @@ where `$UUID` is the rkt pod's UUID, which you can find via `rkt list --full`, a
|
||||
|
||||
##### Check Kubernetes events, logs.
|
||||
|
||||
Besides above tricks, Kubernetes also provides us handy tools for debugging the pods. More information can be found [here](/docs/user-guide/application-troubleshooting)
|
||||
Besides above tricks, Kubernetes also provides us handy tools for debugging the pods. More information can be found [here](/docs/user-guide/application-troubleshooting)
|
||||
|
||||
Reference in New Issue
Block a user