Skip to content

Commit 4f7a4d6

Browse files
authored
Merge pull request #283796 from tejaswikolli-web/connectedregistry-QS
Connectedregistry qs
2 parents f0e0dec + 11d6d94 commit 4f7a4d6

11 files changed

+1167
-4
lines changed

articles/container-registry/TOC.yml

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -293,6 +293,16 @@
293293
items:
294294
- name: Deploy connected registry to nested IoT Edge
295295
href: tutorial-deploy-connected-registry-nested-iot-edge-cli.md
296+
- name: Deploy Connected registry Azure arc extension
297+
items:
298+
- name: Secure and deploy Connected registry Arc extension
299+
href: tutorial-connected-registry-arc.md
300+
- name: Sync Connected registry with Azure arc
301+
href: tutorial-connected-registry-sync.md
302+
- name: Upgrade Connected registry with Azure arc
303+
href: tutorial-connected-registry-upgrade.md
304+
- name: Troubleshoot Connected registry with Azure arc
305+
href: troubleshoot-connected-registry-arc.md
296306
- name: Concepts
297307
items:
298308
- name: Access to connected registry
@@ -357,6 +367,11 @@
357367
href: troubleshoot-artifact-streaming.md
358368
- name: Troubleshoot Artifact cache
359369
href: troubleshoot-artifact-cache.md
370+
- name: Glossary
371+
expanded: false
372+
items:
373+
- name: Glossary for Connected registry with Azure Arc
374+
href: connected-registry-glossary.md
360375
- name: Resources
361376
expanded: false
362377
items:
Lines changed: 184 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,184 @@
1+
---
2+
title: "Glossary for connected registry with Azure Arc"
3+
description: "Learn the terms and definitions for the connected registry extension with Azure Arc for a seamless extension deployment."
4+
author: tejaswikolli-web
5+
ms.author: tejaswikolli
6+
ms.service: azure-container-registry
7+
ms.topic: glossary #Don't change
8+
ms.date: 06/18/2024
9+
#customer intent: As a customer, I want to understand the terms and definitions for the connected registry extension with Azure Arc for a successful deployment.
10+
11+
---
12+
13+
# Glossary for Connected registry with Azure Arc
14+
15+
This glossary provides terms and definitions for the connected registry extension with Azure Arc for a seamless extension deployment.
16+
17+
## Glossary of terms
18+
19+
### Auto-upgrade-version
20+
21+
- **Definition:** Automatically upgrade the version of the extension instance.
22+
- **Accepted Values:** `true`, `false`
23+
- **Default Value:** `false`
24+
- **Note:** [Azure Connected Machine agent](/azure/azure-arc/servers/agent-overview) manages the upgrade process and automatic rollback.
25+
26+
### Bring Your Own Certificate (BYOC)
27+
28+
- **Definition:** Allows customers to use their own certificate management service.
29+
- **Accepted Values:** Kubernetes Secret or Public Certificate + Private Key pair
30+
- **Note:** Customer must specify.
31+
32+
### Cert-manager.enabled
33+
34+
- **Definition:** Enables cert-manager service for use with the connected registry, handling the TLS certificate management lifecycle.
35+
- **Accepted Values:** `true`, `false`
36+
- **Default Value:** `true`
37+
- **Note:** Customers can either use the provided cert-manager service at deployment or use theirs (must already be installed).
38+
39+
### Cert-manager.install
40+
41+
- **Definition:** Installs the cert-manager tool as part of the extension deployment.
42+
- **Accepted Values:** `true`, `false`
43+
- **Default Value:** `true`
44+
- **Note:** Must be set to `false` if a customer is using their own cert-manager service.
45+
46+
### Child Registry
47+
48+
- **Description:** A registry that synchronizes with its parent (top-level) registry. The modes of the parent and child registries must match to ensure compatibility.
49+
50+
### Client Token
51+
52+
- **Definition:** Manages client access to a connected registry, allowing for actions on one or more repositories.
53+
- **Accepted Values:** Token name
54+
- **Note:** After creating a token, configure the connected registry to accept it using the `az acr connected-registry update` command.
55+
56+
### Cloud Registry
57+
58+
- **Description:** The ACR registry from which the connected registry syncs artifacts.
59+
60+
### Cluster-name
61+
62+
- **Definition:** The name of the Arc cluster for which the extension is deployed.
63+
- **Accepted Values:** Alphanumerical value
64+
65+
### Cluster-type
66+
67+
- **Definition:** Specifies the type of Arc cluster for the extension deployment.
68+
- **Accepted Values:** `connectedCluster`
69+
- **Default Value:** `connectedCluster`
70+
71+
### Single configuration value (--config)
72+
73+
- **Definition:** The configuration parameters and values for deploying the connected registry extension on the Arc Kubernetes cluster.
74+
- **Accepted Values:** Alphanumerical value
75+
76+
### Connection String
77+
78+
- **Value Type:** Alphanumerical
79+
- **Customer Action:** Must generate and specify
80+
- **Description:** The connection string contains authorization details necessary for the connected registry to securely connect and sync data with the cloud registry using Shared Key authorization. It includes the connected registry name, sync token name, sync token password, parent gateway endpoint, and parent endpoint protocol.
81+
82+
### Connected Registry
83+
84+
- **Description:** The on-premises or remote registry replica that facilitates local access to containerized workloads synchronized from the ACR registry.
85+
86+
### Data-endpoint-enabled
87+
88+
- **Definition:** Enables a [dedicated data endpoint](/azure/container-registry/container-registry-dedicated-data-endpoints) for client firewall configuration.
89+
- **Accepted Values:** `true`, `false`
90+
- **Default Value:** `false`
91+
- **Note:** Must be enabled for a successful creation of a connected registry.
92+
93+
### Extension-type
94+
95+
- **Definition:** Specifies the extension provider unique name for the extension deployment.
96+
- **Accepted Values:** `Microsoft.ContainerRegistry.ConnectedRegistry`
97+
- **Default Value:** `Microsoft.ContainerRegistry.ConnectedRegistry`
98+
99+
### Kubernetes Secret
100+
101+
- **Definition:** A Kubernetes managed secret for securely accessing data across pods within a cluster.
102+
- **Accepted Values:** Secret name
103+
- **Note:** Customer must specify.
104+
105+
### Message TTL (Time To Live)
106+
107+
- **Value Type:** Numerical
108+
- **Default Value/Behavior:** Every two days
109+
- **Description:** Message TTL defines the duration sync messages are retained in the cloud. This value isn't applicable when the sync schedule is continuous.
110+
111+
### Modes
112+
113+
- **Accepted Values:** `ReadOnly` and `ReadWrite`
114+
- **Default Value/Behavior:** `ReadOnly`
115+
- **Description:** Defines the operational permissions for client access to the connected registry. In `ReadOnly` mode, clients can only pull (read) artifacts, which is also suitable for nested scenarios. In `ReadWrite` mode, clients can pull (read) and push (write) artifacts, which is ideal for local development environments.
116+
117+
### Parent Registry
118+
119+
- **Description:** The primary registry that synchronizes with its child connected registries. A single parent registry can have multiple child registries connected to it. In a nested scenario, there can be multiple layers of registries within the hierarchy.
120+
121+
### Protected Settings File (--config-protected-file)
122+
123+
- **Definition:** The file containing the connection string for deploying the connected registry extension on the Kubernetes cluster. This file would also include the Kubernetes Secret or Public Cert + Private Key values pair for BYOC scenarios.
124+
- **Accepted Values:** Alphanumerical value
125+
- **Note:** Customer must specify.
126+
127+
### Public Certificate + Private Key
128+
129+
- **Value Type:** Alphanumerical base64-encoded
130+
- **Customer Action:** Must specify
131+
- **Description:** The public key certificate comprises a pair of keys: a public key available to anyone for identity verification of the certificate holder, and a private key, a unique secret key.
132+
133+
### Pvc.storageClassName
134+
135+
- **Definition:** Specifies the storage class in use on the cluster.
136+
- **Accepted Values:** `standard`, `azurefile`
137+
138+
### Pvc.storageRequest
139+
140+
- **Definition:** Specifies the storage size that the connected registry claims in the cluster.
141+
- **Accepted Values:** Alphanumerical value (for example, “500Gi”)
142+
- **Default Value:** `500Gi`
143+
144+
### Service.ClusterIP
145+
146+
- **Definition:** The IP address within the Kubernetes service cluster IP range.
147+
- **Accepted Values:** IPv4 or IPv6 format
148+
- **Note:** Customer must specify. An incorrect IP not within the range will result in a failed extension deployment.
149+
150+
### Sync Token
151+
152+
- **Definition:** A token used by each connected registry to authenticate with its immediate parent for content synchronization and updates.
153+
- **Accepted Values:** Token name
154+
- **Action:** Customer action required.
155+
156+
### Synchronization Schedule
157+
158+
- **Value Type:** Numerical
159+
- **Default Value/Behavior:** Every minute
160+
- **Description:** The synchronization schedule, set using a cron expression, determines the cadence for when the registry syncs with its parent.
161+
162+
### Synchronization Window
163+
164+
- **Value Type:** Alphanumerical
165+
- **Default Value/Behavior:** Hourly
166+
- **Description:** The synchronization window specifies the sync duration. This parameter is disregarded if the sync schedule is continuous.
167+
168+
### TrustDistribution.enabled
169+
170+
- **Definition:** Trust distribution refers to the process of securely distributing trust between the connected registry and all client nodes within a Kubernetes cluster. When enabled, all nodes are configured with trust distribution.
171+
- **Accepted Values:** `true`, `false`
172+
- **Note:** Customer must choose `true` or `false`.
173+
174+
### TrustDistribution.useNodeSelector
175+
176+
- **Definition:** By default, the trust distribution daemonsets, which are responsible for configuring the container runtime environment (containerd), will run on all nodes in the cluster. However, with this setting enabled, trust distribution is limited to only those nodes that have been specifically labeled with `containerd-configured-by: connected-registry`.
177+
- **Accepted Values:** `true`, `false`
178+
- **Label:** `containerd-configured-by=connected-registry`
179+
- **Command to specify nodes for trust distribution:** `kubectl label node/[node name] containerd-configured-by=connected-registry`
180+
181+
182+
### Registry Hierarchy
183+
184+
- **Description:** The structure of connected registries, where each connected registry is linked to a parent registry. The top parent in this hierarchy is the ACR registry.

articles/container-registry/pull-images-from-connected-registry.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.devlang: azurecli
1010
ms.service: azure-container-registry
1111
---
1212

13-
# Pull images from a connected registry on IoT Edge device
13+
# Pull images from a connected registry on IoT Edge device (To be deprecated)
1414

1515
To pull images from a [connected registry](intro-connected-registry.md), configure a [client token](overview-connected-registry-access.md#client-tokens) and pass the token credentials to access registry content.
1616

0 commit comments

Comments
 (0)