zh-trans: add broken references for netlify preview

This commit is contained in:
Rui Chen
2018-11-26 18:29:55 +08:00
parent f12cf5c4d4
commit 905b149c29
8 changed files with 147 additions and 0 deletions
+18
View File
@@ -0,0 +1,18 @@
---
title: Contributor
id: contributor
date: 2018-04-12
full_link:
short_description: >
Someone who donates code, documentation, or their time to help the Kubernetes project or community.
aka:
tags:
- community
---
Someone who donates code, documentation, or their time to help the Kubernetes project or community.
<!--more-->
Contributions include pull requests (PRs), issues, feedback, {{< glossary_tooltip text="special interest groups (SIG)" term_id="sig" >}} participation, or organizing community events.
+19
View File
@@ -0,0 +1,19 @@
---
title: kube-apiserver
id: kube-apiserver
date: 2018-04-12
full_link: /docs/reference/generated/kube-apiserver/
short_description: >
Component on the master that exposes the Kubernetes API. It is the front-end for the Kubernetes control plane.
aka:
tags:
- architecture
- fundamental
---
Component on the master that exposes the Kubernetes API. It is the front-end for the Kubernetes control plane.
<!--more-->
It is designed to scale horizontally -- that is, it scales by deploying more instances. See [Building High-Availability Clusters](/docs/admin/high-availability/).
+18
View File
@@ -0,0 +1,18 @@
---
title: Label
id: label
date: 2018-04-12
full_link: /docs/concepts/overview/working-with-objects/labels
short_description: >
Tags objects with identifying attributes that are meaningful and relevant to users.
aka:
tags:
- fundamental
---
Tags objects with identifying attributes that are meaningful and relevant to users.
<!--more-->
Labels are key/value pairs that are attached to objects such as {{< glossary_tooltip text="Pods" term_id="pod" >}}. They are used to organize and to select subsets of objects.
+17
View File
@@ -0,0 +1,17 @@
---
title: Managed Service
id: managed-service
date: 2018-04-12
full_link:
short_description: >
A software offering maintained by a third-party provider.
aka:
tags:
- extension
---
A software offering maintained by a third-party provider.
<!--more-->
Some examples of Managed Services are AWS EC2, Azure SQL Database, and GCP Pub/Sub, but they can be any software offering that can be used by an application. [Service Catalog](/docs/concepts/service-catalog/) provides a way to list, provision, and bind with Managed Services offered by {{< glossary_tooltip text="Service Brokers" term_id="service-broker" >}}.
+18
View File
@@ -0,0 +1,18 @@
---
title: Node
id: node
date: 2018-04-12
full_link: /docs/concepts/architecture/nodes/
short_description: >
A node is a worker machine in Kubernetes.
aka:
tags:
- fundamental
---
A node is a worker machine in Kubernetes.
<!--more-->
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.
+17
View File
@@ -0,0 +1,17 @@
---
title: Service Broker
id: service-broker
date: 2018-04-12
full_link:
short_description: >
An endpoint for a set of Managed Services offered and maintained by a third-party.
aka:
tags:
- extension
---
An endpoint for a set of {{< glossary_tooltip text="Managed Services" term_id="managed-service" >}} offered and maintained by a third-party.
<!--more-->
{{< glossary_tooltip text="Service Brokers" term_id="service-broker" >}} implement the [Open Service Broker API spec](https://github.com/openservicebrokerapi/servicebroker/blob/v2.13/spec.md) and provide a standard interface for applications to use their Managed Services. [Service Catalog](/docs/concepts/service-catalog/) provides a way to list, provision, and bind with Managed Services offered by Service Brokers.
+21
View File
@@ -0,0 +1,21 @@
---
title: SIG (special interest group)
id: sig
date: 2018-04-12
full_link: https://github.com/kubernetes/community/blob/master/sig-list.md#master-sig-list
short_description: >
Community members who collectively manage an ongoing piece or aspect of the larger Kubernetes open source project.
aka:
tags:
- community
---
{{< glossary_tooltip text="Community members" term_id="member" >}} who collectively manage an ongoing piece or aspect of the larger Kubernetes open source project.
<!--more-->
Members within a SIG have a shared interest in advancing a specific area, such as architecture, API machinery, or documentation.
SIGs must follow the [SIG Governance](https://github.com/kubernetes/community/blob/master/sig-governance.md) guidelines but can have their own contribution policy and channels of communication.
For more information, see the [kubernetes/community](https://github.com/kubernetes/community) repo and the current list of [SIGs and Working Groups](https://github.com/kubernetes/community/blob/master/sig-list.md).
+19
View File
@@ -0,0 +1,19 @@
---
title: Volume
id: volume
date: 2018-04-12
full_link: /docs/concepts/storage/volumes/
short_description: >
A directory containing data, accessible to the containers in a pod.
aka:
tags:
- core-object
- fundamental
---
A directory containing data, accessible to the containers in a {{< glossary_tooltip text="pod" term_id="pod" >}}.
<!--more-->
A Kubernetes volume lives as long as the {{< glossary_tooltip text="pod" term_id="pod" >}} that encloses it. Consequently, a volume outlives any {{< glossary_tooltip text="containers" term_id="container" >}} that run within the {{< glossary_tooltip text="pod" term_id="pod" >}}, and data is preserved across {{< glossary_tooltip text="container" term_id="container" >}} restarts.