@@ -26,39 +26,39 @@ Support for Helm charts might be dropped in the future.
2626
2727## Quick start
2828
29- ### Option 1: Deploying using Docker image (Recommended for non-developers)
29+ ### Option 1: Deploying using image (Recommended for non-developers)
3030
3131** Requirements:**
32- * Working Docker setup
32+ * Podman (or Docker) is set up
3333* kubeconfig configuration file
34- * quay.io registry credentials in the environment variables REGISTRY_USERNAME and REGISTRY_PASSWORD.
3534
36- Note that ** Podman is currently not supported** for running
37- containerized roxie due to incomplete mapping of user IDs on macOS. This prevents the passing-in of the gcloud
38- configuration directory to be functional within the container, which is required for interacting with GKE clusters.
35+ And, depending on the cluster:
36+ * credentials for the ` quay.io ` registry in the environment variables ` REGISTRY_USERNAME ` and ` REGISTRY_PASSWORD ` .
3937
40- Example for deploying Central and SecuredCluster to the current Kubernetes cluster context:
41- ``` bash
42- docker run --rm -it --privileged \
43- -v ~ /.config/gcloud:/.config/gcloud \
44- -v $KUBECONFIG :/kubeconfig \
45- -e REGISTRY_USERNAME=$REGISTRY_USERNAME \
46- -e REGISTRY_PASSWORD=$REGISTRY_PASSWORD \
47- ghcr.io/stackrox/roxie:latest deploy
48- ```
49-
50- A new roxie image for the current platform can be built using:
38+ Infra OpenShift4 clusters come already equipped with image pull secrets for ` quay.io ` , so in this case
39+ passing of ` REGISTRY_USERNAME ` and ` REGISTRY_PASSWORD ` to the container is not required:
5140
41+ Example for deploying Central and SecuredCluster to an Infra OpenShift 4 cluster:
5242``` bash
53- make docker-build
43+ podman run --rm -it --privileged \
44+ -v $KUBECONFIG :/kubeconfig:U \
45+ -e MAIN_IMAGE_TAG=4.9.2 \
46+ quay.io/rhacs-eng/roxie:latest deploy --resources=auto
5447```
48+ Specify the ` MAIN_IMAGE_TAG ` as desired.
5549
56- This creates two tags:
57- - ` localhost/roxie:latest `
58- - ` localhost/roxie:<version-tag> `
59-
60- Docker images can be built for the platforms ` linux/amd64 ` and ` linux/arm64 ` . See the ` Makefile ` for more
61- docker related targets.
50+ Deploying to a GKE cluster requires passing of some more arguments:
51+ ```
52+ podman run --rm -it --privileged \
53+ -v ~/.config/gcloud:/.config/gcloud:U \
54+ -v $KUBECONFIG:/kubeconfig:U \
55+ -e MAIN_IMAGE_TAG=4.9.2 \
56+ -e REGISTRY_USERNAME=$REGISTRY_USERNAME \
57+ -e REGISTRY_PASSWORD=$REGISTRY_PASSWORD \
58+ quay.io/rhacs-eng/roxie:latest deploy --resources=auto
59+ ```
60+ Note that in this case we also need to pass the gcloud configuration for the authentication towards
61+ the cluster to succeed.
6262
6363### Option 2: Deploying using local build
6464
@@ -80,9 +80,10 @@ Get help:
8080
8181Deploy using:
8282``` bash
83- ./roxie deploy [ < component> ]
83+ MAIN_IMAGE_TAG=4.9.2 ./roxie deploy [ < component> ]
8484```
8585where ` component ` can be ` central ` or ` sensor ` . If not specified, both components will be deployed.
86+ Specify the ` MAIN_IMAGE_TAG ` as desired.
8687
8788Similarly, the deployment(s) can be torn down using:
8889``` bash
@@ -104,6 +105,20 @@ make test # Unit tests
104105make test-e2e # E2E tests (requires a real cluster context)
105106```
106107
108+ A new roxie image for the current platform can be built using:
109+
110+ ``` bash
111+ make docker-build
112+ ```
113+
114+ This creates two tags:
115+ - ` localhost/roxie:latest `
116+ - ` localhost/roxie:<version-tag> `
117+
118+ Docker images can be built for the platforms ` linux/amd64 ` and ` linux/arm64 ` . See the ` Makefile ` for more
119+ docker related targets.
120+
121+
107122## Testing (E2E)
108123
109124The E2E suite expects a valid ` kubectl ` context.
0 commit comments