Skip to content

Commit dc3016c

Browse files
iMartyniMartyn
authored
Merge pull request #1 from kubernetes/master
Update from upstream
2 parents 40e80ba + 0f0ccd1 commit dc3016c

File tree

3,935 files changed

+254946
-670220
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

3,935 files changed

+254946
-670220
lines changed

‎.github/PULL_REQUEST_TEMPLATE.md

+1-7
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,5 @@
1-
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2-
> For 1.9 Features: set Milestone to `1.9` and Base Branch to `release-1.9`
3-
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
4-
> NOTE: Please check the “Allow edits from maintainers” box (see image below) to
5-
> [allow reviewers to fix problems](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) on your patch and speed up the review process.
1+
> NOTE: After opening the PR, please *un-check and re-check* the ["Allow edits from maintainers"](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) box so that maintainers can work on your patch and speed up the review process. This is a temporary workaround to address a known issue with GitHub.>
62
>
73
> Please delete this note before submitting the pull request.
8-
>
9-
> NOTE: After opening the PR, please *un-check and re-check* the "Allow edits from maintainers" box. This is a temporary workaround to address a known issue with GitHub.
104
115
![Allow edits from maintainers checkbox](https://help.github.com/assets/images/help/pull_requests/allow-maintainers-to-make-edits-sidebar-checkbox.png)

‎_config.yml

+10-10
Original file line numberDiff line numberDiff line change
@@ -18,16 +18,21 @@ defaults:
1818
scope:
1919
path: ""
2020
values:
21-
fullversion: "v1.8.0"
22-
version: "v1.8"
21+
fullversion: "v1.9.0"
22+
version: "v1.9"
2323
githubbranch: "master"
2424
docsbranch: "master"
2525
versions:
26-
- fullversion: "v1.8.0"
26+
- fullversion: "v1.9.0"
27+
version: "v1.9"
28+
githubbranch: "v1.9.0"
29+
docsbranch: "release-1.9"
30+
url: https://kubernetes.io/docs/home/
31+
- fullversion: "v1.8.4"
2732
version: "v1.8"
28-
githubbranch: "v1.8.0"
33+
githubbranch: "v1.8.4"
2934
docsbranch: "release-1.8"
30-
url: https://kubernetes.io/docs/home/
35+
url: https://v1-8.docs.kubernetes.io/docs/home/
3136
- fullversion: "v1.7.6"
3237
version: "v1.7"
3338
githubbranch: "v1.7.6"
@@ -43,11 +48,6 @@ defaults:
4348
githubbranch: "v1.5.7"
4449
docsbranch: "release-1.5"
4550
url: https://v1-5.docs.kubernetes.io/docs/
46-
- fullversion: "v1.4.12"
47-
version: "v1.4"
48-
githubbranch: "v1.4.12"
49-
docsbranch: "release-1.4"
50-
url: https://v1-4.docs.kubernetes.io/docs/
5151
deprecated: false
5252
currentUrl: https://kubernetes.io/docs/home/
5353
nextUrl: http://kubernetes-io-vnext-staging.netlify.com/

‎_data/concepts.yml

+1
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@ toc:
2424

2525
- title: Extending Kubernetes
2626
section:
27+
- docs/concepts/overview/extending.md
2728
- title: Extending the Kubernetes API
2829
section:
2930
- docs/concepts/api-extension/apiserver-aggregation.md

‎_data/glossary/annotation.yaml

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
id: annotation
2+
name: Annotation
3+
full-link: docs/concepts/overview/working-with-objects/annotations
4+
tags:
5+
- fundamental
6+
short-description: >
7+
A key-value pair that is used to attach arbitrary non-identifying metadata to objects.
8+
long-description: >
9+
The metadata in an annotation can be small or large, structured or unstructured, and can include characters not permitted by labels. Clients such as tools and libraries can retrieve this metadata.

‎_data/glossary/configmap.yaml

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
id: configmap
2+
name: ConfigMap
3+
full-link: /docs/tasks/configure-pod-container/configmap/
4+
related:
5+
- pod
6+
- secret
7+
tags:
8+
- core-object
9+
short-description: >
10+
An API object used to store non-confidential data in key-value pairs. Can be consumed as environment variables, command-line arguments, or config files in a {% glossary_tooltip text="volume" term_id="volume" %}.
11+
long-description: >
12+
Allows you to decouple environment-specific configuration from your {% glossary_tooltip text="container images" term_id="container" %}, so that your applications are easily portable.
13+
When storing confidential data use a [Secret](https://kubernetes.io/docs/concepts/configuration/secret/).

‎_data/glossary/daemonset.yaml

+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
id: daemonset
2+
name: DaemonSet
3+
full-link: /docs/concepts/workloads/controllers/daemonset
4+
tags:
5+
- fundamental
6+
- workload
7+
short-description: >
8+
Ensures a copy of a {% glossary_tooltip term_id="pod" %} is running across a set of nodes in a {% glossary_tooltip term_id="cluster" %}.
9+
long-description: >
10+
Used to deploy system daemons such as log collectors and monitoring agents that typically must run on every {% glossary_tooltip term_id="node" %}.

‎_data/glossary/horizontal-pod-autoscaler.yaml

+15
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
id: horizontal-pod-autoscaler
2+
name: Horizontal Pod Autoscaler
3+
full-link: /docs/tasks/run-application/horizontal-pod-autoscale/
4+
aka:
5+
- HPA
6+
related:
7+
- pod
8+
tags:
9+
- operation
10+
short-description: >
11+
An API resource that automatically scales the number of pod replicas based on targeted CPU
12+
utilization or custom metric targets.
13+
long-description: >
14+
HPA is typically used with replication controllers, deployments or replica sets and cannot be
15+
applied to objects that cannot be scaled, for example DaemonSets.

‎_data/glossary/image.yaml

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
id: image
2+
name: Image
3+
tags:
4+
- fundamental
5+
short-description: >
6+
Stored instance of a container that holds a set of software needed to run an application.
7+
long-description: >
8+
A way of packaging software that allows it to be stored in a container registry, pulled to a local system, and run as an application. Meta data is included in the image that can indicate what executable to run, who built it, and other information.
9+

‎_data/glossary/job.yaml

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
id: job
2+
name: Job
3+
full-link: /docs/concepts/workloads/controllers/jobs-run-to-completion
4+
tags:
5+
- core-object
6+
short-description: >
7+
A finite or batch task that runs to completion.
8+
long-description: >
9+
Creates one or more {% glossary_tooltip term_id="pod" %} objects and ensures that a specified number of them successfully terminate. As Pods successfully complete, the Job tracks the successful completions.

‎_data/glossary/kubelet.yaml

+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
id: kubelet
2+
name: Kubelet
3+
full-link: docs/reference/generated/kubelet
4+
tags:
5+
- fundamental
6+
- core-object
7+
short-description: >
8+
An agent that runs on each node in the cluster. It makes sure that containers are running in a pod.
9+
long-description: >
10+
The kubelet takes a set of PodSpecs that are provided through various mechanisms and ensures that the containers described in those PodSpecs are running and healthy. The kubelet doesn’t manage containers which were not created by Kubernetes.

‎_data/glossary/labels.yaml

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
id: labels
2+
name: Labels
3+
full-link: /docs/concepts/overview/working-with-objects/labels
4+
tags:
5+
- fundamental
6+
short-description: >
7+
Used to tag objects with identifying attributes that are meaningful and relevant to users.
8+
long-description: >
9+
Labels are key/value pairs that are attached to objects, such as pods. They can be used to organize and to select subsets of objects.

‎_data/glossary/namespace.yaml

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
id: namespace
2+
name: Namespace
3+
full-link: /docs/concepts/overview/working-with-objects/namespaces
4+
tags:
5+
- fundamental
6+
short-description: >
7+
An abstraction used by Kubernetes to support virtual clusters on the same physical {% glossary_tooltip term_id="cluster" %}.
8+
long-description: >
9+
Namespaces are used to organize objects in a cluster and provide a way to divide cluster resources. Names of resources need to be unique within a namespace, but not across namespaces.

‎_data/glossary/network-policy.yaml

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
id: network-policy
2+
name: Network Policy
3+
full-link: /docs/concepts/services-networking/network-policies/
4+
aka:
5+
- NetworkPolicy
6+
tags:
7+
- networking
8+
- architecture
9+
- extension
10+
short-description: >
11+
A specification of how groups of Pods are allowed to communicate with each other and with other network endpoints.
12+
long-description: >
13+
Network Policies help you declaratively configure which Pods are allowed to connect to each other, which namespaces are allowed to communicate, and more specifically which port numbers to enforce each policy on. `NetworkPolicy` resources use labels to select Pods and define rules which specify what traffic is allowed to the selected Pods. Network Policies are implemented by a supported network plugin provided by a network provider. Be aware that creating a network resource without a controller to implement it will have no effect.

‎_data/glossary/node.yaml

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
id: node
2+
name: Node
3+
full-link: /docs/concepts/architecture/nodes/
4+
aka:
5+
- Minion
6+
related:
7+
- deployment
8+
tags:
9+
- fundamental
10+
short-description: >
11+
A node is a worker machine in Kubernetes.
12+
long-description: >
13+
A worker machine may be a VM or physical machine, depending on the cluster. It has the {% glossary_tooltip text="Services" term_id="service" %} necessary to run {% glossary_tooltip text="Pods" term_id="pod" %} and is managed by the master components. The {% glossary_tooltip text="Services" term_id="service" %} on a node include Docker, kubelet and kube-proxy.

‎_data/glossary/platform-developer.yaml

+2-1
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,10 @@ id: platform-developer
22
name: Platform Developer
33
aka:
44
- Kubernetes Developer
5+
- Extension Developer
56
tags:
67
- user-type
78
short-description: >
89
A person who customizes the Kubernetes platform to fit the needs of their project.
910
long-description: >
10-
A platform developer may, for example, use [Custom Resources](/docs/concepts/api-extension/custom-resources/) or [Extend the Kubernetes API with the aggregation layer](/docs/concepts/api-extension/apiserver-aggregation/) to add functionality to their instance of Kubernetes, specifically for their application.
11+
A platform developer may, for example, use [Custom Resources](/docs/concepts/api-extension/custom-resources/) or [Extend the Kubernetes API with the aggregation layer](/docs/concepts/api-extension/apiserver-aggregation/) to add functionality to their instance of Kubernetes, specifically for their application. Some Platform Developers are also {% glossary_tooltip text="contributors" term_id="contributor" %} and develop extensions which are contributed to the Kubernetes community. Others develop closed-source commercial or site-specific extensions.

‎_data/glossary/pod-security-policy.yaml

+19
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
id: pod-security-policy
2+
name: Pod Security Policy
3+
full-link: /docs/concepts/policy/pod-security-policy/
4+
related:
5+
- pod
6+
- container
7+
- sidecar
8+
- deployment
9+
- statefulset
10+
- security
11+
tags:
12+
- core-object
13+
- fundamental
14+
short-description: >
15+
Enables fine-grained authorization of {% glossary_tooltip term_id="pod" %} creation and updates.
16+
long-description: >
17+
A cluster-level resource that controls security sensitive aspects of the Pod specification.
18+
The `PodSecurityPolicy` objects define a set of conditions that a Pod must run with in order to be accepted into the system, as well as defaults for the related fields.
19+
Pod Security Policy control is implemented as an optional admission controller.

‎_data/glossary/replica-set.yml

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
id: replica-set
2+
name: ReplicaSet
3+
full-link: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/
4+
related:
5+
- replication-controller
6+
tags:
7+
- core-object
8+
- architecture
9+
short-description: >
10+
ReplicaSet is the next-generation Replication Controller.
11+
long-description: >
12+
ReplicaSet, like ReplicationController, ensures that a specified number of pods replicas are running at one time.
13+
ReplicaSet supports the new set-based selector requirements as described in the labels user guide, whereas a Replication Controller only supports equality-based selector requirements.

‎_data/glossary/replication-controller.yaml

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
id: replication-controller
2+
name: Replication Controller
3+
tags:
4+
- fundamental
5+
short-description: >
6+
Kubernetes service that ensures a specific number of instances of a pod are always running.
7+
long-description: >
8+
Will automatically add or remove running instances of a pod, based on a set value for that pod. Allows the pod to return to the defined number of instances if pods are deleted or if too many are started by mistake.
9+

‎_data/glossary/resource-quota.yaml

+11
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
id: resource-quota
2+
name: Resource Quotas
3+
full-link: /docs/concepts/policy/resource-quotas/
4+
tags:
5+
- fundamental
6+
- operation
7+
- architecture
8+
short-description: >
9+
Provides constraints that limit aggregate resource consumption per {% glossary_tooltip term_id="namespace" %}.
10+
long-description: >
11+
Limits the quantity of objects that can be created in a namespace by type, as well as the total amount of compute resources that may be consumed by resources in that project.

‎_data/glossary/secret.yml

+15
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
id: secret
2+
name: Secret
3+
full-link: /docs/concepts/configuration/secret/
4+
related:
5+
- pods
6+
- volume
7+
tags:
8+
- core-object
9+
- security
10+
short-description: >
11+
Stores sensitive information, such as passwords, OAuth tokens, and ssh keys.
12+
long-description: >
13+
Allows for more control over how sensitive information is used and reduces the risk of accidental exposure, including [encryption](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#ensure-all-secrets-are-encrypted) at rest.
14+
A {% glossary_tooltip text="Pod" term_id="pod" %} references the secret as a file in a volume mount or by the kubelet pulling images for a pod.
15+
Secrets are great for confidential data and [ConfigMaps](https://kubernetes.io/docs/tasks/configure-pod-container/configmap/) for non-confidential data.

‎_data/glossary/security-context.yaml

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
id: security-context
2+
name: Security Context
3+
full-link: /docs/tasks/configure-pod-container/security-context/
4+
tags:
5+
- security
6+
short-description: >
7+
The securityContext field defines privilege and access control settings for a Pod or Container, including the runtime UID and GID.
8+
long-description: >
9+
The securityContext field in a {% glossary_tooltip term_id="pod" %} (applying to all containers) or container is used to set the user (runAsUser) and group (fsGroup), capabilities, privilege settings, and security policies (SELinux/AppArmor/Seccomp) that container processes use.

‎_data/glossary/service-account.yaml

+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
id: service-account
2+
name: Service Account
3+
full-link: /docs/tasks/configure-pod-container/configure-service-account/
4+
tags:
5+
- fundamental
6+
- core-object
7+
short-description: >
8+
Provides an identity for processes that run in a Pod {% glossary_tooltip text="Pods" term_id="pod" %}.
9+
long-description: >
10+
When processes inside Pods access the cluster, they are authenticated by the API server as a particular service account, for example, `default`. When you create a Pod, if you do not specify a service account, it is automatically assigned the default service account in the same namespace {% glossary_tooltip text="Namespace" term_id="namespace" %}.

‎_data/glossary/service-catalog.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,4 +5,4 @@ tags:
55
short-description: >
66
An extension API that enables applications running in Kubernetes clusters to easily use external managed software offerings, such as a datastore service offered by a cloud provider.
77
long-description: >
8-
Service Catalog provides a way to list, provision, and bind with external {% glossary_tooltip text="Managed Services" term_id="managed-service" %} from {% glossary_tooltip text="Service Brokers" term_id="service-broker" %} without needing detailed knowledge about how those services are created or managed.
8+
It provides a way to list, provision, and bind with external {% glossary_tooltip text="Managed Services" term_id="managed-service" %} from {% glossary_tooltip text="Service Brokers" term_id="service-broker" %} without needing detailed knowledge about how those services are created or managed.

‎_data/glossary/volume.yaml

+17
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
id: volume
2+
name: Volume
3+
full-link: /docs/concepts/storage/volumes/
4+
related:
5+
- pod
6+
- container
7+
- secret
8+
tags:
9+
- core-object
10+
- fundamental
11+
short-description: >
12+
A directory containing data, accessible to the containers in a {% glossary_tooltip text="pod" term_id="pod" %}.
13+
long-description: >
14+
A Kubernetes volume lives as long as the {% glossary_tooltip text="pod" term_id="pod" %} that encloses it.
15+
Consequently, a volume outlives any {% glossary_tooltip text="containers" term_id="container" %} that run within the
16+
{% glossary_tooltip text="pod" term_id="pod" %}, and data is preserved across
17+
{% glossary_tooltip text="container" term_id="container" %} restarts.

0 commit comments

Comments
 (0)