Kubetest2 - Create project-specific state store buckets in GCP #11200
Conversation
This file contains 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
Since we use boskos to get a random GCP project, we need to create a bucket per project so that permissions will be setup properly. This matches the existing kubetest1 behavior.
k8s-ci-robot
added
size/L
|
/retest |
olemarkus
approved these changes
Apr 11, 2021
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olemarkus The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
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.
Since we use boskos to get a random GCP project, we need to create a bucket per project so that permissions will be setup properly.
This matches the existing kubetest1 behavior. It turns out kubetest1 never actually used
gs://k8s-kops-gce.Ref: https://github.com/kubernetes/test-infra/blob/726b9ea2a24eaaa152ab6c63f443f45941d45116/kubetest/kops.go#L880-L903
This should fix the gce kubetest2 job: https://testgrid.k8s.io/kops-gce#kops-gce-kubetest2
specifically the permission errors in etcd manager: https://storage.googleapis.com/kubernetes-jenkins/logs/e2e-kops-gce-kubetest2/1380986173320597504/artifacts/34.105.15.245/etcd.log