support alibaba cloud ccm#119
Conversation
|
Hi @gujingit. 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. |
JoelSpeed
left a comment
There was a problem hiding this comment.
Please take a look at the cloud_test file again. There are several tests in there that the alibaba platform is needed to be added to, but I think you've only added the new platform to half of them
| name: cloud-conf | ||
| items: | ||
| - key: cloud.conf | ||
| path: cloud-config.conf No newline at end of file |
There was a problem hiding this comment.
Please ensure all files end with a new line (it helps with git diffs in the future)
| --kubeconfig=/etc/kubernetes/cloud-controller-manager.conf \ | ||
| --address=127.0.0.1 \ | ||
| --allow-untagged-cloud=true \ | ||
| --leader-elect=true \ |
There was a problem hiding this comment.
There are more leader election flags required to be configured, the unit tests should explain the issues (you can also copy/paste the leader election flags from any other platform)
| package cloud | ||
|
|
||
| import ( | ||
| "github.com/openshift/cluster-cloud-controller-manager-operator/pkg/cloud/alibaba" |
There was a problem hiding this comment.
Please move this import into the group with the rest of the cloud providers, it should come before the AWS import on line 9
| isAzureStack: true, | ||
| expected: azurestack.GetResources(), | ||
| }, { | ||
| name: "AlibabaCloud resources are empty", |
There was a problem hiding this comment.
This test description isn't correct
| name: "AlibabaCloud resources are empty", | |
| name: "AlibabaCloud resources returned as expected", |
Never mind this comment, I just merged #121 which removes the extra lists. I think you should be fine after a rebase and all the tests should be covered /ok-to-test |
|
Changes look good, but you'll need to run |
| source /etc/kubernetes/apiserver-url.env | ||
| fi | ||
| exec /cloud-controller-manager \ | ||
| --kubeconfig=/etc/kubernetes/cloud-controller-manager.conf \ |
There was a problem hiding this comment.
do we need this explicit kubeconfig flag given that we specify --use-service-account-credentials=true below?
There was a problem hiding this comment.
It's ok to remove the kubeconfig flag
|
i think we might be having some issues with our usage of |
|
i think this will need to update the https://github.com/openshift/cluster-cloud-controller-manager-operator/blob/master/manifests/0000_26_cloud-controller-manager-operator_01_images.configmap.yaml file as well. |
|
Hi, what's the default image reference for alibaba ccm? https://github.com/openshift/cluster-cloud-controller-manager-operator/blob/0083ec2523f754f7e9e1b6bf861c20db25cf297e/pkg/cloud/cloud_test.go#L44 |
@gujingit Hi! you could use |
|
@gujingit |
|
@kwoodson We have updated the dockerfile of https://github.com/kubernetes/cloud-provider-alibaba-cloud in order to pass the unit tests, please pull the latest code. Thanks. |
|
/approve /hold I just want to check that we have the alibaba CCM included in the release payload before we go ahead with merging this. Otherwise I think it's good to go |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed 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 |
|
@JoelSpeed How do we verify the Alibaba CCM is in the release payload? |
|
@Fedosin has put in the requests for this to be done, perhaps he can give an update |
|
@JoelSpeed I have seen the latest image is being built in the 4.10 image. I saw the I think this PR is ready. |
elmiko
left a comment
There was a problem hiding this comment.
/lgtm
are we including the images yet @JoelSpeed ?
|
The images are still marked as WIP, we need to bring in some changes from the upstream provider to fix the build before we can merge this |
|
@elmiko @JoelSpeed Looks like the fix to the |
good question, i imagine we will need to update our code repo to match but the complicating factor here is the refactor of the code base. if we are good to move forward with testing the latest releases to the ccm then we could manually make a merge from the upstream to our copy. i think @JoelSpeed was looking into this. |
|
@gujingit Now that the CCM has been updated, I found that there are a couple of options that are not supported. These two options are causing a failure to start the CCM: Is there a plan to revisit this PR and test that it works? I also noticed that when launching the container that I received the following error message: I was able to fix this by using |
@kwoodson @mtulio we have added these options, please pull the upstream |
|
Barring any other feedback I believe this is ready to go. |
|
/hold cancel |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@gujingit: The following tests failed, say
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. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
No description provided.