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: content/kubeone/main/guides/registry-configuration/_index.en.md
+43-21Lines changed: 43 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,36 +37,58 @@ This guide assumes that:
37
37
If you don't have an image registry, you can check out the
38
38
[Docker Registry][docker-reg-guide] as a possible solution.
39
39
40
-
## Preloading Images
40
+
## Mirroring Images with `kubeone mirror-images`
41
41
42
-
Another prerequisites for this guide to work is that your image registry has
43
-
all images needed for your cluster to work preloaded.
42
+
KubeOne provides a built-in command `kubeone mirror-images` to simplify mirroring all required images (Kubernetes core components, CNI plugins, etc.) to your private registry. This command replaces the older `image-loader.sh` script and supports advanced filtering and multi-version mirroring.
44
43
45
-
To make this task easier, we provide the image loader script that:
44
+
### Prerequisites
46
45
47
-
* pulls all images used by components deployed by KubeOne (CNI,
48
-
metrics-server...) and Kubeadm (Kubernetes core components and CoreDNS)
49
-
* re-tag those images so the image registry (e.g. `docker.io`) is replaced
50
-
with the image registry provided by the user
51
-
* push re-tagged images to your (mirror) image registry
46
+
1.**Registry Setup**: Ensure your registry is accessible by all cluster nodes and supports TLS if using containerd.
47
+
2.**Authentication**: The registry must allow unauthenticated access (support for credentials is planned for future releases).
48
+
3.**KubeOne CLI**: Use KubeOne v1.5.0 or newer.
52
49
53
-
The image loader script (`image-loader.sh`) comes in the KubeOne release
54
-
archive, under the `hack` directory. It can also be found on [GitHub in the
55
-
`hack` directory][img-loader]. If you're downloading the script from GitHub,
56
-
it's recommended to switch to the appropriate tag depending on which KubeOne
57
-
version you're using.
50
+
### Usage
58
51
59
-
Once you have downloaded the script, you can run it in the following way.
60
-
Make sure to replace `KUBERNETES_VERSION` with the Kubernetes version you plan
61
-
to use (without the `v` prefix), as well as, replace the `TARGET_REGISTRY` with
62
-
the address to your image registry.
52
+
The `kubeone mirror-images` command pulls, re-tags, and pushes images to your registry. Use the following syntax:
63
53
54
+
```bash
55
+
kubeone mirror-images \
56
+
[--filter base,optional,control-plane] \
57
+
[--kubernetes-versions v1.29.4,v1.28.8] \
58
+
[--insecure] # Allow pushing to insecure registries (HTTP) \
Copy file name to clipboardExpand all lines: content/kubeone/v1.11/guides/registry-configuration/_index.en.md
+43-21Lines changed: 43 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,36 +37,58 @@ This guide assumes that:
37
37
If you don't have an image registry, you can check out the
38
38
[Docker Registry][docker-reg-guide] as a possible solution.
39
39
40
-
## Preloading Images
40
+
## Mirroring Images with `kubeone mirror-images`
41
41
42
-
Another prerequisites for this guide to work is that your image registry has
43
-
all images needed for your cluster to work preloaded.
42
+
KubeOne provides a built-in command `kubeone mirror-images` to simplify mirroring all required images (Kubernetes core components, CNI plugins, etc.) to your private registry. This command replaces the older `image-loader.sh` script and supports advanced filtering and multi-version mirroring.
44
43
45
-
To make this task easier, we provide the image loader script that:
44
+
### Prerequisites
46
45
47
-
* pulls all images used by components deployed by KubeOne (CNI,
48
-
metrics-server...) and Kubeadm (Kubernetes core components and CoreDNS)
49
-
* re-tag those images so the image registry (e.g. `docker.io`) is replaced
50
-
with the image registry provided by the user
51
-
* push re-tagged images to your (mirror) image registry
46
+
1.**Registry Setup**: Ensure your registry is accessible by all cluster nodes and supports TLS if using containerd.
47
+
2.**Authentication**: The registry must allow unauthenticated access (support for credentials is planned for future releases).
48
+
3.**KubeOne CLI**: Use KubeOne v1.5.0 or newer.
52
49
53
-
The image loader script (`image-loader.sh`) comes in the KubeOne release
54
-
archive, under the `hack` directory. It can also be found on [GitHub in the
55
-
`hack` directory][img-loader]. If you're downloading the script from GitHub,
56
-
it's recommended to switch to the appropriate tag depending on which KubeOne
57
-
version you're using.
50
+
### Usage
58
51
59
-
Once you have downloaded the script, you can run it in the following way.
60
-
Make sure to replace `KUBERNETES_VERSION` with the Kubernetes version you plan
61
-
to use (without the `v` prefix), as well as, replace the `TARGET_REGISTRY` with
62
-
the address to your image registry.
52
+
The `kubeone mirror-images` command pulls, re-tags, and pushes images to your registry. Use the following syntax:
63
53
54
+
```bash
55
+
kubeone mirror-images \
56
+
[--filter base,optional,control-plane] \
57
+
[--kubernetes-versions v1.29.4,v1.28.8] \
58
+
[--insecure] # Allow pushing to insecure registries (HTTP) \
0 commit comments