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 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.
87
+
```bash
88
+
# With docker daemon running
89
+
multi-cluster-app-dispatcher % make images
91
90
91
+
#Using podman
92
+
make images-podman
92
93
```
93
-
$ docker images mcad-controller
94
-
REPOSITORY TAG IMAGE ID CREATED SIZE
95
-
mcad-controller v.1.14 1dbf126976cf 11 minutes ago 272MB
96
-
$
97
-
```
94
+
98
95
### Push the Multi-Cluster-App-Dispatcher Image to an Image Repository
99
-
The following example assumes an available `<repository>/mcad-controller` on [Docker Hub](https://hub.docker.com)
100
-
```
101
-
$ docker login
102
-
$ docker push <respository>/mcad-controller:v1.14
96
+
97
+
The following example assumes an available `<repository>/mcad-controller` on [Docker Hub](https://hub.docker.com) and using image version `v1.14`
Refer to [deployment](../deploy/deployment.md) on how to deploy the `multi-cluster-app-dispatcher` as a controller in Kubernetes.
112
+
113
+
## 3. Running e2e tests locally
114
+
115
+
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