e2e scripts: make setup idempotent and fix test runner credentials#2363
Closed
delthas wants to merge 11 commits intodevelopment/2.14from
Closed
e2e scripts: make setup idempotent and fix test runner credentials#2363delthas wants to merge 11 commits intodevelopment/2.14from
delthas wants to merge 11 commits intodevelopment/2.14from
Conversation
Instead of pruning all unused images (which destroys unrelated local images), remove only the CTST image after loading it into kind. The e2e image was already cleaned up with docker rmi.
Replace kubectl create with create --dry-run=client | kubectl apply or kubectl apply -f so that re-running the setup scripts updates existing resources instead of failing.
Replace the `sed -i 's/sorbet-data/miria-data/g'` workaround with the new PVC_NAME env var from zenko-operator's deploy-sorbet-resources.sh. Both deploys now explicitly specify their PVC_NAME, making the coupling with run-e2e-ctst.sh's claimName visible at a glance. See: scality/zenko-operator#599 Issue: ZKOP-530
Preserve ZENKO_MONGODB_DATABASE if already set instead of always generating a UUID, ensuring re-runs reuse the same database.
Tilt rebuilds the operator image from source, so pre-pulling the release image is redundant.
Skip network round-trip for helm repos already registered. Clone kafka-operator to a persistent directory to avoid re-cloning on every run.
… CRDs Strip stale metadata when copying root-ca secret to avoid resourceVersion conflict. Use kubectl apply --server-side for prometheus and kafka CRDs instead of create-or-replace pattern.
Refactor the action.yaml step loop from a big if block to early exit guards for clarity. Skip deploy-metadata.sh when ring tests are disabled.
Instead of regenerating the keypair secret on every run, check if it already exists and extract the public key from it. This prevents OAEP decryption errors caused by location configs encrypted with a previous keypair.
SCRAM-SHA-512 user registrations are stored in ZooKeeper. The auth ZooKeeper clone was using ephemeral storage, so credentials were lost on pod restart, causing notification-processor-destination4 to fail with SASL authentication errors.
Hardcoded credentials don't survive vault restarts. Read the vault admin key from the management-vault-admin-creds secret instead, matching how the CI run-e2e-ctst.sh script works. Also fix the account name to zenko-ctst to match CI.
Contributor
Hello delthas,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Contributor
Missing Jira issueIt is mandatory to specify a Jira issue in the source branch name I could not find such an issue in |
Contributor
Author
|
Oops this was auto-created. Sorry. 😅 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary