You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/book/src/02_topics/04_embedded-registry.md
+15-1Lines changed: 15 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,12 @@
1
1
# Configuring Embedded Registry in RKE2
2
2
3
3
## Overview
4
+
4
5
RKE2 allows users to enable an **embedded registry** on control plane nodes. When the `embeddedRegistry` option is set to `true` in the `serverConfig`, users can configure the registry using the `PrivateRegistriesConfig` field.
5
6
The process follows [RKE2 docs](https://docs.rke2.io/install/registry_mirror).
6
7
7
8
## Enabling Embedded Registry
9
+
8
10
To enable the embedded registry, set the `embeddedRegistry` field to `true` in the `serverConfig` section of the `RKE2ControlPlane` configuration:
9
11
10
12
```yaml
@@ -18,6 +20,7 @@ spec:
18
20
```
19
21
20
22
## Configuring Private Registries
23
+
21
24
Once the embedded registry is enabled, you can configure private registries using the `PrivateRegistriesConfig` field in `RKE2ConfigSpec`. This field allows you to define registry mirrors, authentication, and TLS settings.
22
25
23
26
Example:
@@ -38,14 +41,25 @@ spec:
38
41
"myregistry.example.com":
39
42
authSecret:
40
43
name: my-registry-secret
44
+
namespace: my-secrets-namespace
41
45
tls:
42
46
tlsConfigSecret:
43
47
name: my-registry-tls-secret
48
+
namespace: my-secrets-namespace
44
49
insecureSkipVerify: false
45
50
```
46
51
47
52
## TLS Secret Format
53
+
48
54
When configuring the `tlsConfigSecret`, ensure the secret contains the following keys:
55
+
49
56
- **`ca.crt`** – CA certificate
50
57
- **`tls.key`** – TLS private key
51
-
- **`tls.crt`** – TLS certificate
58
+
- **`tls.crt`** – TLS certificate
59
+
60
+
## Auth Secret Format
61
+
62
+
When configuring the `authSecret`, ensure the secret contains the following keys:
63
+
64
+
- **`username` and `password`** - When using Basic Auth credentials
65
+
- **`identity-token`** - When using a personal access token
0 commit comments