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
Add env files for Kind-in-Prow integration test jobs
The existing `test/e2e-tests-kind.env` is specifically for the `PipelineRun` approach. These new files are for running the e2e tests, via `kind`, in Prow.
There are four new env files - one for just the go e2e tests each for `stable` and `alpha`, and one for just the yaml tests each for `stable` and `alpha`.
Additionally, `examples/v1beta1/taskruns/git-volume.yaml` is moved to `examples/v1beta1/taskruns/no-ci/git-volume.yaml`. This is because Kind nodes don't have `git` installed, which is necessary for git volumes to work. Also, `--ignore-path=/product_uuid` has been added to the Kaniko args in `examples/v1beta1/pipelineruns/pipelinerun.yaml` and `test/yamls/v1beta1/pipelineruns/pipelinerun.yaml` to work around an issue with Kaniko multi-stage builds on Kind (GoogleContainerTools/kaniko#2164).
Signed-off-by: Andrew Bayer <[email protected]>
- --ignore-path=/product_uuid # TODO(abayer): Work around Kaniko multi-stage build issues on Kind: https://github.com/GoogleContainerTools/kaniko/issues/2164
169
170
# kaniko assumes it is running as root, which means this example fails on platforms
170
171
# that default to run containers as random uid (like OpenShift). Adding this securityContext
- --ignore-path=/product_uuid # TODO(abayer): Work around Kaniko multi-stage build issues on Kind: https://github.com/GoogleContainerTools/kaniko/issues/2164
169
170
# kaniko assumes it is running as root, which means this example fails on platforms
170
171
# that default to run containers as random uid (like OpenShift). Adding this securityContext
171
172
# makes it explicit that it needs to run as root.
172
173
securityContext:
173
174
runAsUser: 0
174
175
- name: write-digest
175
176
workingDir: $(workspaces.source.path)
177
+
# TODO(abayer): Using ko:// means we end up rebuilding the image, which can be annoying. Consider alternatives while ensuring
178
+
# we're always replacing the ko:// images with ones already built from our source...
0 commit comments