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
fix docker build for UI and bumped some outdated versions in docs and config (#3017)
* fix docker build for UI and bumped some outdated versions in docs and config
* update helm chart image again because of wrong format field
* switch to new registry ghcr.io for e2e test
* update e2e test runner Dockerfile
@@ -276,10 +276,10 @@ Examples for fake K8s objects can be found in:
276
276
277
277
The operator provides reference end-to-end (e2e) tests to
278
278
ensure various infrastructure parts work smoothly together. The test code is available at `e2e/tests`.
279
-
The special `registry.opensource.zalan.do/acid/postgres-operator-e2e-tests-runner` image is used to run the tests. The container mounts the local `e2e/tests` directory at runtime, so whatever you modify in your local copy of the tests will be executed by a test runner. By maintaining a separate test runner image we avoid the need to re-build the e2e test image on every build.
279
+
The special `ghcr.io/zalando/postgres-operator-e2e-tests-runner` image is used to run the tests. The container mounts the local `e2e/tests` directory at runtime, so whatever you modify in your local copy of the tests will be executed by a test runner. By maintaining a separate test runner image we avoid the need to re-build the e2e test image on every build.
280
280
281
-
Each e2e execution tests a Postgres Operator image built from the current git branch. The test
282
-
runner creates a new local K8s cluster using [kind](https://kind.sigs.k8s.io/),
281
+
Each e2e execution tests a Postgres Operator image built from the current git branch.
282
+
The test runner creates a new local K8s cluster using [kind](https://kind.sigs.k8s.io/),
283
283
utilizes provided manifest examples, and runs e2e tests contained in the `tests`
284
284
folder. The K8s API client in the container connects to the `kind` cluster via
285
285
the standard Docker `bridge` network. The kind cluster is deleted if tests
0 commit comments