mirror of
https://github.com/kubernetes-sigs/kubespray.git
synced 2026-02-28 09:39:12 +03:00
Fix markdownlint failures under ./roles/ (#7089)
This fixes markdownlint failures under roles/
This commit is contained in:
@@ -24,7 +24,7 @@ whether the registry is run or not. To set this flag, you can specify
|
||||
does not include this flag, the following steps should work. Note that some of
|
||||
this is cloud-provider specific, so you may have to customize it a bit.
|
||||
|
||||
### Make some storage
|
||||
- Make some storage
|
||||
|
||||
The primary job of the registry is to store data. To do that we have to decide
|
||||
where to store it. For cloud environments that have networked storage, we can
|
||||
@@ -58,7 +58,7 @@ If, for example, you wanted to use NFS you would just need to change the
|
||||
Note that in any case, the storage (in the case the GCE PersistentDisk) must be
|
||||
created independently - this is not something Kubernetes manages for you (yet).
|
||||
|
||||
### I don't want or don't have persistent storage
|
||||
- I don't want or don't have persistent storage
|
||||
|
||||
If you are running in a place that doesn't have networked storage, or if you
|
||||
just want to kick the tires on this without committing to it, you can easily
|
||||
@@ -260,13 +260,13 @@ Now you can build and push images on your local computer as
|
||||
your kubernetes cluster with the same name.
|
||||
|
||||
More Extensions
|
||||
===============
|
||||
---------------
|
||||
|
||||
- [Use GCS as storage backend](gcs/README.md)
|
||||
- [Enable TLS/SSL](tls/README.md)
|
||||
- [Enable Authentication](auth/README.md)
|
||||
- [Use GCS as storage backend](gcs/README.md)
|
||||
- [Enable TLS/SSL](tls/README.md)
|
||||
- [Enable Authentication](auth/README.md)
|
||||
|
||||
Future improvements
|
||||
-------------------
|
||||
|
||||
- Allow port-forwarding to a Service rather than a pod (\#15180)
|
||||
- Allow port-forwarding to a Service rather than a pod (\#15180)
|
||||
|
||||
Reference in New Issue
Block a user