Skip to content

Commit

Permalink
fix
Browse files Browse the repository at this point in the history 
Signed-off-by: tiansuo114 <1729765480@qq.com>
  • Loading branch information
@tiansuo114
tiansuo114 committed Oct 27, 2024
1 parent be93e38 commit bcc7fb3
Showing 1 changed file with 18 additions and 43 deletions.
61 changes: 18 additions & 43 deletions docs/installation/installation.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -230,53 +230,28 @@ member3 v1.23.4 Pull True 7m27s

There are 3 clusters named `member1`, `member2` and `member3` have registered with `Push` or `Pull` mode.

### List of Required Images for Karmada Deployment
## Required Images for Karmada Deployment

The following table lists the images required for deploying Karmada, based on the configuration in the `karmada-init.yaml` file:
The following table lists the images required for deploying Karmada:

| Component | Default Image Repository | Default Tag |
| --------------------------------- | -------------------------------------- | ----------------------- |
| **Etcd (Local)** | `etcd` | `latest` |
| **Etcd Init Image (Local)** | `alpine` | `3.19.1` |
| **Karmada API Server** | `kube-apiserver` | `v1.29.6` |
| **Karmada Aggregated API Server** | `karmada/karmada-aggregated-apiserver` | `v${karmadaGitVersion}` |
| **Kube Controller Manager** | `kube-controller-manager` | `v1.30.4` |
| **Karmada Controller Manager** | `karmada/karmada-controller-manager` | `v${karmadaGitVersion}` |
| **Karmada Scheduler** | `karmada/karmada-scheduler` | `v${karmadaGitVersion}` |
| **Karmada Webhook** | `karmada/karmada-webhook` | `v${karmadaGitVersion}` |
| Component | Default Image Registry + Name | Default Tag |
| --------------------------------- | ------------------------------------------------ |-----------------------------|
| **Karmada API Server** | `registry.k8s.io/kube-apiserver` | `v1.29.6` (current release) |
| **Karmada Aggregated API Server** | `docker.io/karmada/karmada-aggregated-apiserver` | `v${karmadaGitVersion}` |
| **Kube Controller Manager** | `registry.k8s.io/kube-controller-manager` | `v1.30.4` (current release) |
| **Karmada Controller Manager** | `docker.io/karmada/karmada-controller-manager` | `v${karmadaGitVersion}` |
| **Karmada Scheduler** | `docker.io/karmada/karmada-scheduler` | `v${karmadaGitVersion}` |
| **Karmada Webhook** | `docker.io/karmada/karmada-webhook` | `v${karmadaGitVersion}` |
| **Etcd (Local)** | `registry.k8s.io/etcd` | `latest` (current release) |
| **Etcd Init Image (Local)** | `docker.io/alpine` | `3.19.1` (current release) |
| **Karmada Agent** | `docker.io/karmada/karmada-agent` | `v${karmadaGitVersion}` |

### Default Image Registries
### Notes

For most Karmada components, the default image registries and repositories are as follows:
Karmada reuses some Kubernetes images, such as `etcd`, `kube-controller-manager`, and `kube-apiserver`(also known as `karmada-apiserver`). These images are fetched from the Kubernetes official image registry (registry.k8s.io) by default.

| Component | Default Image Registry + Name | Default Tag |
| --------------------------------- | ------------------------------------------------ | ----------------------- |
| **Etcd (Local)** | `registry.k8s.io/etcd` | `latest` |
| **Etcd Init Image (Local)** | `docker.io/alpine` | `3.19.1` |
| **Karmada API Server** | `registry.k8s.io/kube-apiserver` | `v1.29.6` |
| **Karmada Aggregated API Server** | `docker.io/karmada/karmada-aggregated-apiserver` | `v${karmadaGitVersion}` |
| **Kube Controller Manager** | `registry.k8s.io/kube-controller-manager` | `v1.30.4` |
| **Karmada Controller Manager** | `docker.io/karmada/karmada-controller-manager` | `v${karmadaGitVersion}` |
| **Karmada Scheduler** | `docker.io/karmada/karmada-scheduler` | `v${karmadaGitVersion}` |
| **Karmada Webhook** | `docker.io/karmada/karmada-webhook` | `v${karmadaGitVersion}` |
Karmada routinely upgrades these involved Kubernetes images and includes them in Karmada's test suite to ensure compatibility and stability.

### Optional External Image Registry
Karmada-maintained images are fetched from the Karmada official image registry (docker.io/karmada). These images include Karmada's components, such as karmada-controller-manager and karmada-scheduler.

The default image registries for Karmada are `docker.io` and `registry.k8s.io`. The images for Etcd, Kube Controller Manager, and Karmada API Server are sourced from `registry.k8s.io`.

If you are using a private image registry, for example, `my.private.registry`, the images will be pulled from this registry instead of the default public registries. The configuration for the private registry is:

```yaml
privateRegistry:
registry: "my.private.registry"
```
In this case, all the images will be pulled from `my.private.registry`:

- **Etcd (Local)**: `my.private.registry/etcd:latest`
- **Karmada API Server**: `my.private.registry/kube-apiserver:v1.29.6`
- And so on for the other components.

These images can be mirrored into your private registry for use in environments with limited or no access to public registries.

**Note**: The tag and repository values are placeholders and should be updated based on your deployment environment and the specific version of Karmada you are deploying.
Various installation tools provided by Karmada support customizing image sources. You can configure to fetch images from private registries or trusted third-party registries. This provides flexibility to ensure smooth deployment of Karmada in different network environments.

0 comments on commit bcc7fb3

Please sign in to comment.