support alibabacloud oss for image registry#724
support alibabacloud oss for image registry#724openshift-merge-robot merged 6 commits intoopenshift:masterfrom
Conversation
|
Hi @menglingwei. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
replace PR #720 . |
|
/ok-to-test |
|
@menglingwei Can we rebase this to clean up the conflicts? Thanks! |
Yes, i can clean up the conflicts. This PR is a draf PR for openshift/api#1009. So, I think we can merge this PR first? Then I resubmit a new PR for cluster-image-registry-operator. |
ricardomaraschini
left a comment
There was a problem hiding this comment.
Looks good. I haven't found the part where this driver is actually used during the reconciliation. Is that something that is coming next?
| generatedName := false | ||
| // Retry up to 5000 times if we get a naming conflict | ||
| const numRetries = 5000 | ||
| for i := 0; i < numRetries; i++ { |
There was a problem hiding this comment.
I imagine you have copied this from other drivers. Can we simply try it once (instead of 500 times) and return an error in case of a failure? The reconcile cycle will happen again later on and then we retry this. wdyt?
|
@ricardomaraschini You review api PR first , is that ok? When api PR is merged. i will update go.mod dependences. |
|
@menglingwei we don't merge API changes until we have PRs (that have a temporary |
I understand. so i need to fix this drat PR, and make the test run success. and then you will merge the API PR? |
|
@menglingwei Thanks for the efforts here. Please fix the conflicts with a rebase as well as the tests. Then we can perform the necessary tests. |
I got it. i will fix the conflict ASAP |
|
ci/prow/e2e-ovirt job failed. but i don't know how to make this job run success.any suggestions ? |
@kwoodson I fixed the conflicts with rebase master. but I found some jobs also run failed. |
|
https://github.com/openshift/cluster-image-registry-operator/pull/724/commits PRs shouldn't contain merge commits. Please rebase using |
|
@ricardomaraschini Could you comment on the state of this PR? Have you had an opportunity to test? I can assist or if you could point me to the test suite for the image registry and I can perform this. |
|
@kwoodson tests should be part of this PR, it's a new feature and it should have new tests. Manual tests:
|
|
9a6e6a4 to
e857b31
Compare
|
@menglingwei, @kwoodson just create a new cluster successfully. Now we can see that those new policies were created. Thanks. $ aliyun ram GetPolicy \
--PolicyName test-rglgq-openshift-image-registry-installer-cloud-credentials-policy-policy \
--PolicyType Custom \
| jq -r '.DefaultPolicyVersion.PolicyDocument' \
| jq '.Statement[].Action' |grep -E '(Tagging|ListBuckets)'
"oss:PutBucketTagging",
"oss:GetBucketTagging",
"oss:DeleteBucketTagging",
"oss:ListBuckets",
$ BUCKET_NAME=$(oc get configs.imageregistry.operator.openshift.io/cluster -n openshift-image-registry -o jsonpath='{.spec.storage}' |jq -r .oss.bucket)
$ echo $BUCKET_NAME
test-rglgq-image-registry-us-east-1-jknktcahorkmcvlwvnnfgykxrh
$ ./ossutil64 ls oss://${BUCKET_NAME}
Object Number is: 0
1.219796(s) elapsed
$ oc get pods -l docker-registry=default -n openshift-image-registry
NAME READY STATUS RESTARTS AGE
image-registry-77b9bb4bbd-6thxc 1/1 Running 0 38m
image-registry-77b9bb4bbd-c7z8b 1/1 Running 0 38m@xiuwang could you please validate it? @ricardomaraschini @dmage please see the feedback from the final review from QE. /lgtm |
|
/retest-required |
2 similar comments
|
/retest-required |
|
/retest-required |
|
/retest |
1 similar comment
|
/retest |
|
@menglingwei: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
Validate the image registry works well with OSS stoage, the error never shown, $oc get pods -l docker-registry=default -n openshift-image-registry /lgtm |
|
@xiuwang can you please qe-approved this ? |
|
/lgtm cancel |
|
@sferich888 could you please re add px-approved here? This PR went through some changes and ended up loosing all its flags. |
|
/lgtm |
|
/lgtm cancel I was not aware that once I add lgtm the PR is automatically approved. We need to wait for the others' approved flag first. |
|
/label qe-approved |
@ricardomaraschini there is already a |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jianli-wei, kwoodson, menglingwei, mtulio, ricardomaraschini, xiuwang The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Add Alibabacloud oss storage for image resigry operator.