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
Note that `helm-controller` depends on [source-controller](https://github.com/fluxcd/source-controller) to acquire the Helm charts from Helm repositories. If `source-controller` is not running on your test cluster, you need to tell `helm-controller` where to find it.
33
44
34
45
Port forward to source-controller artifacts server:
35
46
@@ -43,8 +54,47 @@ Export the local address as `SOURCE_CONTROLLER_LOCALHOST`:
43
54
export SOURCE_CONTROLLER_LOCALHOST=localhost:8080
44
55
```
45
56
57
+
Alternatively, if your test cluster is already running `source-controller` and `helm-controller`, you need to scale down the in-cluster `helm-controller`:
Set the name of the container image to be created from the source code. This will be used when building, pushing and referring to the image on YAML files:
74
+
75
+
```sh
76
+
export IMG=registry-path/helm-controller:latest
77
+
```
78
+
79
+
Build the container image, tagging it as `$(IMG)`:
80
+
81
+
```sh
82
+
make docker-build
83
+
```
84
+
85
+
Push the image into the repository:
86
+
87
+
```sh
88
+
make docker-push
89
+
```
90
+
91
+
**Note**: `make docker-build` will build an image for the `amd64` architecture.
92
+
93
+
94
+
### Deploying into a cluster
95
+
96
+
Deploy `helm-controller` into the cluster that is configured in the local kubeconfig file (i.e. `~/.kube/config`):
0 commit comments