Hugo: Fix lists (#8511)
Fix display of lists, add empty lines before them so that hugo formats them correctly as lists and not as paragraphs.
This commit is contained in:
committed by
k8s-ci-robot
parent
c2f73e5862
commit
ed3fc99154
@@ -219,6 +219,7 @@ endpoints. You can switch to the new reconciler by adding the flag
|
||||
{{< feature-state state="alpha" >}}
|
||||
|
||||
If you want to know more, you can check the following resources:
|
||||
|
||||
- [issue kubernetes/kubernetes#22609](https://github.com/kubernetes/kubernetes/issues/22609),
|
||||
which gives additional context
|
||||
- [master/reconcilers/mastercount.go](https://github.com/kubernetes/kubernetes/blob/dd9981d038012c120525c9e6df98b3beb3ef19e1/pkg/master/reconcilers/mastercount.go#L63),
|
||||
|
||||
@@ -117,6 +117,7 @@ This section breaks down the access required on various API objects by the CCM t
|
||||
The Node controller only works with Node objects. It requires full access to get, list, create, update, patch, watch, and delete Node objects.
|
||||
|
||||
v1/Node:
|
||||
|
||||
- Get
|
||||
- List
|
||||
- Create
|
||||
@@ -130,6 +131,7 @@ v1/Node:
|
||||
The route controller listens to Node object creation and configures routes appropriately. It requires get access to Node objects.
|
||||
|
||||
v1/Node:
|
||||
|
||||
- Get
|
||||
|
||||
### Service controller
|
||||
@@ -141,6 +143,7 @@ To access Services, it requires list, and watch access. To update Services, it r
|
||||
To set up endpoints for the Services, it requires access to create, list, get, watch, and update.
|
||||
|
||||
v1/Service:
|
||||
|
||||
- List
|
||||
- Get
|
||||
- Watch
|
||||
@@ -152,6 +155,7 @@ v1/Service:
|
||||
The PersistentVolumeLabels controller listens on PersistentVolume (PV) create events and then updates them. This controller requires access to get and update PVs.
|
||||
|
||||
v1/PersistentVolume:
|
||||
|
||||
- Get
|
||||
- List
|
||||
- Watch
|
||||
@@ -162,11 +166,13 @@ v1/PersistentVolume:
|
||||
The implementation of the core of CCM requires access to create events, and to ensure secure operation, it requires access to create ServiceAccounts.
|
||||
|
||||
v1/Event:
|
||||
|
||||
- Create
|
||||
- Patch
|
||||
- Update
|
||||
|
||||
v1/ServiceAccount:
|
||||
|
||||
- Create
|
||||
|
||||
The RBAC ClusterRole for the CCM looks like this:
|
||||
|
||||
Reference in New Issue
Block a user