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
* Changes to the run-e2e-kind.sh to
* Changed out echo server image, small edits
* Backed out change in the clean up code.
* Updated the makefile to build the executable
* Address code review comments.
* * Small changes to the e2e script
* Build documentation updates.
* Documentation updates per code review
Fixed errors in the e2e script to load ubuntu:latest image correctly.
* Cleaned up false errors
Rectified use of undefined variable.
go build -race -o _output/bin/mcad-controller-local ./cmd/kar-controllers/
53
76
```
54
77
55
-
Ensure the executables: `deepcopy-gen`, `mcad-controllers` are created in the target output directory:
56
-
```
57
-
$ ls ../_output/bin/
58
-
deepcopy-gen mcad-controller
59
-
$
78
+
Ensure the executables: `deepcopy-gen` and `mcad-controllers` are created in the target output directory:
79
+
80
+
```bash
81
+
multi-cluster-app-dispatcher $ ls _output/bin
82
+
deepcopy-gen mcad-controller
60
83
```
61
84
62
85
### Build the Multi-Cluster-App-Dispatcher Image
63
86
64
-
Run the image build script `image.sh`:
87
+
If you want to run the end to end tests locally, you will need to have the docker daemon running on your workstation, and build the image using docker. Images can also be build using podman for deployment of the MCAD controller on remote clusters.
Note the *image name* and *image tag* from the image build script (`./image.sh`) above. For example the *image name* and *image tag* built after running the example above is `mcad-controller:v1.14`. List the Docker images to ensure the image exists.
91
+
```bash
92
+
# With docker daemon running
93
+
multi-cluster-app-dispatcher % make images
91
94
95
+
....
96
+
97
+
# output from a local branch, MacOS build, local file names replaced with XXXXXXXXXX
98
+
"---"
99
+
"MAKE GLOBAL VARIABLES:"
100
+
""BIN_DIR="_output/bin"
101
+
""GIT_BRANCH="local_e2e_test"
102
+
""RELEASE_VER="v1.29.55"
103
+
""TAG="local_e2e_test-v1.29.55"
104
+
"---"
105
+
# Check for invalid tag name
106
+
t=local_e2e_test-v1.29.55 && [ ${#t}-le 128 ] || { echo"Target name $t has 128 or more chars";false; }
107
+
mkdir -p _output/bin
108
+
Compiling deepcopy-gen...
109
+
Generating deepcopy...
110
+
go build -o _output/bin/deepcopy-gen ./cmd/deepcopy-gen/
Refer to [deployment](../deploy/deployment.md) on how to deploy the `multi-cluster-app-dispatcher` as a controller in Kubernetes.
176
+
177
+
## 3. Running e2e tests locally
178
+
179
+
When running e2e tests, is recommended you restrict the `docker` daemon [cpu and memory resources](https://docs.docker.com/config/containers/resource_constraints/). The recomended settings are:
0 commit comments