Update glossary page (#7547)
Changed some unit and charm names to match what we actually ship now.
This commit is contained in:
committed by
k8s-ci-robot
parent
a6a480bba2
commit
8aaa23971e
@@ -13,9 +13,9 @@ This page explains some of the terminology used in deploying Kubernetes with Juj
|
||||
|
||||
**model** - A collection of charms and their relationships that define a deployment. This includes machines and units. A controller can host multiple models. It is recommended to separate Kubernetes clusters into individual models for management and isolation reasons.
|
||||
|
||||
**charm** - The definition of a service, including its metadata, dependencies with other services, required packages, and application management logic. It contains all the operational knowledge of deploying a Kubernetes cluster. Included charm examples are `kubernetes-core`, `easy-rsa`, `kibana`, and `etcd`.
|
||||
**charm** - The definition of a service, including its metadata, dependencies with other services, required packages, and application management logic. It contains all the operational knowledge of deploying a Kubernetes cluster. Included charm examples are `kubernetes-core`, `easyrsa`, `flannel`, and `etcd`.
|
||||
|
||||
**unit** - A given instance of a service. These may or may not use up a whole machine, and may be colocated on the same machine. So for example you might have a `kubernetes-worker`, and `filebeat`, and `topbeat` units running on a single machine, but they are three distinct units of different services.
|
||||
**unit** - A given instance of a service. These may or may not use up a whole machine, and may be colocated on the same machine. So for example you might have a `kubernetes-worker`, and `etcd`, and `easyrsa` units running on a single machine, but they are three distinct units of different services.
|
||||
|
||||
**machine** - A physical node, these can either be bare metal nodes, or virtual machines provided by a cloud.
|
||||
{% endcapture %}
|
||||
|
||||
Reference in New Issue
Block a user