istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix formatting glitch in a few glossary entries.

This commit is contained in:
mtail 2018-08-02 09:53:23 -07:00
parent 3b529341a1
commit a6420a4475
3 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
content/help/glossary/service-name.md
View File

@ -4,4 +4,3 @@ title: Service Name
A unique name for a [service](#service), identifying it within the [service mesh](#service-mesh).
A service may not be renamed and maintain its identity, each service name is unique.
A service may have multiple [versions](#service-version), but a service name is version-independent.
* Service names are accessible in Istio configuration as the `source.service` and `destination.service` [attributes](#attribute).

8
content/help/glossary/workload-principal.md
View File

@ -4,6 +4,8 @@ title: Workload Principal
Identifies the verifiable authority under which a [workload](#workload) runs.
Istio's service-to-service authentication is used to produce the workload principal.
By default workload principals are compliant with the SPIFFE ID format.
* Multiple [workloads](#workload) may share the same workload principal, but each workload has a single canonical workload
principal
* Workload principals are accessible in Istio configuration as the `source.user` and `destination.user` [attributes](#attribute).
- Multiple [workloads](#workload) may share the same workload principal, but each workload has a single canonical workload
principal
- Workload principals are accessible in Istio configuration as the `source.user` and `destination.user` [attributes](#attribute).

9
content/help/glossary/workload.md
View File

@ -2,7 +2,8 @@
title: Workload
---
A process/binary deployed by operators in Istio, typically represented by entities such as containers, pods, or VMs.
* A workload can expose zero or more [service endpoints](#service-endpoint).
* A workload can consume zero or more [services](#service).
* Each workload has a single canonical [service name](#service-name) associated with it, but
may also represent additional service names.
* A workload can expose zero or more [service endpoints](#service-endpoint).
* A workload can consume zero or more [services](#service).
* Each workload has a single canonical [service name](#service-name) associated with it, but
may also represent additional service names.