Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit ecc27bb

Browse filesBrowse files
kbhawkeykbhawkey
committed
add en pages
1 parent 1502e02 commit ecc27bb
Copy full SHA for ecc27bb

File tree

Expand file treeCollapse file tree

347 files changed

+2900
-2537
lines changed
Open diff view settings
Filter options

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
Dismiss banner
Expand file treeCollapse file tree

347 files changed

+2900
-2537
lines changed
Open diff view settings
Collapse file

‎content/en/docs/concepts/_index.md‎

Copy file name to clipboardExpand all lines: content/en/docs/concepts/_index.md
+8-7Lines changed: 8 additions & 7 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
---
22
title: Concepts
33
main_menu: true
4-
content_template: templates/concept
4+
content_type: concept
55
weight: 40
66
---
77

8-
{{% capture overview %}}
8+
<!-- overview -->
99

1010
The Concepts section helps you learn about the parts of the Kubernetes system and the abstractions Kubernetes uses to represent your {{< glossary_tooltip text="cluster" term_id="cluster" length="all" >}}, and helps you obtain a deeper understanding of how Kubernetes works.
1111

12-
{{% /capture %}}
1312

14-
{{% capture body %}}
13+
14+
<!-- body -->
1515

1616
## Overview
1717

@@ -60,12 +60,13 @@ The Kubernetes master is responsible for maintaining the desired state for your
6060
The nodes in a cluster are the machines (VMs, physical servers, etc) that run your applications and cloud workflows. The Kubernetes master controls each node; you'll rarely interact with nodes directly.
6161

6262

63-
{{% /capture %}}
6463

65-
{{% capture whatsnext %}}
64+
65+
## {{% heading "whatsnext" %}}
66+
6667

6768
If you would like to write a concept page, see
6869
[Using Page Templates](/docs/home/contribute/page-templates/)
6970
for information about the concept page type and the concept template.
7071

71-
{{% /capture %}}
72+
Collapse file

‎content/en/docs/concepts/architecture/cloud-controller.md‎

Copy file name to clipboardExpand all lines: content/en/docs/concepts/architecture/cloud-controller.md
+7-7Lines changed: 7 additions & 7 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: Cloud Controller Manager
3-
content_template: templates/concept
3+
content_type: concept
44
weight: 40
55
---
66

7-
{{% capture overview %}}
7+
<!-- overview -->
88

99
{{< feature-state state="beta" for_k8s_version="v1.11" >}}
1010

@@ -17,9 +17,9 @@ components.
1717
The cloud-controller-manager is structured using a plugin
1818
mechanism that allows different cloud providers to integrate their platforms with Kubernetes.
1919

20-
{{% /capture %}}
2120

22-
{{% capture body %}}
21+
22+
<!-- body -->
2323

2424
## Design
2525

