Update rclone configuration for gcs case to assume that gcs bucket use uniform bucket-level access control
This prevent gatling operator from creating no one accessible object in GCS and allows bucket owners to control access permission
Test
built successfully and deployed controller manager
❯ make docker-build
❯ docker tag gatling-operator:20220117-151751 gcr.io/xxxx/gatling-operator:20220117-151751
❯ docker push gcr.io/xxxx/gatling-operator:20220117-151751
The push refers to repository [gcr.io/xxxx/gatling-operator]
ff99425d122b: Pushed
5b1fa8e3e100: Layer already exists
20220117-151751: digest: sha256:1eee753dfb69fc502342f2f112e2272e4f83cbc562e51522773954bfb919134e size: 739
❯ k edit deploy gatling-operator-controller-manager
❯ k get pod
NAME READY STATUS RESTARTS AGE
gatling-operator-controller-manager-74597d47b9-mjcqj 2/2 Running 0 20m
deployed gatling custom resource and confirm that they succeed and created reports in gcs bucket
❯ k get job
NAME COMPLETIONS DURATION AGE
api-load-test-reporter 1/1 24s 14m
api-load-test-runner 1/1 5m20s 19m
❯ gsutil ls gs://gatling-operator-reports2/api-load-test/3393858636/
gs://gatling-operator-reports2/api-load-test/3393858636/index.html
gs://gatling-operator-reports2/api-load-test/3393858636/style/
confirmed that files are able to be downloaded and reports can be seen properly in local environment
❯ gsutil -m cp -r \
"gs://xxxx-gatling-operator-reports2/api-load-test/3393858636/" \
.
If you experience problems with multiprocessing on MacOS, they might be related to https://bugs.python.org/issue33725. You can disable multiprocessing by editing your .boto config or by adding the following flag to your command: `-o "GSUtil:parallel_process_count=1"`. Note that multithreading is still available even if you disable multiprocessing.
Copying gs://gatling-operator-reports2/api-load-test/3393858636/index.html...
Copying gs://gatling-operator-reports2/api-load-test/3393858636/js/all_sessions.js...
Copying gs://gatling-operator-reports2/api-load-test/3393858636/js/assertions.xml...
confirmed that index.html file viewed from authenticated url can not show its contents properly
access to authenticated url is redirected to other domain and so relatively created url for other resources becomes invalid
to make it viewable, we need to create Public URL which is not redirected to other domain
Description
Test