Replace the tab with 4 spaces in md files (#2797)
* Replace the tab with 4 spaces in md files Signed-off-by: yupengzte <yu.peng36@zte.com.cn> * Fix typos of accessing-the-api.md Signed-off-by: yupengzte <yu.peng36@zte.com.cn> * Fix typos of manage-compute-resources-container.md Signed-off-by: yupengzte <yu.peng36@zte.com.cn> * Fix typos of run-to-completion-finite-workloads.md Signed-off-by: yupengzte <yu.peng36@zte.com.cn> * Fix typos of connect-applications-service.md Signed-off-by: yupengzte <yu.peng36@zte.com.cn> * Fix typos of init-containers.md Signed-off-by: yupengzte <yu.peng36@zte.com.cn> * Fix typos of calico.md Signed-off-by: yupengzte <yu.peng36@zte.com.cn> * Fix typos of ingress.md Signed-off-by: yupengzte <yu.peng36@zte.com.cn> * Fix typos of index.md Signed-off-by: yupengzte <yu.peng36@zte.com.cn> * Fix typos of index.md Signed-off-by: yupengzte <yu.peng36@zte.com.cn> * Fix typos of apparmor.md Signed-off-by: yupengzte <yu.peng36@zte.com.cn> * Fix typos of run-stateful-application.md Signed-off-by: yupengzte <yu.peng36@zte.com.cn> * Fix typos of index.md Signed-off-by: yupengzte <yu.peng36@zte.com.cn> * Fix typos of index.md Signed-off-by: yupengzte <yu.peng36@zte.com.cn> * Fix typos of replicasets.md Signed-off-by: yupengzte <yu.peng36@zte.com.cn>
This commit is contained in:
Andy Yu
@@ -63,7 +63,7 @@ users in its object store.
|
||||
|
||||
Once the request is authenticated as coming from a specific user,
|
||||
it moves to a generic authorization step. This is shown as step **2** in the
|
||||
diagram.
|
||||
diagram.
|
||||
|
||||
The input to the Authorization step are attributes of the REST request, including:
|
||||
- the username determined by the Authentication step.
|
||||
@@ -80,7 +80,7 @@ then the request can proceed. If all deny the request, then the request is deni
|
||||
code 403).
|
||||
|
||||
The [Authorization Modules](/docs/admin/authorization) page describes what authorization modules
|
||||
are available and how to configure them.
|
||||
are available and how to configure them.
|
||||
|
||||
For version 1.2, clusters created by `kube-up.sh` are configured so that no authorization is
|
||||
required for any request.
|
||||
@@ -108,7 +108,7 @@ They act on objects being created, deleted, updated or connected (proxy), but no
|
||||
|
||||
Multiple admission controllers can be configured. Each is called in order.
|
||||
|
||||
This is shown as step **3** in the diagram.
|
||||
This is shown as step **3** in the diagram.
|
||||
|
||||
Unlike Authentication and Authorization Modules, if any admission controller module
|
||||
rejects, then the request is immediately rejected.
|
||||
@@ -122,7 +122,7 @@ Once a request passes all admission controllers, it is validated using the valid
|
||||
for the corresponding API object, and then written to the object store (shown as step **4**).
|
||||
|
||||
|
||||
## API Server Ports and IPs
|
||||
## API Server Ports and IPs
|
||||
|
||||
The previous discussion applies to requests sent to the secure port of the API server
|
||||
(the typical case). The API server can actually serve on 2 ports:
|
||||
@@ -132,7 +132,7 @@ By default the Kubernetes API server serves HTTP on 2 ports:
|
||||
1. `Localhost Port`:
|
||||
|
||||
- is intended for testing and bootstrap, and for other components of the master node
|
||||
(scheduler, controller-manager) to talk to the API
|
||||
(scheduler, controller-manager) to talk to the API
|
||||
- no TLS
|
||||
- default is port 8080, change with `--insecure-port` flag.
|
||||
- defaults IP is localhost, change with `--insecure-bind-address` flag.
|
||||
@@ -141,7 +141,7 @@ By default the Kubernetes API server serves HTTP on 2 ports:
|
||||
- protected by need to have host access
|
||||
|
||||
2. `Secure Port`:
|
||||
|
||||
|
||||
- use whenever possible
|
||||
- uses TLS. Set cert with `--tls-cert-file` and key with `--tls-private-key-file` flag.
|
||||
- default is port 6443, change with `--secure-port` flag.
|
||||
|
||||
@@ -229,7 +229,7 @@ cross-zone attachments are not generally permitted by cloud providers:
|
||||
|
||||
```shell
|
||||
> kubectl describe pod mypod | grep Node
|
||||
Node: kubernetes-minion-9vlv/10.240.0.5
|
||||
Node: kubernetes-minion-9vlv/10.240.0.5
|
||||
> kubectl get node kubernetes-minion-9vlv --show-labels
|
||||
NAME STATUS AGE LABELS
|
||||
kubernetes-minion-9vlv Ready 22m beta.kubernetes.io/instance-type=n1-standard-2,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a,kubernetes.io/hostname=kubernetes-minion-9vlv
|
||||
@@ -268,9 +268,9 @@ The pods should be spread across all 3 zones:
|
||||
|
||||
```shell
|
||||
> kubectl describe pod -l app=guestbook | grep Node
|
||||
Node: kubernetes-minion-9vlv/10.240.0.5
|
||||
Node: kubernetes-minion-281d/10.240.0.8
|
||||
Node: kubernetes-minion-olsh/10.240.0.11
|
||||
Node: kubernetes-minion-9vlv/10.240.0.5
|
||||
Node: kubernetes-minion-281d/10.240.0.8
|
||||
Node: kubernetes-minion-olsh/10.240.0.11
|
||||
|
||||
> kubectl get node kubernetes-minion-9vlv kubernetes-minion-281d kubernetes-minion-olsh --show-labels
|
||||
NAME STATUS AGE LABELS
|
||||
|
||||
@@ -64,16 +64,16 @@ Or you can get detailed information with:
|
||||
|
||||
```shell
|
||||
$ kubectl describe namespaces <name>
|
||||
Name: default
|
||||
Labels: <none>
|
||||
Status: Active
|
||||
Name: default
|
||||
Labels: <none>
|
||||
Status: Active
|
||||
|
||||
No resource quota.
|
||||
|
||||
Resource Limits
|
||||
Type Resource Min Max Default
|
||||
---- -------- --- --- ---
|
||||
Container cpu - - 100m
|
||||
Type Resource Min Max Default
|
||||
---- -------- --- --- ---
|
||||
Container cpu - - 100m
|
||||
```
|
||||
|
||||
Note that these details show both resource quota (if present) as well as resource limit ranges.
|
||||
|
||||
Reference in New Issue
Block a user