@@ -200,8 +200,9 @@ rules:
200200
- update
201201
```
202202
203-
{{% /capture %}}
204-
{{% capture whatsnext %}}
203+
204+
## {{% heading "whatsnext" %}}
205+
205206
[Cloud Controller Manager Administration](/docs/tasks/administer-cluster/running-cloud-controller/#cloud-controller-manager)
206207
has instructions on running and managing the cloud controller manager.
207208
@@ -212,4 +213,3 @@ The cloud controller manager uses Go interfaces to allow implementations from an
212213
The implementation of the shared controllers highlighted in this document (Node, Route, and Service), and some scaffolding along with the shared cloudprovider interface, is part of the Kubernetes core. Implementations specific to cloud providers are outside the core of Kubernetes and implement the `CloudProvider` interface.
213214

214215
For more information about developing plugins, see [Developing Cloud Controller Manager](/docs/tasks/administer-cluster/developing-cloud-controller-manager/).
215-
{{% /capture %}}
Collapse file

‎content/en/docs/concepts/architecture/control-plane-node-communication.md‎

Copy file name to clipboardExpand all lines: content/en/docs/concepts/architecture/control-plane-node-communication.md
+4-4Lines changed: 4 additions & 4 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -3,19 +3,19 @@ reviewers:
33
- dchen1107
44
- liggitt
55
title: Control Plane-Node Communication
6-
content_template: templates/concept
6+
content_type: concept
77
weight: 20
88
aliases:
99
- master-node-communication
1010
---
1111

12-
{{% capture overview %}}
12+
<!-- overview -->
1313

1414
This document catalogs the communication paths between the control plane (really the apiserver) and the Kubernetes cluster. The intent is to allow users to customize their installation to harden the network configuration such that the cluster can be run on an untrusted network (or on fully public IPs on a cloud provider).
1515

16-
{{% /capture %}}
1716

18-
{{% capture body %}}
17+
18+
<!-- body -->
1919

2020
## Node to Control Plane
2121
All communication paths from the nodes to the control plane terminate at the apiserver (none of the other master components are designed to expose remote services). In a typical deployment, the apiserver is configured to listen for remote connections on a secure HTTPS port (443) with one or more forms of client [authentication](/docs/reference/access-authn-authz/authentication/) enabled.
Collapse file

‎content/en/docs/concepts/architecture/controller.md‎

Copy file name to clipboardExpand all lines: content/en/docs/concepts/architecture/controller.md
+8-7Lines changed: 8 additions & 7 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: Controllers
3-
content_template: templates/concept
3+
content_type: concept
44
weight: 30
55
---
66

7-
{{% capture overview %}}
7+
<!-- overview -->
88

99
In robotics and automation, a _control loop_ is
1010
a non-terminating loop that regulates the state of a system.
@@ -18,10 +18,10 @@ closer to the desired state, by turning equipment on or off.
1818

1919
{{< glossary_definition term_id="controller" length="short">}}
2020

21-
{{% /capture %}}
2221

2322

24-
{{% capture body %}}
23+
24+
<!-- body -->
2525

2626
## Controller pattern
2727

@@ -150,11 +150,12 @@ You can run your own controller as a set of Pods,
150150
or externally to Kubernetes. What fits best will depend on what that particular
151151
controller does.
152152

153-
{{% /capture %}}
154153

155-
{{% capture whatsnext %}}
154+
155+
## {{% heading "whatsnext" %}}
156+
156157
* Read about the [Kubernetes control plane](/docs/concepts/#kubernetes-control-plane)
157158
* Discover some of the basic [Kubernetes objects](/docs/concepts/#kubernetes-objects)
158159
* Learn more about the [Kubernetes API](/docs/concepts/overview/kubernetes-api/)
159160
* If you want to write your own controller, see [Extension Patterns](/docs/concepts/extend-kubernetes/extend-cluster/#extension-patterns) in Extending Kubernetes.
160-
{{% /capture %}}
161+
Collapse file

‎content/en/docs/concepts/architecture/nodes.md‎

Copy file name to clipboardExpand all lines: content/en/docs/concepts/architecture/nodes.md
+8-7Lines changed: 8 additions & 7 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,11 @@ reviewers:
33
- caesarxuchao
44
- dchen1107
55
title: Nodes
6-
content_template: templates/concept
6+
content_type: concept
77
weight: 10
88
---
99

10-
{{% capture overview %}}
10+
<!-- overview -->
1111

1212
Kubernetes runs your workload by placing containers into Pods to run on _Nodes_.
1313
A node may be a virtual or physical machine, depending on the cluster. Each node
@@ -23,9 +23,9 @@ The [components](/docs/concepts/overview/components/#node-components) on a node
2323
{{< glossary_tooltip text="container runtime" term_id="container-runtime" >}}, and the
2424
{{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}}.
2525

26-
{{% /capture %}}
2726

28-
{{% capture body %}}
27+
28+
<!-- body -->
2929

3030
## Management
3131

@@ -332,12 +332,13 @@ the kubelet can use topology hints when making resource assignment decisions.
332332
See [Control Topology Management Policies on a Node](/docs/tasks/administer-cluster/topology-manager/)
333333
for more information.
334334

335-
{{% /capture %}}
336-
{{% capture whatsnext %}}
335+
336+
## {{% heading "whatsnext" %}}
337+
337338
* Learn about the [components](/docs/concepts/overview/components/#node-components) that make up a node.
338339
* Read the [API definition for Node](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#node-v1-core).
339340
* Read the [Node](https://git.k8s.io/community/contributors/design-proposals/architecture/architecture.md#the-kubernetes-node)
340341
section of the architecture design document.
341342
* Read about [taints and tolerations](/docs/concepts/configuration/taint-and-toleration/).
342343
* Read about [cluster autoscaling](/docs/tasks/administer-cluster/cluster-management/#cluster-autoscaling).
343-
{{% /capture %}}
344+
Collapse file

‎content/en/docs/concepts/cluster-administration/addons.md‎

Copy file name to clipboardExpand all lines: content/en/docs/concepts/cluster-administration/addons.md
+5-5Lines changed: 5 additions & 5 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
title: Installing Addons
3-
content_template: templates/concept
3+
content_type: concept
44
---
55

6-
{{% capture overview %}}
6+
<!-- overview -->
77

88

99
Add-ons extend the functionality of Kubernetes.
@@ -12,10 +12,10 @@ This page lists some of the available add-ons and links to their respective inst
1212

1313
Add-ons in each section are sorted alphabetically - the ordering does not imply any preferential status.
1414

15-
{{% /capture %}}
1615

1716

18-
{{% capture body %}}
17+
18+
<!-- body -->
1919

2020
## Networking and Network Policy
2121

@@ -55,4 +55,4 @@ There are several other add-ons documented in the deprecated [cluster/addons](ht
5555

5656
Well-maintained ones should be linked to here. PRs welcome!
5757

58-
{{% /capture %}}
58+
Collapse file

‎content/en/docs/concepts/cluster-administration/certificates.md‎

Copy file name to clipboardExpand all lines: content/en/docs/concepts/cluster-administration/certificates.md
+5-5Lines changed: 5 additions & 5 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
11
---
22
title: Certificates
3-
content_template: templates/concept
3+
content_type: concept
44
weight: 20
55
---
66

77

8-
{{% capture overview %}}
8+
<!-- overview -->
99

1010
When using client certificate authentication, you can generate certificates
1111
manually through `easyrsa`, `openssl` or `cfssl`.
1212

13-
{{% /capture %}}
1413

1514

16-
{{% capture body %}}
15+
16+
<!-- body -->
1717

1818
### easyrsa
1919

@@ -249,4 +249,4 @@ You can use the `certificates.k8s.io` API to provision
249249
x509 certificates to use for authentication as documented
250250
[here](/docs/tasks/tls/managing-tls-in-a-cluster).
251251

252-
{{% /capture %}}
252+
Collapse file

‎content/en/docs/concepts/cluster-administration/cloud-providers.md‎

Copy file name to clipboardExpand all lines: content/en/docs/concepts/cluster-administration/cloud-providers.md
+5-5Lines changed: 5 additions & 5 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
---
22
title: Cloud Providers
3-
content_template: templates/concept
3+
content_type: concept
44
weight: 30
55
---
66

7-
{{% capture overview %}}
7+
<!-- overview -->
88
This page explains how to manage Kubernetes running on a specific
99
cloud provider.
10-
{{% /capture %}}
1110

1211

13-
{{% capture body %}}
12+
13+
<!-- body -->
1414
### kubeadm
1515
[kubeadm](/docs/reference/setup-tools/kubeadm/kubeadm/) is a popular option for creating kubernetes clusters.
1616
kubeadm has configuration options to specify configuration information for cloud providers. For example a typical
@@ -363,7 +363,7 @@ Kubernetes network plugin and should appear in the `[Route]` section of the
363363

364364
[kubenet]: /docs/concepts/cluster-administration/network-plugins/#kubenet
365365

366-
{{% /capture %}}
366+
367367

368368
## OVirt
369369

Collapse file

‎content/en/docs/concepts/cluster-administration/cluster-administration-overview.md‎

Copy file name to clipboardExpand all lines: content/en/docs/concepts/cluster-administration/cluster-administration-overview.md
+5-5Lines changed: 5 additions & 5 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -3,16 +3,16 @@ reviewers:
33
- davidopp
44
- lavalamp
55
title: Cluster Administration Overview
6-
content_template: templates/concept
6+
content_type: concept
77
weight: 10
88
---
99

10-
{{% capture overview %}}
10+
<!-- overview -->
1111
The cluster administration overview is for anyone creating or administering a Kubernetes cluster.
1212
It assumes some familiarity with core Kubernetes [concepts](/docs/concepts/).
13-
{{% /capture %}}
1413

15-
{{% capture body %}}
14+
15+
<!-- body -->
1616
## Planning a cluster
1717

1818
See the guides in [Setup](/docs/setup/) for examples of how to plan, set up, and configure Kubernetes clusters. The solutions listed in this article are called *distros*.
@@ -68,6 +68,6 @@ Note: Not all distros are actively maintained. Choose distros which have been te
6868

6969
* [Logging and Monitoring Cluster Activity](/docs/concepts/cluster-administration/logging/) explains how logging in Kubernetes works and how to implement it.
7070

71-
{{% /capture %}}
71+
7272

7373

Collapse file

‎content/en/docs/concepts/cluster-administration/flow-control.md‎

Copy file name to clipboardExpand all lines: content/en/docs/concepts/cluster-administration/flow-control.md
+7-7Lines changed: 7 additions & 7 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: API Priority and Fairness
3-
content_template: templates/concept
3+
content_type: concept
44
min-kubernetes-server-version: v1.18
55
---
66

7-
{{% capture overview %}}
7+
<!-- overview -->
88

99
{{< feature-state state="alpha" for_k8s_version="v1.18" >}}
1010

@@ -33,9 +33,9 @@ the `--max-requests-inflight` flag without the API Priority and
3333
Fairness feature enabled.
3434
{{< /caution >}}
3535

36-
{{% /capture %}}
3736

38-
{{% capture body %}}
37+
38+
<!-- body -->
3939

4040
## Enabling API Priority and Fairness
4141

@@ -366,13 +366,13 @@ poorly-behaved workloads that may be harming system health.
366366
request and the PriorityLevel to which it was assigned.
367367

368368

369-
{{% /capture %}}
370369

371-
{{% capture whatsnext %}}
370+
371+
## {{% heading "whatsnext" %}}
372+
372373

373374
For background information on design details for API priority and fairness, see
374375
the [enhancement proposal](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/20190228-priority-and-fairness.md).
375376
You can make suggestions and feature requests via [SIG API
376377
Machinery](https://github.com/kubernetes/community/tree/master/sig-api-machinery).
377378

378-
{{% /capture %}}

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.