From 956b3adc3bc4716615ba72fdc23f0d63ac04ba49 Mon Sep 17 00:00:00 2001 From: Silvano Cirujano Cuesta Date: Mon, 10 Feb 2025 16:39:44 +0100 Subject: [PATCH] feat(onboarding): add legend Signed-off-by: Silvano Cirujano Cuesta --- .../workload/workload-orchestration-edge-onboarding.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/system-design/orchestration/workload/workload-orchestration-edge-onboarding.md b/system-design/orchestration/workload/workload-orchestration-edge-onboarding.md index 77cb6da..56a53e4 100644 --- a/system-design/orchestration/workload/workload-orchestration-edge-onboarding.md +++ b/system-design/orchestration/workload/workload-orchestration-edge-onboarding.md @@ -13,6 +13,10 @@ In order for the workload orchestration solution to manage the edge device's wor 1. The device's management client receives the URL for the Git repository containing its desired state and an associated access token for authentication 1. The [device capabilities](./device-capability-reporting.md) information is sent from the device to the workload orchestration web service using the [Device API](../../margo-api-reference/workload-api/device-api/device-capabilities.md) +> Note: +> 🔐 Indicates communication is secure and requires authentication/authorization. +> 🔓 Indicates communication is secure but DOES NOT require authentication/authorization. + ``` mermaid sequenceDiagram %%{init: {'sequence': {'mirrorActors': false}}}%%