From 1a3dd1d1cf8b5043e56216e6f621c208ba780bef Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B8rn=20Erik=20Pedersen?= Date: Thu, 17 May 2018 23:41:50 +0200 Subject: [PATCH] Remove data/glossary (#8321) It is unused. Glossary should be maintained in the glossary page bundle. --- data/glossary/_example.yml | 27 ------------------- data/glossary/annotation.yaml | 9 ------- data/glossary/application-architect.yaml | 11 -------- data/glossary/application-developer.yaml | 11 -------- data/glossary/approver.yaml | 10 ------- data/glossary/certificate.yaml | 11 -------- data/glossary/cla.yaml | 9 ------- data/glossary/cloud-controller-manager.yml | 13 --------- data/glossary/cloud-provider.yaml | 10 ------- data/glossary/cluster-architect.yaml | 11 -------- data/glossary/cluster-operator.yaml | 15 ----------- data/glossary/cluster.yaml | 9 ------- data/glossary/code-contributor.yaml | 12 --------- data/glossary/configmap.yaml | 13 --------- data/glossary/container-env-variables.yaml | 9 ------- data/glossary/container.yaml | 10 ------- data/glossary/contributor.yaml | 8 ------ data/glossary/controller.yaml | 12 --------- data/glossary/cronjob.yaml | 10 ------- data/glossary/customresourcedefinition.yaml | 14 ---------- data/glossary/daemonset.yaml | 11 -------- data/glossary/deployment.yaml | 11 -------- data/glossary/developer.yaml | 11 -------- data/glossary/docker.yaml | 9 ------- data/glossary/downstream.yaml | 11 -------- .../glossary/dynamic-volume-provisioning.yaml | 11 -------- data/glossary/etcd.yaml | 11 -------- data/glossary/helm-chart.yaml | 10 ------- data/glossary/horizontal-pod-autoscaler.yaml | 17 ------------ data/glossary/image.yaml | 9 ------- data/glossary/ingress.yaml | 13 --------- data/glossary/init-container.yaml | 8 ------ data/glossary/istio.yaml | 13 --------- data/glossary/job.yaml | 11 -------- data/glossary/kops.yaml | 19 ------------- data/glossary/kube-apiserver.yaml | 12 --------- data/glossary/kube-controller-manager.yaml | 14 ---------- data/glossary/kube-proxy.yaml | 10 ------- data/glossary/kube-scheduler.yaml | 13 --------- data/glossary/kubeadm.yaml | 10 ------- data/glossary/kubectl.yaml | 10 ------- data/glossary/kubelet.yaml | 10 ------- data/glossary/kubernetes-api.yaml | 13 --------- data/glossary/label.yaml | 10 ------- data/glossary/maintainer.yaml | 8 ------ data/glossary/managed-service.yaml | 9 ------- data/glossary/member.yaml | 10 ------- data/glossary/minikube.yaml | 10 ------- data/glossary/name.yaml | 10 ------- data/glossary/namespace.yaml | 10 ------- data/glossary/network-policy.yaml | 13 --------- data/glossary/node.yaml | 13 --------- data/glossary/persistent-volume-claim.yaml | 15 ----------- data/glossary/persistent-volume.yaml | 17 ------------ data/glossary/platform-developer.yaml | 11 -------- data/glossary/pod-security-policy.yaml | 19 ------------- data/glossary/pod.yaml | 17 ------------ data/glossary/podpreset.yaml | 12 --------- data/glossary/rbac.yaml | 10 ------- data/glossary/replica-set.yml | 14 ---------- data/glossary/replication-controller.yaml | 10 ------- data/glossary/resource-quota.yaml | 11 -------- data/glossary/reviewer.yaml | 8 ------ data/glossary/secret.yml | 15 ----------- data/glossary/security-context.yaml | 9 ------- data/glossary/selector.yaml | 13 --------- data/glossary/service-account.yaml | 10 ------- data/glossary/service-broker.yaml | 9 ------- data/glossary/service-catalog.yaml | 8 ------ data/glossary/service.yaml | 10 ------- data/glossary/sig.yaml | 12 --------- data/glossary/statefulset.yml | 17 ------------ data/glossary/storage-class.yaml | 11 -------- data/glossary/uid.yaml | 10 ------- data/glossary/upstream.yaml | 11 -------- data/glossary/volume-plugin.yaml | 11 -------- data/glossary/volume.yaml | 17 ------------ data/glossary/wg.yaml | 11 -------- 78 files changed, 912 deletions(-) delete mode 100644 data/glossary/_example.yml delete mode 100644 data/glossary/annotation.yaml delete mode 100644 data/glossary/application-architect.yaml delete mode 100644 data/glossary/application-developer.yaml delete mode 100644 data/glossary/approver.yaml delete mode 100644 data/glossary/certificate.yaml delete mode 100644 data/glossary/cla.yaml delete mode 100644 data/glossary/cloud-controller-manager.yml delete mode 100644 data/glossary/cloud-provider.yaml delete mode 100644 data/glossary/cluster-architect.yaml delete mode 100644 data/glossary/cluster-operator.yaml delete mode 100644 data/glossary/cluster.yaml delete mode 100644 data/glossary/code-contributor.yaml delete mode 100644 data/glossary/configmap.yaml delete mode 100644 data/glossary/container-env-variables.yaml delete mode 100644 data/glossary/container.yaml delete mode 100644 data/glossary/contributor.yaml delete mode 100644 data/glossary/controller.yaml delete mode 100644 data/glossary/cronjob.yaml delete mode 100644 data/glossary/customresourcedefinition.yaml delete mode 100644 data/glossary/daemonset.yaml delete mode 100644 data/glossary/deployment.yaml delete mode 100644 data/glossary/developer.yaml delete mode 100644 data/glossary/docker.yaml delete mode 100644 data/glossary/downstream.yaml delete mode 100644 data/glossary/dynamic-volume-provisioning.yaml delete mode 100644 data/glossary/etcd.yaml delete mode 100644 data/glossary/helm-chart.yaml delete mode 100644 data/glossary/horizontal-pod-autoscaler.yaml delete mode 100644 data/glossary/image.yaml delete mode 100644 data/glossary/ingress.yaml delete mode 100644 data/glossary/init-container.yaml delete mode 100644 data/glossary/istio.yaml delete mode 100644 data/glossary/job.yaml delete mode 100644 data/glossary/kops.yaml delete mode 100644 data/glossary/kube-apiserver.yaml delete mode 100644 data/glossary/kube-controller-manager.yaml delete mode 100644 data/glossary/kube-proxy.yaml delete mode 100644 data/glossary/kube-scheduler.yaml delete mode 100644 data/glossary/kubeadm.yaml delete mode 100644 data/glossary/kubectl.yaml delete mode 100644 data/glossary/kubelet.yaml delete mode 100644 data/glossary/kubernetes-api.yaml delete mode 100644 data/glossary/label.yaml delete mode 100644 data/glossary/maintainer.yaml delete mode 100644 data/glossary/managed-service.yaml delete mode 100644 data/glossary/member.yaml delete mode 100644 data/glossary/minikube.yaml delete mode 100644 data/glossary/name.yaml delete mode 100644 data/glossary/namespace.yaml delete mode 100644 data/glossary/network-policy.yaml delete mode 100644 data/glossary/node.yaml delete mode 100644 data/glossary/persistent-volume-claim.yaml delete mode 100644 data/glossary/persistent-volume.yaml delete mode 100644 data/glossary/platform-developer.yaml delete mode 100644 data/glossary/pod-security-policy.yaml delete mode 100644 data/glossary/pod.yaml delete mode 100644 data/glossary/podpreset.yaml delete mode 100644 data/glossary/rbac.yaml delete mode 100644 data/glossary/replica-set.yml delete mode 100644 data/glossary/replication-controller.yaml delete mode 100644 data/glossary/resource-quota.yaml delete mode 100644 data/glossary/reviewer.yaml delete mode 100644 data/glossary/secret.yml delete mode 100644 data/glossary/security-context.yaml delete mode 100644 data/glossary/selector.yaml delete mode 100644 data/glossary/service-account.yaml delete mode 100644 data/glossary/service-broker.yaml delete mode 100644 data/glossary/service-catalog.yaml delete mode 100644 data/glossary/service.yaml delete mode 100644 data/glossary/sig.yaml delete mode 100644 data/glossary/statefulset.yml delete mode 100644 data/glossary/storage-class.yaml delete mode 100644 data/glossary/uid.yaml delete mode 100644 data/glossary/upstream.yaml delete mode 100644 data/glossary/volume-plugin.yaml delete mode 100644 data/glossary/volume.yaml delete mode 100644 data/glossary/wg.yaml diff --git a/data/glossary/_example.yml b/data/glossary/_example.yml deleted file mode 100644 index c7e6533611..0000000000 --- a/data/glossary/_example.yml +++ /dev/null @@ -1,27 +0,0 @@ -id: _example -name: Example K8s Term -full-link: /docs/link-to-long-dedicated-docs-page -aka: -- Slang K8s Term -- Misnomer -- Formerly Known as Prince -related: -- id-of-less-fancy-k8s-term -- id-of-tangential-term -- id-of-commonly-used-with-term -tags: -- Some Tag -short-description: > - Required. - Markdown allowed (e.g. for cross-linking). - One or two lines that provide a minimum definition. - Do not repeat the term. - Prefer fragments. - End with a period. -long-description: > - Optional. - Markdown allowed. - Longer additional text to appear after (in conjunction with) short description. - Provide where the short description is not sufficient as the intro paragraph to a topic. - Write complete but concise sentences. - **See /_includes/templates/glossary/README.md for the official style guide.** diff --git a/data/glossary/annotation.yaml b/data/glossary/annotation.yaml deleted file mode 100644 index 7d46eb232a..0000000000 --- a/data/glossary/annotation.yaml +++ /dev/null @@ -1,9 +0,0 @@ -id: annotation -name: Annotation -full-link: /docs/concepts/overview/working-with-objects/annotations -tags: -- fundamental -short-description: > - A key-value pair that is used to attach arbitrary non-identifying metadata to objects. -long-description: > - 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. diff --git a/data/glossary/application-architect.yaml b/data/glossary/application-architect.yaml deleted file mode 100644 index 387d4443ea..0000000000 --- a/data/glossary/application-architect.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: application-architect -name: Application Architect -related: - - application-developer -tags: - - user-type -short-description: > - A person responsible for the high-level design of an application. -long-description: > - An architect ensures that an app's implementation allows it to interact with its surrounding components in a scalable, maintainable way. - Surrounding components include databases, logging infrastructure, and other microservices. diff --git a/data/glossary/application-developer.yaml b/data/glossary/application-developer.yaml deleted file mode 100644 index 696e53ef6d..0000000000 --- a/data/glossary/application-developer.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: application-developer -name: Application Developer -related: - - application-architect -tags: - - user-type -short-description: > - A person who writes an application that runs in a Kubernetes cluster. -long-description: > - An application developer focuses on one part of an application. - The scale of their focus may vary significantly in size. diff --git a/data/glossary/approver.yaml b/data/glossary/approver.yaml deleted file mode 100644 index f521314566..0000000000 --- a/data/glossary/approver.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: approver -name: Approver -tags: -- community -short-description: > - A person who can review and approve Kubernetes code contributions. -long-description: > - 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. diff --git a/data/glossary/certificate.yaml b/data/glossary/certificate.yaml deleted file mode 100644 index 856c254d50..0000000000 --- a/data/glossary/certificate.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: certificate -name: Certificate -full-link: /docs/tasks/tls/managing-tls-in-a-cluster/ -tags: -- security -short-description: > - A cryptographically secure file used to validate access to the Kubernetes cluster. -long-description: > - Certificates enable applications within a Kubernetes - cluster to access the Kubernetes API securely. Certificates validate that - clients are allowed to access the API. diff --git a/data/glossary/cla.yaml b/data/glossary/cla.yaml deleted file mode 100644 index 159cb575d9..0000000000 --- a/data/glossary/cla.yaml +++ /dev/null @@ -1,9 +0,0 @@ -id: cla -name: CLA (Contributor License Agreement) -full-link: https://github.com/kubernetes/community/blob/master/CLA.md -tags: -- community -short-description: > - Terms under which a {% glossary_tooltip text="contributor" term_id="contributor" %} grants a license to an open source project for their contributions. -long-description: > - CLAs help resolve legal disputes involving contributed material and intellectual property (IP). diff --git a/data/glossary/cloud-controller-manager.yml b/data/glossary/cloud-controller-manager.yml deleted file mode 100644 index dd819c4214..0000000000 --- a/data/glossary/cloud-controller-manager.yml +++ /dev/null @@ -1,13 +0,0 @@ -id: cloud-controller-manager -name: Cloud Controller Manager -full-link: https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/ -tags: -- core-object -- architecture -- operation -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. -long-description: > - 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. diff --git a/data/glossary/cloud-provider.yaml b/data/glossary/cloud-provider.yaml deleted file mode 100644 index 82ba2f4c22..0000000000 --- a/data/glossary/cloud-provider.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: cloud-provider -name: Cloud Provider -full-link: /docs/concepts/cluster-administration/cloud-providers -tags: -- community -short-description: > - Cloud provider is a company that offers cloud computing platform that can run Kubernetes clusters. -long-description: > - Cloud providers or sometime called Cloud Service Provider (CSPs) provides cloud computing platforms. They may offer services such as Infrastructure as a Service (IaaS) or Platform as a Service (PaaS). Cloud providers host the Kubernetes cluster and also provide services that interact with the cluster, such as Load Balancers, Storage Classes etc. - diff --git a/data/glossary/cluster-architect.yaml b/data/glossary/cluster-architect.yaml deleted file mode 100644 index 14b60a0e18..0000000000 --- a/data/glossary/cluster-architect.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: cluster-architect -name: Cluster Architect -related: - - cluster - - cluster-operator -tags: - - user-type -short-description: > - A person who designs infrastructure that involves one or more Kubernetes clusters. -long-description: > - Cluster architects are concerned with best practices for distributed systems, for example: high availability and security. diff --git a/data/glossary/cluster-operator.yaml b/data/glossary/cluster-operator.yaml deleted file mode 100644 index 82eaa42a60..0000000000 --- a/data/glossary/cluster-operator.yaml +++ /dev/null @@ -1,15 +0,0 @@ -id: cluster-operator -name: Cluster Operator -aka: - - Cluster Administrator -related: - - cluster - - cluster-architect -tags: - - user-type -short-description: > - A person who configures, controls, and monitors clusters. -long-description: | - Their primary responsibility is keeping a cluster up and running, which may involve periodic maintenance activities or upgrades.
- - **NOTE:** Cluster operators are different from the [Operator pattern](https://coreos.com/operators) that extends the Kubernetes API. diff --git a/data/glossary/cluster.yaml b/data/glossary/cluster.yaml deleted file mode 100644 index a86c1ab696..0000000000 --- a/data/glossary/cluster.yaml +++ /dev/null @@ -1,9 +0,0 @@ -id: cluster -name: Cluster -tags: -- fundamental -- operation -short-description: > - A set of machines, called nodes, that run containerized applications managed by Kubernetes. -long-description: > - A cluster has several worker nodes and at least one master node. diff --git a/data/glossary/code-contributor.yaml b/data/glossary/code-contributor.yaml deleted file mode 100644 index f31b196b5c..0000000000 --- a/data/glossary/code-contributor.yaml +++ /dev/null @@ -1,12 +0,0 @@ -id: code-contributor -name: Code Contributor -full-link: /docs/imported/community/devel/ -aka: - - Community Developer -tags: -- community -- user-type -short-description: > - A person who develops and contributes code to the Kubernetes open source codebase. -long-description: > - They are also an active {% glossary_tooltip text="community member" term_id="member" %} who participates in one or more {% glossary_tooltip text="Special Interest Groups (SIGs)" term_id="sig" %}. diff --git a/data/glossary/configmap.yaml b/data/glossary/configmap.yaml deleted file mode 100644 index faebef5297..0000000000 --- a/data/glossary/configmap.yaml +++ /dev/null @@ -1,13 +0,0 @@ -id: configmap -name: ConfigMap -full-link: /docs/tasks/configure-pod-container/configure-pod-configmap/ -related: -- pod -- secret -tags: -- core-object -short-description: > - 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" %}. -long-description: > - Allows you to decouple environment-specific configuration from your {% glossary_tooltip text="container images" term_id="container" %}, so that your applications are easily portable. - When storing confidential data use a [Secret](https://kubernetes.io/docs/concepts/configuration/secret/). diff --git a/data/glossary/container-env-variables.yaml b/data/glossary/container-env-variables.yaml deleted file mode 100644 index ea1fbd2260..0000000000 --- a/data/glossary/container-env-variables.yaml +++ /dev/null @@ -1,9 +0,0 @@ -id: container-env-variables -name: Container Environment Variables -full-link: /docs/concepts/containers/container-environment-variables.md -tags: -- fundamental -short-description: > - Container environment variables are name/value pairs that provide useful information into containers running in a Pod. -long-description: > - Container environment variables provide information that is required by the running containerized applications along with information about important resources to the [Containers] {% glossary_tooltip text="Containers" term_id="container" %}. For example, file system, information about the container itself and other cluster resources such as service endpoints, etc. diff --git a/data/glossary/container.yaml b/data/glossary/container.yaml deleted file mode 100644 index b9682d4b23..0000000000 --- a/data/glossary/container.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: container -name: Container -full-link: /docs/concepts/overview/what-is-kubernetes/#why-containers -tags: -- fundamental -- workload -short-description: > - A lightweight and portable executable image that contains software and all of its dependencies. -long-description: > - Containers decouple applications from underlying host infrastructure to make deployment easier in different cloud or OS environments, and for easier scaling. diff --git a/data/glossary/contributor.yaml b/data/glossary/contributor.yaml deleted file mode 100644 index af005aac50..0000000000 --- a/data/glossary/contributor.yaml +++ /dev/null @@ -1,8 +0,0 @@ -id: contributor -name: Contributor -tags: -- community -short-description: > - Someone who donates code, documentation, or their time to help the Kubernetes project or community. -long-description: > - Contributions include pull requests (PRs), issues, feedback, {% glossary_tooltip text="special interest groups (SIG)" term_id="sig" %} participation, or organizing community events. diff --git a/data/glossary/controller.yaml b/data/glossary/controller.yaml deleted file mode 100644 index b5a5f3d088..0000000000 --- a/data/glossary/controller.yaml +++ /dev/null @@ -1,12 +0,0 @@ -id: controller -name: Controller -full-link: /docs/admin/kube-controller-manager/ -related: -- controller-manager -tags: -- architecture -- fundamental -short-description: > - A control loop that watches the shared state of the cluster through the {% glossary_tooltip text="apiserver" term_id="kube-apiserver" %} and makes changes attempting to move the current state towards the desired state. -long-description: > - Examples of controllers that ship with Kubernetes today are the replication controller, endpoints controller, namespace controller, and serviceaccounts controller. diff --git a/data/glossary/cronjob.yaml b/data/glossary/cronjob.yaml deleted file mode 100644 index 5116cf424a..0000000000 --- a/data/glossary/cronjob.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: cronjob -name: CronJob -full-link: /docs/concepts/workloads/controllers/cron-jobs/ -tags: -- core-object -- workload -short-description: > - Manages a [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/) that runs on a periodic schedule. -long-description: > - Similar to a line in a *crontab* file, a Cronjob object specifies a schedule using the [Cron](https://en.wikipedia.org/wiki/Cron) format. diff --git a/data/glossary/customresourcedefinition.yaml b/data/glossary/customresourcedefinition.yaml deleted file mode 100644 index 8c3bd0a82a..0000000000 --- a/data/glossary/customresourcedefinition.yaml +++ /dev/null @@ -1,14 +0,0 @@ -id: CustomResourceDefinition -name: CustomResourceDefinition -aka: -- CRD -- Formerly Known as ThirdPartyResources (TPR) -tags: -- fundamental -- operation -- extension -full-link: docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/ -short-description: > - Custom code that defines a resource to add to your Kubernetes API server without building a complete custom server. -long-description: > - Custom Resource Definitions let you extend the Kubernetes API for your environment if the publicly supported API resources can't meet your needs. diff --git a/data/glossary/daemonset.yaml b/data/glossary/daemonset.yaml deleted file mode 100644 index cb3374037d..0000000000 --- a/data/glossary/daemonset.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: daemonset -name: DaemonSet -full-link: /docs/concepts/workloads/controllers/daemonset -tags: -- fundamental -- core-object -- workload -short-description: > - Ensures a copy of a {% glossary_tooltip text="Pod" term_id="pod" %} is running across a set of nodes in a {% glossary_tooltip text="cluster" term_id="cluster" %}. -long-description: > - Used to deploy system daemons such as log collectors and monitoring agents that typically must run on every {% glossary_tooltip term_id="node" %}. diff --git a/data/glossary/deployment.yaml b/data/glossary/deployment.yaml deleted file mode 100644 index 4a8d04211a..0000000000 --- a/data/glossary/deployment.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: deployment -name: Deployment -full-link: /docs/concepts/workloads/controllers/deployment/ -tags: -- fundamental -- core-object -- workload -short-description: > - An API object that manages a replicated application. -long-description: > - Each replica is represented by a {% glossary_tooltip term_id="pod" %}, and the Pods are distributed among the nodes of a cluster. diff --git a/data/glossary/developer.yaml b/data/glossary/developer.yaml deleted file mode 100644 index 38534826ab..0000000000 --- a/data/glossary/developer.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: developer -name: Developer (disambiguation) -aka: - - Kubernetes Developer -tags: -- community -- user-type -short-description: > - May refer to: {% 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" %}. -long-description: > - This overloaded term may have different meanings depending on the context diff --git a/data/glossary/docker.yaml b/data/glossary/docker.yaml deleted file mode 100644 index d055a99f42..0000000000 --- a/data/glossary/docker.yaml +++ /dev/null @@ -1,9 +0,0 @@ -id: docker -name: docker -full-link: /docs/reference/kubectl/docker-cli-to-kubectl/ -tags: -- fundamental -short-description: > - Docker is a software technology providing operating-system-level virtualization also known as containers. -long-description: > - 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). diff --git a/data/glossary/downstream.yaml b/data/glossary/downstream.yaml deleted file mode 100644 index dab6d75628..0000000000 --- a/data/glossary/downstream.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: downstream -name: Downstream (disambiguation) -related: -- upstream -tags: -- community -short-description: > - May refer to: code in the Kubernetes ecosystem that depends upon the core Kubernetes codebase or a forked repo. -long-description: | - * 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*. diff --git a/data/glossary/dynamic-volume-provisioning.yaml b/data/glossary/dynamic-volume-provisioning.yaml deleted file mode 100644 index 56fb7a88b9..0000000000 --- a/data/glossary/dynamic-volume-provisioning.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: dynamicvolumeprovisioning -name: Dynamic Volume Provisioning -full-link: /docs/concepts/storage/dynamic-provisioning -tags: -- core-object -- storage -short-description: > - Allows users to request automatic creation of storage {% glossary_tooltip text="Volumes" term_id="volume" %}. -long-description: > - 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. diff --git a/data/glossary/etcd.yaml b/data/glossary/etcd.yaml deleted file mode 100644 index a5e862ba85..0000000000 --- a/data/glossary/etcd.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: etcd -name: etcd -full-link: /docs/tasks/administer-cluster/configure-upgrade-etcd/ -tags: -- architecture -- storage -short-description: > - Consistent and highly-available key value store used as Kubernetes' backing store for all cluster data. -long-description: > - Always have a backup plan for etcd's data for your Kubernetes cluster. - For in-depth information on etcd, see [etcd documentation](https://github.com/coreos/etcd/blob/master/Documentation/docs.md). diff --git a/data/glossary/helm-chart.yaml b/data/glossary/helm-chart.yaml deleted file mode 100644 index 49d916d1af..0000000000 --- a/data/glossary/helm-chart.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: helm-chart -name: Helm Chart -full-link: https://github.com/kubernetes/helm/blob/master/docs/charts.md -tags: -- tool -short-description: > - A package of pre-configured Kubernetes resources that can be managed with the Helm tool. -long-description: | - 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. diff --git a/data/glossary/horizontal-pod-autoscaler.yaml b/data/glossary/horizontal-pod-autoscaler.yaml deleted file mode 100644 index ddd9970d6a..0000000000 --- a/data/glossary/horizontal-pod-autoscaler.yaml +++ /dev/null @@ -1,17 +0,0 @@ -id: horizontal-pod-autoscaler -name: Horizontal Pod Autoscaler -full-link: /docs/tasks/run-application/horizontal-pod-autoscale/ -aka: -- HPA -related: -- pod -- replication-controller -- deployment -tags: -- operation -short-description: > - An API resource that automatically scales the number of pod replicas based on targeted CPU - utilization or custom metric targets. -long-description: > - 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" %}. diff --git a/data/glossary/image.yaml b/data/glossary/image.yaml deleted file mode 100644 index d6ed55e004..0000000000 --- a/data/glossary/image.yaml +++ /dev/null @@ -1,9 +0,0 @@ -id: image -name: Image -tags: -- fundamental -short-description: > - Stored instance of a container that holds a set of software needed to run an application. -long-description: > - 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. - diff --git a/data/glossary/ingress.yaml b/data/glossary/ingress.yaml deleted file mode 100644 index f06031ee2e..0000000000 --- a/data/glossary/ingress.yaml +++ /dev/null @@ -1,13 +0,0 @@ -id: ingress -name: Ingress -full-link: /docs/concepts/services-networking/ingress/ -aka: - - Ingress controller -tags: -- networking -- architecture -- extension -short-description: > - An API object that manages external access to the services in a cluster, typically HTTP. -long-description: > - Ingress can provide load balancing, SSL termination and name-based virtual hosting. diff --git a/data/glossary/init-container.yaml b/data/glossary/init-container.yaml deleted file mode 100644 index 9e6904739e..0000000000 --- a/data/glossary/init-container.yaml +++ /dev/null @@ -1,8 +0,0 @@ -id: init-container -name: Init Container -tags: -- fundamental -short-description: > - One or more initialization containers that must run to completion before any app containers run. -long-description: > - 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. diff --git a/data/glossary/istio.yaml b/data/glossary/istio.yaml deleted file mode 100644 index c05bad8e72..0000000000 --- a/data/glossary/istio.yaml +++ /dev/null @@ -1,13 +0,0 @@ -id: istio -name: Istio -full-link: https://istio.io/docs/concepts/what-is-istio/overview.html -tags: -- networking -- architecture -- extension -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. -long-description: > - 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. diff --git a/data/glossary/job.yaml b/data/glossary/job.yaml deleted file mode 100644 index ec32a36943..0000000000 --- a/data/glossary/job.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: job -name: Job -full-link: /docs/concepts/workloads/controllers/jobs-run-to-completion -tags: -- fundamental -- core-object -- workload -short-description: > - A finite or batch task that runs to completion. -long-description: > - 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. diff --git a/data/glossary/kops.yaml b/data/glossary/kops.yaml deleted file mode 100644 index 67a40892d1..0000000000 --- a/data/glossary/kops.yaml +++ /dev/null @@ -1,19 +0,0 @@ -id: kops -name: Kops -full-link: /docs/getting-started-guides/kops/ -tags: -- tool -- operation -short-description: > - A CLI tool that helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters. *NOTE: Officially supports AWS only, with GCE and VMware vSphere in alpha*. -long-description: | - `kops` provisions your cluster with: - - * Fully automated installation - * DNS-based cluster identification - * Self-healing: 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. diff --git a/data/glossary/kube-apiserver.yaml b/data/glossary/kube-apiserver.yaml deleted file mode 100644 index 788d65f798..0000000000 --- a/data/glossary/kube-apiserver.yaml +++ /dev/null @@ -1,12 +0,0 @@ -id: kube-apiserver -name: kube-apiserver -full-link: /docs/reference/generated/kube-apiserver/ -aka: -- apiserver -tags: -- architecture -- fundamental -short-description: > - Component on the master that exposes the Kubernetes API. It is the front-end for the Kubernetes control plane. -long-description: > - It is designed to scale horizontally -- that is, it scales by deploying more instances. See [Building High-Availability Clusters](/docs/admin/high-availability/). diff --git a/data/glossary/kube-controller-manager.yaml b/data/glossary/kube-controller-manager.yaml deleted file mode 100644 index 577fec68ee..0000000000 --- a/data/glossary/kube-controller-manager.yaml +++ /dev/null @@ -1,14 +0,0 @@ -id: kube-controller-manager -name: kube-controller-manager -full-link: /docs/reference/generated/kube-controller-manager/ -aka: -- controller-manager -related: -- controller -tags: -- architecture -- fundamental -short-description: > - Component on the master that runs {% glossary_tooltip text="controllers" term_id="controller" %}. -long-description: > - 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. diff --git a/data/glossary/kube-proxy.yaml b/data/glossary/kube-proxy.yaml deleted file mode 100644 index b5dc358ffe..0000000000 --- a/data/glossary/kube-proxy.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: kube proxy -name: kube-proxy -full-link: /docs/reference/generated/kube-proxy -tags: -- fundamental -- core-object -short-description: > - `kube-proxy` is a network proxy that runs on each node in the cluster. -long-description: > - `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. diff --git a/data/glossary/kube-scheduler.yaml b/data/glossary/kube-scheduler.yaml deleted file mode 100644 index 126212abf7..0000000000 --- a/data/glossary/kube-scheduler.yaml +++ /dev/null @@ -1,13 +0,0 @@ -id: kube-scheduler -name: kube-scheduler -full-link: /docs/reference/generated/kube-scheduler/ -aka: -- scheduler -tags: -- architecture -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. -long-description: > - 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. diff --git a/data/glossary/kubeadm.yaml b/data/glossary/kubeadm.yaml deleted file mode 100644 index e70b046f19..0000000000 --- a/data/glossary/kubeadm.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: kubeadm -name: Kubeadm -full-link: /docs/admin/kubeadm/ -tags: -- tool -- operation -short-description: > - A tool for quickly installing Kubernetes and setting up a secure cluster. -long-description: > - You can use kubeadm to install both the control plane and the worker node components. diff --git a/data/glossary/kubectl.yaml b/data/glossary/kubectl.yaml deleted file mode 100644 index 825749811c..0000000000 --- a/data/glossary/kubectl.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: kubectl -name: Kubectl -full-link: /docs/user-guide/kubectl-overview/ -tags: -- tool -- fundamental -short-description: > - A command line tool for communicating with a {% glossary_tooltip text="Kubernetes API" term_id="kubernetes-api" %} server. -long-description: > - You can use kubectl to create, inspect, update, and delete Kubernetes objects. diff --git a/data/glossary/kubelet.yaml b/data/glossary/kubelet.yaml deleted file mode 100644 index ed69870cbd..0000000000 --- a/data/glossary/kubelet.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: kubelet -name: Kubelet -full-link: /docs/reference/generated/kubelet -tags: -- fundamental -- core-object -short-description: > - An agent that runs on each node in the cluster. It makes sure that containers are running in a pod. -long-description: > - 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. diff --git a/data/glossary/kubernetes-api.yaml b/data/glossary/kubernetes-api.yaml deleted file mode 100644 index 773da6e516..0000000000 --- a/data/glossary/kubernetes-api.yaml +++ /dev/null @@ -1,13 +0,0 @@ -id: kubernetes-api -name: Kubernetes API -full-link: /docs/concepts/overview/kubernetes-api/ -tags: -- fundamental -- architecture -short-description: > - The application that serves Kubernetes functionality through a RESTful interface and stores the state of the cluster. -long-description: > - 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. diff --git a/data/glossary/label.yaml b/data/glossary/label.yaml deleted file mode 100644 index c74accddb5..0000000000 --- a/data/glossary/label.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: label -name: Label -full-link: /docs/concepts/overview/working-with-objects/labels -tags: -- fundamental -short-description: > - Tags objects with identifying attributes that are meaningful and relevant to users. -long-description: > - 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. diff --git a/data/glossary/maintainer.yaml b/data/glossary/maintainer.yaml deleted file mode 100644 index dc97b11544..0000000000 --- a/data/glossary/maintainer.yaml +++ /dev/null @@ -1,8 +0,0 @@ -id: maintainer -name: Maintainer -tags: -- community -short-description: > - A highly experienced {% glossary_tooltip text="contributor" term_id="contributor" %}, active in multiple areas of Kubernetes, who has cross-area ownership and write access to a project's GitHub repository. -long-description: > - Maintainers work holistically across the project to maintain its health and success and have made substantial contributions, both through code development and broader organizational efforts. diff --git a/data/glossary/managed-service.yaml b/data/glossary/managed-service.yaml deleted file mode 100644 index 409831141f..0000000000 --- a/data/glossary/managed-service.yaml +++ /dev/null @@ -1,9 +0,0 @@ -id: managed-service -name: Managed Service -tags: -- extension -short-description: > - A software offering maintained by a third-party provider. -long-description: > - 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" %}. \ No newline at end of file diff --git a/data/glossary/member.yaml b/data/glossary/member.yaml deleted file mode 100644 index e78ec6bcce..0000000000 --- a/data/glossary/member.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: member -name: Member -tags: -- community -short-description: > - A continuously active {% glossary_tooltip text="contributor" term_id="contributor" %} in the K8s community. -long-description: > - Members can have issues and PRs assigned to them and participate in {% glossary_tooltip text="special interest groups (SIGs)" term_id="sig" %} through GitHub teams. - Pre-submit tests are automatically run for members' PRs. - A member is expected to remain an active contributor to the community. diff --git a/data/glossary/minikube.yaml b/data/glossary/minikube.yaml deleted file mode 100644 index 3f9c01ef51..0000000000 --- a/data/glossary/minikube.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: minikube -name: Minikube -full-link: /docs/getting-started-guides/minikube/ -tags: -- fundamental -- tool -short-description: > - A tool for running Kubernetes locally. -long-description: > - Minikube runs a single-node cluster inside a VM on your computer. diff --git a/data/glossary/name.yaml b/data/glossary/name.yaml deleted file mode 100644 index e918d43357..0000000000 --- a/data/glossary/name.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: name -name: Name -full-link: /docs/concepts/overview/working-with-objects/names -tags: - - fundamental -short-description: > - A client-provided string that refers to an object in a resource URL, such as `/api/v1/pods/some-name`. -long-description: > - 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. diff --git a/data/glossary/namespace.yaml b/data/glossary/namespace.yaml deleted file mode 100644 index 2d976fc881..0000000000 --- a/data/glossary/namespace.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: namespace -name: Namespace -full-link: /docs/concepts/overview/working-with-objects/namespaces -tags: - - fundamental -short-description: > - An abstraction used by Kubernetes to support multiple virtual clusters on the same physical {% glossary_tooltip text="cluster" term_id="cluster" %}. -long-description: > - 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. diff --git a/data/glossary/network-policy.yaml b/data/glossary/network-policy.yaml deleted file mode 100644 index 302c78f289..0000000000 --- a/data/glossary/network-policy.yaml +++ /dev/null @@ -1,13 +0,0 @@ -id: network-policy -name: Network Policy -full-link: /docs/concepts/services-networking/network-policies/ -aka: - - NetworkPolicy -tags: -- networking -- architecture -- extension -short-description: > - A specification of how groups of Pods are allowed to communicate with each other and with other network endpoints. -long-description: > - 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. diff --git a/data/glossary/node.yaml b/data/glossary/node.yaml deleted file mode 100644 index fe0b91a158..0000000000 --- a/data/glossary/node.yaml +++ /dev/null @@ -1,13 +0,0 @@ -id: node -name: Node -full-link: /docs/concepts/architecture/nodes/ -aka: -- Minion -related: -- deployment -tags: -- fundamental -short-description: > - A node is a worker machine in Kubernetes. -long-description: > - 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. diff --git a/data/glossary/persistent-volume-claim.yaml b/data/glossary/persistent-volume-claim.yaml deleted file mode 100644 index 8e7fe41ab7..0000000000 --- a/data/glossary/persistent-volume-claim.yaml +++ /dev/null @@ -1,15 +0,0 @@ -id: persistent-volume-claim -name: Persistent Volume Claim -full-link: /docs/concepts/storage/persistent-volumes/ -related: -- persistent-volume -- statefulset -- deployment -- pod -tags: -- core-object -- storage -short-description: > - Claims storage resources defined in a PersistentVolume so that it can be mounted as a volume in a container. -long-description: | - 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. diff --git a/data/glossary/persistent-volume.yaml b/data/glossary/persistent-volume.yaml deleted file mode 100644 index 00f70a2366..0000000000 --- a/data/glossary/persistent-volume.yaml +++ /dev/null @@ -1,17 +0,0 @@ -id: persistent-volume -name: Persistent Volume -full-link: /docs/concepts/storage/persistent-volumes/ -related: -- statefulset -- deployment -- persistent-volume-claim -- pod -tags: -- core-object -- storage -short-description: > - An API object that represents a piece of storage in the cluster. Available as a general, pluggable resource that persists beyond the lifecycle of any individual {% glossary_tooltip text="Pod" term_id="pod" %}. -long-description: | - PersistentVolumes (PVs) provide an API that abstracts details of how storage is provided from how it is consumed. - PVs are used directly in scenarios where storage can be created ahead of time (static provisioning). - For scenarios that require on-demand storage (dynamic provisioning), PersistentVolumeClaims (PVCs) are used instead. diff --git a/data/glossary/platform-developer.yaml b/data/glossary/platform-developer.yaml deleted file mode 100644 index 8d0c556d06..0000000000 --- a/data/glossary/platform-developer.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: platform-developer -name: Platform Developer -aka: - - Kubernetes Developer - - Extension Developer -tags: - - user-type -short-description: > - A person who customizes the Kubernetes platform to fit the needs of their project. -long-description: > - 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. diff --git a/data/glossary/pod-security-policy.yaml b/data/glossary/pod-security-policy.yaml deleted file mode 100644 index 5c0b721b48..0000000000 --- a/data/glossary/pod-security-policy.yaml +++ /dev/null @@ -1,19 +0,0 @@ -id: pod-security-policy -name: Pod Security Policy -full-link: /docs/concepts/policy/pod-security-policy/ -related: -- pod -- container -- sidecar -- deployment -- statefulset -- security -tags: -- core-object -- fundamental -short-description: > - Enables fine-grained authorization of {% glossary_tooltip term_id="pod" %} creation and updates. -long-description: > - A cluster-level resource that controls security sensitive aspects of the Pod specification. - 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. - Pod Security Policy control is implemented as an optional admission controller. diff --git a/data/glossary/pod.yaml b/data/glossary/pod.yaml deleted file mode 100644 index a5d3f567b9..0000000000 --- a/data/glossary/pod.yaml +++ /dev/null @@ -1,17 +0,0 @@ -id: pod -name: Pod -full-link: /docs/concepts/workloads/pods/pod-overview/ -related: -- container -- sidecar -- deployment -- statefulset -tags: -- core-object -- fundamental -short-description: > - The smallest and simplest Kubernetes object. A Pod represents a set of running {% glossary_tooltip text="containers" term_id="container" %} on your cluster. -long-description: > - 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" %}. diff --git a/data/glossary/podpreset.yaml b/data/glossary/podpreset.yaml deleted file mode 100644 index 57715327c8..0000000000 --- a/data/glossary/podpreset.yaml +++ /dev/null @@ -1,12 +0,0 @@ -id: podpreset -name: PodPreset -tags: -- operation -short-description: > - An API object that injects information such as secrets, volume mounts, - and environment variables into pods at creation time. -long-description: > - 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. diff --git a/data/glossary/rbac.yaml b/data/glossary/rbac.yaml deleted file mode 100644 index e1fde1de8d..0000000000 --- a/data/glossary/rbac.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: rbac -name: RBAC (Role-Based Access Control) -full-link: /docs/admin/authorization/rbac/ -tags: -- security -- fundamental -short-description: > - Manages authorization decisions, allowing admins to dynamically configure access policies through the {% glossary_tooltip text="Kubernetes API" term_id="kubernetes-api" %}. -long-description: > - RBAC utilizes *roles*, which contain permission rules, and *role bindings*, which grant the permissions defined in a role to a set of users. diff --git a/data/glossary/replica-set.yml b/data/glossary/replica-set.yml deleted file mode 100644 index e239a438b7..0000000000 --- a/data/glossary/replica-set.yml +++ /dev/null @@ -1,14 +0,0 @@ -id: replica-set -name: ReplicaSet -full-link: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/ -related: -- replication-controller -tags: -- fundamental -- core-object -- workload -short-description: > - ReplicaSet is the next-generation Replication Controller. -long-description: > - 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. diff --git a/data/glossary/replication-controller.yaml b/data/glossary/replication-controller.yaml deleted file mode 100644 index 04b071a8e4..0000000000 --- a/data/glossary/replication-controller.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: replication-controller -name: Replication Controller -tags: -- workload -- core-object -short-description: > - Kubernetes service that ensures a specific number of instances of a pod are always running. -long-description: > - 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. - diff --git a/data/glossary/resource-quota.yaml b/data/glossary/resource-quota.yaml deleted file mode 100644 index b8e8adf4f8..0000000000 --- a/data/glossary/resource-quota.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: resource-quota -name: Resource Quotas -full-link: /docs/concepts/policy/resource-quotas/ -tags: -- fundamental -- operation -- architecture -short-description: > - Provides constraints that limit aggregate resource consumption per {% glossary_tooltip term_id="namespace" %}. -long-description: > - 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. diff --git a/data/glossary/reviewer.yaml b/data/glossary/reviewer.yaml deleted file mode 100644 index 076b120e02..0000000000 --- a/data/glossary/reviewer.yaml +++ /dev/null @@ -1,8 +0,0 @@ -id: reviewer -name: Reviewer -tags: -- community -short-description: > - A person who reviews code for quality and correctness on some part of the project. -long-description: > - Reviewers are knowledgeable about both the codebase and software engineering principles. Reviewer status is scoped to a part of the codebase. diff --git a/data/glossary/secret.yml b/data/glossary/secret.yml deleted file mode 100644 index c131817f8b..0000000000 --- a/data/glossary/secret.yml +++ /dev/null @@ -1,15 +0,0 @@ -id: secret -name: Secret -full-link: /docs/concepts/configuration/secret/ -related: -- pods -- volume -tags: -- core-object -- security -short-description: > - Stores sensitive information, such as passwords, OAuth tokens, and ssh keys. -long-description: > - 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. diff --git a/data/glossary/security-context.yaml b/data/glossary/security-context.yaml deleted file mode 100644 index 7281a7e6cd..0000000000 --- a/data/glossary/security-context.yaml +++ /dev/null @@ -1,9 +0,0 @@ -id: security-context -name: Security Context -full-link: /docs/tasks/configure-pod-container/security-context/ -tags: -- security -short-description: > - The securityContext field defines privilege and access control settings for a Pod or Container, including the runtime UID and GID. -long-description: > - 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. diff --git a/data/glossary/selector.yaml b/data/glossary/selector.yaml deleted file mode 100644 index e8e7a7b72d..0000000000 --- a/data/glossary/selector.yaml +++ /dev/null @@ -1,13 +0,0 @@ -id: selector -name: Selector -full-link: /docs/concepts/overview/working-with-objects/labels/ -related: -- label -tags: -- fundamental -short-description: > - Allows users to filter a list of resources based on labels. -long-description: > - Selectors are applied when querying lists of resources to filter - them by {% glossary_tooltip text="Labels" term_id="label" - %}. diff --git a/data/glossary/service-account.yaml b/data/glossary/service-account.yaml deleted file mode 100644 index a7fcf3ec05..0000000000 --- a/data/glossary/service-account.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: service-account -name: Service Account -full-link: /docs/tasks/configure-pod-container/configure-service-account/ -tags: -- fundamental -- core-object -short-description: > - Provides an identity for processes that run in a {% glossary_tooltip text="Pod" term_id="pod" %}. -long-description: > - 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" %}. diff --git a/data/glossary/service-broker.yaml b/data/glossary/service-broker.yaml deleted file mode 100644 index 9cdc99bbcb..0000000000 --- a/data/glossary/service-broker.yaml +++ /dev/null @@ -1,9 +0,0 @@ -id: service-broker -name: Service Broker -tags: -- extension -short-description: > - An endpoint for a set of {% glossary_tooltip text="Managed Services" term_id="managed-service" %} offered and maintained by a third-party. -long-description: > - {% 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. \ No newline at end of file diff --git a/data/glossary/service-catalog.yaml b/data/glossary/service-catalog.yaml deleted file mode 100644 index 10cd2288a7..0000000000 --- a/data/glossary/service-catalog.yaml +++ /dev/null @@ -1,8 +0,0 @@ -id: service-catalog -name: Service Catalog -tags: -- extension -short-description: > - 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. -long-description: > - 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. diff --git a/data/glossary/service.yaml b/data/glossary/service.yaml deleted file mode 100644 index 03c3469c53..0000000000 --- a/data/glossary/service.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: service -name: Service -full-link: /docs/concepts/services-networking/service/ -tags: -- fundamental -- core-object -short-description: > - 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. -long-description: > - The access point can be internal or external to the cluster. diff --git a/data/glossary/sig.yaml b/data/glossary/sig.yaml deleted file mode 100644 index 8e9ccef98b..0000000000 --- a/data/glossary/sig.yaml +++ /dev/null @@ -1,12 +0,0 @@ -id: sig -name: SIG (special interest group) -full-link: https://github.com/kubernetes/community/blob/master/sig-list.md#master-sig-list -tags: -- community -short-description: > - {% glossary_tooltip text="Community members" term_id="member" %} who collectively manage an ongoing piece or aspect of the larger Kubernetes open source project. -long-description: | - 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). diff --git a/data/glossary/statefulset.yml b/data/glossary/statefulset.yml deleted file mode 100644 index 542523f5df..0000000000 --- a/data/glossary/statefulset.yml +++ /dev/null @@ -1,17 +0,0 @@ -id: statefulset -name: StatefulSet -full-link: /docs/concepts/workloads/controllers/statefulset/ -related: -- deployment -- pod -tags: -- fundamental -- core-object -- workload -- storage -short-description: > - Manages the deployment and scaling of a set of {% glossary_tooltip text="Pods" term_id="pod" %}, *and provides guarantees about the ordering and uniqueness* of these Pods. -long-description: | - Like a {% glossary_tooltip term_id="deployment" %}, a StatefulSet manages Pods that are based on an identical container spec. Unlike a Deployment, a StatefulSet maintains a sticky identity for each of their Pods. These pods are created from the same spec, but are not interchangeable: each has a persistent identifier that it maintains across any rescheduling. - - A StatefulSet operates under the same pattern as any other Controller. You define your desired state in a StatefulSet *object*, and the StatefulSet *controller* makes any necessary updates to get there from the current state. diff --git a/data/glossary/storage-class.yaml b/data/glossary/storage-class.yaml deleted file mode 100644 index db36fca776..0000000000 --- a/data/glossary/storage-class.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: storageclass -name: Storage Class -full-link: /docs/concepts/storage/storage-classes -tags: -- core-object -- storage -short-description: > - A StorageClass provides a way for administrators to describe different available storage types. -long-description: > - StorageClasses can map to quality-of-service levels, backup policies, or to arbitrary policies determined by cluster administrators. - Each StorageClass contains the fields `provisioner`, `parameters`, and `reclaimPolicy`, which are used when a {% glossary_tooltip text="Persistent Volume" term_id="persistent-volume" %} belonging to the class needs to be dynamically provisioned. Users can request a particular class using the name of a StorageClass object. diff --git a/data/glossary/uid.yaml b/data/glossary/uid.yaml deleted file mode 100644 index 277fb61e62..0000000000 --- a/data/glossary/uid.yaml +++ /dev/null @@ -1,10 +0,0 @@ -id: uid -name: UID -full-link: /docs/concepts/overview/working-with-objects/names -tags: - - fundamental -short-description: > - A Kubernetes systems-generated string to uniquely identify objects. -long-description: > - 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. diff --git a/data/glossary/upstream.yaml b/data/glossary/upstream.yaml deleted file mode 100644 index e2c2cac66d..0000000000 --- a/data/glossary/upstream.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: upstream -name: Upstream (disambiguation) -related: -- downstream -tags: -- community -short-description: > - May refer to: core Kubernetes or the source repo from which a repo was forked. -long-description: | - * In the **Kubernetes Community**: Conversations often use *upstream* to mean the core Kubernetes codebase, which the general ecosystem, other code, or third-party tools relies upon. For example, [community members](#term-member) may suggest that a feature is moved upstream so that it is in the core codebase instead of in a plugin or third-party tool. - * In **GitHub** or **git**: The convention is to refer to a source repo as *upstream*, whereas the forked repo is considered *downstream*. diff --git a/data/glossary/volume-plugin.yaml b/data/glossary/volume-plugin.yaml deleted file mode 100644 index b3ccdaec8d..0000000000 --- a/data/glossary/volume-plugin.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: volumeplugin -name: Volume Plugin -tags: -- core-object -- storage -short-description: > - A Volume Plugin enables integration of storage within a {% glossary_tooltip text="Pod" term_id="pod" %}. -long-description: > - 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. - diff --git a/data/glossary/volume.yaml b/data/glossary/volume.yaml deleted file mode 100644 index b89b139d52..0000000000 --- a/data/glossary/volume.yaml +++ /dev/null @@ -1,17 +0,0 @@ -id: volume -name: Volume -full-link: /docs/concepts/storage/volumes/ -related: -- pod -- container -- secret -tags: -- core-object -- fundamental -short-description: > - A directory containing data, accessible to the containers in a {% glossary_tooltip text="pod" term_id="pod" %}. -long-description: > - 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. diff --git a/data/glossary/wg.yaml b/data/glossary/wg.yaml deleted file mode 100644 index 8237068cf0..0000000000 --- a/data/glossary/wg.yaml +++ /dev/null @@ -1,11 +0,0 @@ -id: wg -name: WG (working group) -full-link: https://github.com/kubernetes/community/blob/master/sig-list.md#master-working-group-list -tags: -- community -short-description: > - Facilitates the discussion and/or implementation of a short-lived, narrow, or decoupled project for a committee, {% glossary_tooltip text="SIG" term_id="sig" %}, or cross-SIG effort. -long-description: | - Working groups are a way of organizing people to accomplish a discrete task, and are relatively easy to create and deprecate when inactive. - - 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).