[ci tests] helmfile e2e tests don't use docker cache #3985
Assignees
Comments
godber
pushed a commit
that referenced
this issue
Mar 6, 2025
This PR makes the following changes: - Adds e2e helmfile tests that test teraslice with an encrypted opensearch2 cluster - Adds 3 new configuration settings to the `elasticsearch-next` terafoundation connector - **username:** The username for the client auth - **password:** The password for the client auth - **caCertificate:** The root-ca for validation - #3971 - Fixes issue where helmfile e2e tests wasn't using the docker image cache in ci - #3985 - Bumps the following packages: - release: (minor) **teraslice** from `v2.13.0` to `2.14.0` - bump: (minor) **@terascope/scripts** from `v1.11.1` to `v1.12.0` - bump: (minor) **elasticsearch-store** from `v1.8.4` to `v1.9.0` - bump: (minor) **terafoundation** from `v1.10.4` to `v1.11.0`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our "helm" e2e test in ci don't currently load the service images into kind like other e2e tests with kind do. This causes timeout issues in ci tests (specifically ssl related e2e tests). We just need to adjust some logic that we already currently have and ensure it runs in the TEST_HELM scenario.
The text was updated successfully, but these errors were encountered: