zh_Trans: Fix preview issue (#11311)

* zh_trans: kubeadm-upgrade-1-12.md * update file * Update _index.md * Delete _index.md * Update kubeadm-upgrade-1-12.md * zh_trans: docs/reference/setup-tools/kubeadm/generated/kubeadm_config.md * Update kubeadm_config.md * zh_trans: fix Preview * zh_trans: fix Preview
2018-11-26 19:08:04 +08:00
parent d6bdb664fb
commit 941f8d1ce4
74 changed files with 2112 additions and 0 deletions
@@ -0,0 +1,20 @@
+---
+title: Aggregation Layer
+id: aggregation-layer
+date: 2018-10-08
+full_link: /docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/
+short_description: >
+  The aggregation layer lets you install additional Kubernetes-style APIs in your cluster.
+
+aka: 
+tags:
+- architecture
+- extension
+- operation
+---
+ The aggregation layer lets you install additional Kubernetes-style APIs in your cluster.
+
+<!--more--> 
+
+When you've configured the {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} to [support additional APIs](https://kubernetes.io/docs/tasks/access-kubernetes-api/configure-aggregation-layer/), you can add `APIService` objects to "claim" a URL path in the Kubernetes API.
+
@@ -0,0 +1,18 @@
+---
+title: Approver
+id: approver
+date: 2018-04-12
+full_link: 
+short_description: >
+  A person who can review and approve Kubernetes code contributions.
+
+aka: 
+tags:
+- community
+---
+ A person who can review and approve Kubernetes code contributions.
+
+<!--more--> 
+
+While code review is focused on code quality and correctness, approval is focused on the holistic acceptance of a contribution. Holistic acceptance includes backwards/forwards compatibility, adhering to API and flag conventions, subtle performance and correctness issues, interactions with other parts of the system, and others. Approver status is scoped to a part of the codebase. Approvers were previously referred to as maintainers.
+
@@ -0,0 +1,20 @@
+---
+title: Cloud Controller Manager
+id: cloud-controller-manager
+date: 2018-04-12
+full_link: https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/
+short_description: >
+  Cloud Controller Manager is an alpha feature in 1.8. In upcoming releases it will be the preferred way to integrate Kubernetes with any cloud.
+
+aka: 
+tags:
+- core-object
+- architecture
+- operation
+---
+ Cloud Controller Manager is an alpha feature in 1.8. In upcoming releases it will be the preferred way to integrate Kubernetes with any cloud.
+
+<!--more--> 
+
+Kubernetes v1.6 contains a new binary called cloud-controller-manager. cloud-controller-manager is a daemon that embeds cloud-specific control loops.  These cloud-specific control loops were originally in the kube-controller-manager. Since cloud providers develop and release at a different pace compared to the Kubernetes  project, abstracting the provider-specific code to the cloud-controller-manager binary allows cloud vendors to evolve independently from the core Kubernetes code.
+
@@ -0,0 +1,19 @@
+---
+title: Developer (disambiguation)
+id: developer
+date: 2018-04-12
+full_link: 
+short_description: >
+  May refer to&#58; Application Developer, Code Contributor, or Platform Developer.
+
+aka: 
+tags:
+- community
+- user-type
+---
+ May refer to&#58; {{< glossary_tooltip text="Application Developer" term_id="application-developer" >}}, {{< glossary_tooltip text="Code Contributor" term_id="code-contributor" >}}, or {{< glossary_tooltip text="Platform Developer" term_id="platform-developer" >}}.
+
+<!--more--> 
+
+This overloaded term may have different meanings depending on the context
+
@@ -0,0 +1,18 @@
+---
+title: docker
+id: docker
+date: 2018-04-12
+full_link: /docs/reference/kubectl/docker-cli-to-kubectl/
+short_description: >
+  Docker is a software technology providing operating-system-level virtualization also known as containers.
+
+aka: 
+tags:
+- fundamental
+---
+ Docker is a software technology providing operating-system-level virtualization also known as containers.
+
+<!--more--> 
+
+Docker uses the resource isolation features of the Linux kernel such as cgroups and kernel namespaces, and a union-capable file system such as OverlayFS and others to allow independent "containers" to run within a single Linux instance, avoiding the overhead of starting and maintaining virtual machines (VMs).
+
@@ -0,0 +1,19 @@
+---
+title: Downstream (disambiguation)
+id: downstream
+date: 2018-04-12
+full_link: 
+short_description: >
+  May refer to: code in the Kubernetes ecosystem that depends upon the core Kubernetes codebase or a forked repo.
+
+aka: 
+tags:
+- community
+---
+ May refer to: code in the Kubernetes ecosystem that depends upon the core Kubernetes codebase or a forked repo.
+
+<!--more--> 
+
+* In the **Kubernetes Community**: Conversations often use *downstream* to mean the ecosystem, code, or third-party tools that rely on the core Kubernetes codebase. For example, a new feature in Kubernetes may be adopted by applications *downstream* to improve their functionality.
+* In **GitHub** or **git**: The convention is to refer to a forked repo as *downstream*, whereas the source repo is considered *upstream*.
+
@@ -0,0 +1,19 @@
+---
+title: Dynamic Volume Provisioning
+id: dynamicvolumeprovisioning
+date: 2018-04-12
+full_link: /docs/concepts/storage/dynamic-provisioning
+short_description: >
+  Allows users to request automatic creation of storage  Volumes.
+
+aka: 
+tags:
+- core-object
+- storage
+---
+ Allows users to request automatic creation of storage  {{< glossary_tooltip text="Volumes" term_id="volume" >}}.
+
+<!--more--> 
+
+Dynamic provisioning eliminates the need for cluster administrators to pre-provision storage. Instead, it automatically provisions storage by user request. Dynamic volume provisioning is based on an API object, {{< glossary_tooltip text="StorageClass" term_id="storage-class" >}}, referring to a {{< glossary_tooltip text="Volume Plugin" term_id="volume-plugin" >}} that provisions a {{< glossary_tooltip text="Volume" term_id="volume" >}} and the set of parameters to pass to the Volume Plugin.
+
@@ -0,0 +1,22 @@
+---
+title: Flexvolume
+id: flexvolume
+date: 2018-06-25
+full_link: https://kubernetes.io/docs/concepts/storage/volumes/#flexvolume
+short_description: >
+    Flexvolume is an interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with Flexvolumes.
+
+
+aka: 
+tags:
+- storage 
+---
+ Flexvolume is an interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with Flexvolumes.
+
+<!--more--> 
+
+Flexvolumes enable users to write their own drivers and add support for their volumes in Kubernetes. FlexVolume driver binaries and dependencies must be installed on host machines. This requires root access. The Storage SIG suggests implementing a {{< glossary_tooltip text="CSI" term_id="csi" >}} driver if possible since it addresses the limitations with Flexvolumes.
+
+* [Flexvolume in the Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/volumes/#flexvolume)
+* [More information on Flexvolumes](https://github.com/kubernetes/community/blob/master/contributors/devel/flexvolume.md)
+* [Volume Plugin FAQ for Storage Vendors](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md)
@@ -0,0 +1,19 @@
+---
+title: Helm Chart
+id: helm-chart
+date: 2018-04-12
+full_link: https://github.com/kubernetes/helm/blob/master/docs/charts.md
+short_description: >
+  A package of pre-configured Kubernetes resources that can be managed with the Helm tool.
+
+aka: 
+tags:
+- tool
+---
+ A package of pre-configured Kubernetes resources that can be managed with the Helm tool.
+
+<!--more--> 
+
+Charts provide a reproducible way of creating and sharing Kubernetes applications.
+A single chart can be used to deploy something simple, like a memcached Pod, or something complex, like a full web app stack with HTTP servers, databases, caches, and so on.
+
@@ -0,0 +1,18 @@
+---
+title: Horizontal Pod Autoscaler
+id: horizontal-pod-autoscaler
+date: 2018-04-12
+full_link: /docs/tasks/run-application/horizontal-pod-autoscale/
+short_description: >
+  An API resource that automatically scales the number of pod replicas based on targeted CPU utilization or custom metric targets.
+
+aka: 
+tags:
+- operation
+---
+ An API resource that automatically scales the number of pod replicas based on targeted CPU utilization or custom metric targets.
+
+<!--more--> 
+
+HPA is typically used with {{< glossary_tooltip text="Replication Controllers" term_id="replication-controller" >}}, {{< glossary_tooltip text="Deployments" term_id="deployment" >}}, or Replica Sets. It cannot be applied to objects that cannot be scaled, for example {{< glossary_tooltip text="DaemonSets" term_id="daemonset" >}}.
+
@@ -0,0 +1,18 @@
+---
+title: Image
+id: image
+date: 2018-04-12
+full_link: 
+short_description: >
+  Stored instance of a container that holds a set of software needed to run an application.
+
+aka: 
+tags:
+- fundamental
+---
+ Stored instance of a container that holds a set of software needed to run an application.
+
+<!--more--> 
+
+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.
+
@@ -0,0 +1,18 @@
+---
+title: Init Container
+id: init-container
+date: 2018-04-12
+full_link: 
+short_description: >
+  One or more initialization containers that must run to completion before any app containers run. 
+
+aka: 
+tags:
+- fundamental
+---
+ One or more initialization containers that must run to completion before any app containers run. 
+
+<!--more--> 
+
+Initialization (init) containers are like regular app containers, with one difference: init containers must run to completion before any app containers can start. Init containers run in series: each init container must run to completion before the next init container begins.  
+
@@ -0,0 +1,20 @@
+---
+title: Istio
+id: istio
+date: 2018-04-12
+full_link: https://istio.io/docs/concepts/what-is-istio/overview.html
+short_description: >
+  An open platform (not Kubernetes-specific) that provides a uniform way to integrate microservices, manage traffic flow, enforce policies, and aggregate telemetry data.
+
+aka: 
+tags:
+- networking
+- architecture
+- extension
+---
+ An open platform (not Kubernetes-specific) that provides a uniform way to integrate microservices, manage traffic flow, enforce policies, and aggregate telemetry data.
+
+<!--more--> 
+
+Adding Istio does not require changing application code. It is a layer of infrastructure between a service and the network, which when combined with service deployments, is commonly referred to as a service mesh. Istio's control plane abstracts away the underlying cluster management platform, which may be Kubernetes, Mesosphere, etc.
+
@@ -0,0 +1,20 @@
+---
+title: Job
+id: job
+date: 2018-04-12
+full_link: /docs/concepts/workloads/controllers/jobs-run-to-completion
+short_description: >
+  A finite or batch task that runs to completion.
+
+aka: 
+tags:
+- fundamental
+- core-object
+- workload
+---
+ A finite or batch task that runs to completion.
+
+<!--more--> 
+
+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.
+
@@ -0,0 +1,28 @@
+---
+title: Kops
+id: kops
+date: 2018-04-12
+full_link: /docs/getting-started-guides/kops/
+short_description: >
+  A CLI tool that helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters. *NOTE&#58; Officially supports AWS only, with GCE and VMware vSphere in alpha*.
+
+aka: 
+tags:
+- tool
+- operation
+---
+ A CLI tool that helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters. *NOTE&#58; Officially supports AWS only, with GCE and VMware vSphere in alpha*.
+
+<!--more--> 
+
+`kops` provisions your cluster with&#58;
+
+  * Fully automated installation
+  * DNS-based cluster identification
+  * Self-healing&#58; everything runs in Auto-Scaling Groups
+  * Limited OS support (Debian preferred, Ubuntu 16.04 supported, early support for CentOS & RHEL)
+  * High availability (HA) support
+  * The ability to directly provision, or generate terraform manifests
+
+You can also build your own cluster using {{< glossary_tooltip term_id="kubeadm" >}} as a building block. `kops` builds on the kubeadm work.
+
@@ -0,0 +1,19 @@
+---
+title: kube-controller-manager
+id: kube-controller-manager
+date: 2018-04-12
+full_link: /docs/reference/generated/kube-controller-manager/
+short_description: >
+  Component on the master that runs controllers.
+
+aka: 
+tags:
+- architecture
+- fundamental
+---
+ Component on the master that runs {{< glossary_tooltip text="controllers" term_id="controller" >}}.
+
+<!--more--> 
+
+Logically, each {{< glossary_tooltip text="controller" term_id="controller" >}} is a separate process, but to reduce complexity, they are all compiled into a single binary and run in a single process.
+
@@ -0,0 +1,19 @@
+---
+title: kube-proxy
+id: kube-proxy
+date: 2018-04-12
+full_link: /docs/reference/generated/kube-proxy
+short_description: >
+  `kube-proxy` is a network proxy that runs on each node in the cluster.
+
+aka: 
+tags:
+- fundamental
+- core-object
+---
+ `kube-proxy` is a network proxy that runs on each node in the cluster.
+
+<!--more--> 
+
+`kube-proxy` is responsible for request forwarding. `kube-proxy` allows TCP and UDP stream forwarding or round robin TCP and UDP forwarding across a set of backend functions.
+
@@ -0,0 +1,18 @@
+---
+title: kube-scheduler
+id: kube-scheduler
+date: 2018-04-12
+full_link: /docs/reference/generated/kube-scheduler/
+short_description: >
+  Component on the master that watches newly created pods that have no node assigned, and selects a node for them to run on.
+
+aka: 
+tags:
+- architecture
+---
+ Component on the master that watches newly created pods that have no node assigned, and selects a node for them to run on.
+
+<!--more--> 
+
+Factors taken into account for scheduling decisions include individual and collective resource requirements,  hardware/software/policy constraints, affinity and anti-affinity specifications, data locality, inter-workload interference and deadlines.
+
@@ -0,0 +1,19 @@
+---
+title: Kubectl
+id: kubectl
+date: 2018-04-12
+full_link: /docs/user-guide/kubectl-overview/
+short_description: >
+  A command line tool for communicating with a Kubernetes API server.
+
+aka: 
+tags:
+- tool
+- fundamental
+---
+ A command line tool for communicating with a {{< glossary_tooltip text="Kubernetes API" term_id="kubernetes-api" >}} server.
+
+<!--more--> 
+
+You can use kubectl to create, inspect, update, and delete Kubernetes objects.
+
@@ -0,0 +1,19 @@
+---
+title: Kubelet
+id: kubelet
+date: 2018-04-12
+full_link: /docs/reference/generated/kubelet
+short_description: >
+  An agent that runs on each node in the cluster. It makes sure that containers are running in a pod.
+
+aka: 
+tags:
+- fundamental
+- core-object
+---
+ An agent that runs on each node in the cluster. It makes sure that containers are running in a pod.
+
+<!--more--> 
+
+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.
+
@@ -0,0 +1,19 @@
+---
+title: Kubernetes API
+id: kubernetes-api
+date: 2018-04-12
+full_link: /docs/concepts/overview/kubernetes-api/
+short_description: >
+  The application that serves Kubernetes functionality through a RESTful interface and stores the state of the cluster.
+
+aka: 
+tags:
+- fundamental
+- architecture
+---
+ The application that serves Kubernetes functionality through a RESTful interface and stores the state of the cluster.
+
+<!--more--> 
+
+Kubernetes resources and "records of intent" are all stored as API objects, and modified via RESTful calls to the API. The API allows configuration to be managed in a declarative way. Users can interact with the Kubernetes API directly, or via tools like `kubectl`. The core Kubernetes API is flexible and can also be extended to support custom resources.
+
@@ -0,0 +1,19 @@
+---
+title: Minikube
+id: minikube
+date: 2018-04-12
+full_link: /docs/getting-started-guides/minikube/
+short_description: >
+  A tool for running Kubernetes locally.
+
+aka: 
+tags:
+- fundamental
+- tool
+---
+ A tool for running Kubernetes locally.
+
+<!--more--> 
+
+Minikube runs a single-node cluster inside a VM on your computer.
+
@@ -0,0 +1,18 @@
+---
+title: Name
+id: name
+date: 2018-04-12
+full_link: /docs/concepts/overview/working-with-objects/names
+short_description: >
+  A client-provided string that refers to an object in a resource URL, such as `/api/v1/pods/some-name`.
+
+aka: 
+tags:
+- fundamental
+---
+ A client-provided string that refers to an object in a resource URL, such as `/api/v1/pods/some-name`.
+
+<!--more--> 
+
+Only one object of a given kind can have a given name at a time. However, if you delete the object, you can make a new object with the same name.
+
@@ -0,0 +1,20 @@
+---
+title: Network Policy
+id: network-policy
+date: 2018-04-12
+full_link: /docs/concepts/services-networking/network-policies/
+short_description: >
+  A specification of how groups of Pods are allowed to communicate with each other and with other network endpoints.
+
+aka: 
+tags:
+- networking
+- architecture
+- extension
+---
+ A specification of how groups of Pods are allowed to communicate with each other and with other network endpoints.
+
+<!--more--> 
+
+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.
+
@@ -0,0 +1,19 @@
+---
+title: Persistent Volume Claim
+id: persistent-volume-claim
+date: 2018-04-12
+full_link: /docs/concepts/storage/persistent-volumes/
+short_description: >
+  Claims storage resources defined in a PersistentVolume so that it can be mounted as a volume in a container.
+
+aka: 
+tags:
+- core-object
+- storage
+---
+ Claims storage resources defined in a PersistentVolume so that it can be mounted as a volume in a container.
+
+<!--more--> 
+
+Specifies the amount of storage, how the storage will be accessed (read-only, read-write and/or exclusive) and how it is reclaimed (retained, recycled or deleted). Details of the storage itself are in the PersistentVolume specification.
+
@@ -0,0 +1,18 @@
+---
+title: Platform Developer
+id: platform-developer
+date: 2018-04-12
+full_link: 
+short_description: >
+  A person who customizes the Kubernetes platform to fit the needs of their project.
+
+aka: 
+tags:
+- user-type
+---
+ A person who customizes the Kubernetes platform to fit the needs of their project.
+
+<!--more--> 
+
+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.
+
@@ -0,0 +1,19 @@
+---
+title: Pod
+id: pod
+date: 2018-04-12
+full_link: /docs/concepts/workloads/pods/pod-overview/
+short_description: >
+  The smallest and simplest Kubernetes object. A Pod represents a set of running containers on your cluster.
+
+aka: 
+tags:
+- core-object
+- fundamental
+---
+ The smallest and simplest Kubernetes object. A Pod represents a set of running {{< glossary_tooltip text="containers" term_id="container" >}} on your cluster.
+
+<!--more--> 
+
+A Pod is typically set up to run a single primary container. It can also run optional sidecar containers that add supplementary features like logging. Pods are commonly managed by a {{< glossary_tooltip term_id="deployment" >}}.
+
@@ -0,0 +1,18 @@
+---
+title: PodPreset
+id: podpreset
+date: 2018-04-12
+full_link: 
+short_description: >
+  An API object that injects information such as secrets, volume mounts, and environment variables into pods at creation time.
+
+aka: 
+tags:
+- operation
+---
+ An API object that injects information such as secrets, volume mounts, and environment variables into pods at creation time.
+
+<!--more--> 
+
+This object chooses the pods to inject information into using standard selectors. This allows the podspec definitions to be nonspecific, decoupling the podspec from environment specific configuration.
+
@@ -0,0 +1,65 @@
+<<<<<<< HEAD
+---
+title: Quantity
+id: quantity
+date: 2018-08-07
+full_link:
+short_description: >
+  A whole-number representation of small or large numbers using SI suffixes.
+
+aka: 
+tags:
+---
+ A whole-number representation of small or large numbers using SI suffixes.
+
+<!--more--> 
+
+Quantities are representations of small or large numbers using a compact,
+whole-number notation with SI suffixes.  Fractional numbers are represented
+using milli-units, while large numbers can be represented using kilo-units,
+mega-units, giga-units, etc.
+
+For instance, the number `1.5` is represented `1500m`, while the number `1000`
+can be represented as `1k`, and `1000000` as `1M`. You can also specify
+binary-notation suffixes; the number 2048 can be written as `2Ki`.
+
+The accepted decimal (power-of-10) units are `m` (milli), `k` (kilo,
+intentionally lowercase), `M` (mega), `G` (giga), `T` (terra), `P` (peta),
+`E` (exa).
+
+The accepted binary (power-of-2) units are `Ki` (kibi), `Mi` (mebi), `Gi` (gibi),
+`Ti` (tebi), `Pi` (pebi), `Ei` (exbi).
+||||||| merged common ancestors
+=======
+---
+title: Quantity
+id: quantity
+date: 2018-08-07
+full_link:
+short_description: >
+  A whole-number representation of small or large numbers using SI suffixes.
+
+aka: 
+tags:
+- core-object
+---
+ A whole-number representation of small or large numbers using SI suffixes.
+
+<!--more-->
+
+Quantities are representations of small or large numbers using a compact,
+whole-number notation with SI suffixes.  Fractional numbers are represented
+using milli units, while large numbers can be represented using kilo,
+mega, or giga units.
+
+For instance, the number `1.5` is represented as `1500m`, while the number `1000`
+can be represented as `1k`, and `1000000` as `1M`. You can also specify
+binary-notation suffixes; the number 2048 can be written as `2Ki`.
+
+The accepted decimal (power-of-10) units are `m` (milli), `k` (kilo,
+intentionally lowercase), `M` (mega), `G` (giga), `T` (terra), `P` (peta),
+`E` (exa).
+
+The accepted binary (power-of-2) units are `Ki` (kibi), `Mi` (mebi), `Gi` (gibi),
+`Ti` (tebi), `Pi` (pebi), `Ei` (exbi).
+>>>>>>> master
@@ -0,0 +1,19 @@
+---
+title: RBAC (Role-Based Access Control)
+id: rbac
+date: 2018-04-12
+full_link: /docs/reference/access-authn-authz/rbac/
+short_description: >
+  Manages authorization decisions, allowing admins to dynamically configure access policies through the Kubernetes API.
+
+aka: 
+tags:
+- security
+- fundamental
+---
+ Manages authorization decisions, allowing admins to dynamically configure access policies through the {{< glossary_tooltip text="Kubernetes API" term_id="kubernetes-api" >}}.
+
+<!--more--> 
+
+RBAC utilizes *roles*, which contain permission rules, and *role bindings*, which grant the permissions defined in a role to a set of users.
+
@@ -0,0 +1,20 @@
+---
+title: ReplicaSet
+id: replica-set
+date: 2018-04-12
+full_link: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/
+short_description: >
+  ReplicaSet is the next-generation Replication Controller.
+
+aka: 
+tags:
+- fundamental
+- core-object
+- workload
+---
+ ReplicaSet is the next-generation Replication Controller.
+
+<!--more--> 
+
+ReplicaSet, like ReplicationController, ensures that a specified number of pods replicas are running at one time. 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.
+
@@ -0,0 +1,20 @@
+---
+title: Resource Quotas
+id: resource-quota
+date: 2018-04-12
+full_link: /docs/concepts/policy/resource-quotas/
+short_description: >
+  Provides constraints that limit aggregate resource consumption per namespace.
+
+aka: 
+tags:
+- fundamental
+- operation
+- architecture
+---
+ Provides constraints that limit aggregate resource consumption per {{< glossary_tooltip term_id="namespace" >}}.
+
+<!--more--> 
+
+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.
+
@@ -0,0 +1,19 @@
+---
+title: Secret
+id: secret
+date: 2018-04-12
+full_link: /docs/concepts/configuration/secret/
+short_description: >
+  Stores sensitive information, such as passwords, OAuth tokens, and ssh keys.
+
+aka: 
+tags:
+- core-object
+- security
+---
+ Stores sensitive information, such as passwords, OAuth tokens, and ssh keys.
+
+<!--more--> 
+
+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.  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. Secrets are great for confidential data and [ConfigMaps](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) for non-confidential data.
+
@@ -0,0 +1,18 @@
+---
+title: Security Context
+id: security-context
+date: 2018-04-12
+full_link: /docs/tasks/configure-pod-container/security-context/
+short_description: >
+  The securityContext field defines privilege and access control settings for a Pod or Container, including the runtime UID and GID.
+
+aka: 
+tags:
+- security
+---
+ The securityContext field defines privilege and access control settings for a Pod or Container, including the runtime UID and GID.
+
+<!--more--> 
+
+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.
+
@@ -0,0 +1,19 @@
+---
+title: Service Account
+id: service-account
+date: 2018-04-12
+full_link: /docs/tasks/configure-pod-container/configure-service-account/
+short_description: >
+  Provides an identity for processes that run in a Pod.
+
+aka: 
+tags:
+- fundamental
+- core-object
+---
+ Provides an identity for processes that run in a {{< glossary_tooltip text="Pod" term_id="pod" >}}.
+
+<!--more--> 
+
+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" >}}.
+
@@ -0,0 +1,19 @@
+---
+title: Service
+id: service
+date: 2018-04-12
+full_link: /docs/concepts/services-networking/service/
+short_description: >
+  An API object that describes how to access applications, such as a set of Pods, and can describe ports and load-balancers.
+
+aka: 
+tags:
+- fundamental
+- core-object
+---
+ An API object that describes how to access applications, such as a set of {{< glossary_tooltip text="Pods" term_id="pod" >}}, and can describe ports and load-balancers.
+
+<!--more--> 
+
+The access point can be internal or external to the cluster.
+
@@ -0,0 +1,18 @@
+---
+title: UID
+id: uid
+date: 2018-04-12
+full_link: /docs/concepts/overview/working-with-objects/names
+short_description: >
+  A Kubernetes systems-generated string to uniquely identify objects.
+
+aka: 
+tags:
+- fundamental
+---
+ A Kubernetes systems-generated string to uniquely identify objects.
+
+<!--more--> 
+
+Every object created over the whole lifetime of a Kubernetes cluster has a distinct UID. It is intended to distinguish between historical occurrences of similar entities.
+
@@ -0,0 +1,19 @@
+---
+title: Volume Plugin
+id: volumeplugin
+date: 2018-04-12
+full_link: 
+short_description: >
+  A Volume Plugin enables integration of storage within a Pod.
+
+aka: 
+tags:
+- core-object
+- storage
+---
+ A Volume Plugin enables integration of storage within a {{< glossary_tooltip text="Pod" term_id="pod" >}}.
+
+<!--more--> 
+
+A Volume Plugin lets you attach and mount storage volumes for use by a {{< glossary_tooltip text="Pod" term_id="pod" >}}. Volume plugins can be _in tree_ or _out of tree_. _In tree_ plugins are part of the Kubernetes code repository and follow its release cycle. _Out of tree_ plugins are developed independently.
+