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
This guide describes how to build and deploy the AWS provider extension to a remote Kubernetes cluster for development and testing.
4
+
5
+
## Prerequisites
6
+
7
+
A Gardener installation deployed remotely following the [Gardener Remote Setup Guide](https://gardener.cloud/docs/gardener/deployment/getting_started_remotely/)
8
+
9
+
**Important:** Ensure your `kubectl` context is set to the correct remote cluster before running any commands. The deployment process automatically detects the cluster's registry URL from the active kubeconfig.
10
+
11
+
## Building and Deploying
12
+
13
+
### Deploy Everything
14
+
15
+
To build Docker images, Helm charts, and deploy the extension in one command:
16
+
17
+
```bash
18
+
make deploy-remote
19
+
```
20
+
21
+
This will:
22
+
1. Build the provider and admission Docker images
23
+
2. Push images to the cluster's registry
24
+
3. Package the Helm charts
25
+
4. Push charts to the cluster's registry
26
+
5. Generate the extension manifest with correct registry references
27
+
6. Apply the extension to the cluster
28
+
29
+
### Individual Steps
30
+
31
+
You can also run individual steps:
32
+
33
+
```bash
34
+
# Build Docker images
35
+
make docker-images
36
+
37
+
# Push Docker images
38
+
make docker-push
39
+
40
+
# Build Helm charts
41
+
make helm-charts
42
+
43
+
# Push Helm charts
44
+
make helm-push
45
+
46
+
# Generate extension manifest
47
+
make extension-manifest
48
+
49
+
# Apply extension to cluster
50
+
make extension-apply
51
+
```
52
+
53
+
## Platform-Specific Notes
54
+
55
+
### ARM Macs (Apple Silicon)
56
+
57
+
When building on ARM Macs (M1/M2/M3), you must specify the target platform as `linux/amd64` since Kubernetes clusters typically run on AMD64 architecture:
58
+
59
+
```bash
60
+
TARGET_PLATFORMS=linux/amd64 make deploy-remote
61
+
```
62
+
63
+
Or for individual steps:
64
+
65
+
```bash
66
+
TARGET_PLATFORMS=linux/amd64 make docker-images
67
+
make docker-push helm-charts helm-push extension-manifest extension-apply
68
+
```
69
+
70
+
## Generated Artifacts
71
+
72
+
All build artifacts are placed in the `remote/` directory (gitignored):
73
+
-`remote/*.tgz` - Helm chart packages
74
+
-`remote/extension.yaml` - Generated extension manifest with registry URLs
75
+
76
+
## Registry Configuration
77
+
78
+
The deployment automatically derives the registry URL from your cluster's API server:
79
+
- API server: `api.example.shoot.dev.k8s-hana.ondemand.com`
0 commit comments