Add GKE credential to jenkinsfile #13087
Open
+6
−2
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
ATTENTION!!
Depends on rancherlabs/corral-packages#71 to be merged in the corral-packages repo
Fixes #rancher/qa-tasks#1641
Supports e2e tests in #12934 by Adding the GKE credentials to the jenkins file
Occurred changes and/or fixed issues
GKE cred was stored in the secrets manager with the jenkins identifier tag for the e2e tests that validate GKE cluster provisioning to be executed in the pipeline that stores cloud credentials
Areas or cases that should be tested
Run all e2e tests via the jenkins pipeline
Areas which could experience regressions
Cluster provisioning tests
Cloud credentials creation tests
Any other tests that rely on authentication with cloud credentials
Checklist