File tree Expand file tree Collapse file tree 3 files changed +10
-9
lines changed
setup/production-environment/tools/kubeadm
access-application-cluster Expand file tree Collapse file tree 3 files changed +10
-9
lines changed Original file line number Diff line number Diff line change @@ -9,7 +9,7 @@ weight: 50
9
9
---
10
10
reviewers:
11
11
- sig-cluster-lifecycle
12
- title: Options for Highly Available topology
12
+ title: Options for Highly Available Topology
13
13
content_type: concept
14
14
weight: 50
15
15
---
Original file line number Diff line number Diff line change @@ -357,13 +357,13 @@ The following manifest defines an Ingress that sends traffic to your Service via
357
357
358
358
359
359
``` yaml
360
- - path : /v2
361
- pathType : Prefix
362
- backend :
363
- service :
364
- name : web2
365
- port :
366
- number : 8080
360
+ - path : /v2
361
+ pathType : Prefix
362
+ backend :
363
+ service :
364
+ name : web2
365
+ port :
366
+ number : 8080
367
367
` ` `
368
368
369
369
<!--
Original file line number Diff line number Diff line change @@ -93,7 +93,8 @@ Kubernetes API 服务器。也就是说,Pod 可以使用 `kubernetes.default.s
93
93
94
94
<!--
95
95
The recommended way to authenticate to the API server is with a
96
- [service account](/docs/tasks/configure-pod-container/configure-service-account/) credential. By default, a Pod
96
+ [service account](/docs/tasks/configure-pod-container/configure-service-account/)
97
+ credential. By default, a Pod
97
98
is associated with a service account, and a credential (token) for that
98
99
service account is placed into the filesystem tree of each container in that Pod,
99
100
at `/var/run/secrets/kubernetes.io/serviceaccount/token`.
You can’t perform that action at this time.
0 commit comments