-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add huawei cloud controller #10198
Add huawei cloud controller #10198
Conversation
Hi @dabeck. Thanks for your PR. I'm waiting for a kubernetes-sigs 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. Instructions 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. |
## Credentials to authenticate against Keystone API | ||
## All of them are required Per default these values will be | ||
## read from the environment. | ||
# external_huaweicloud_auth_url: "{{ lookup('env','OS_AUTH_URL') }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see a lot of things related to OpenStack from a rapid search it seems to me that huawei cloud is somehow using OpenStack so are those really valid or is it just a copy paste "gone wrong"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is really close to openstack since huaweicloud is based on openstack BUT it is not fully compatible. Especially the loadbalancers are not offering Octavia Support which is a MUST since k8s 1.26 with the openstack provider. That's why huawei introduced it's own cloud provider as kubernetes-sig project.
But I get the point. Maybe we could use the existing OpenStack Provider and make the image field mutable so that one could use the huawei fork!?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the insight well I don't really mind just wanted to make sure it was intentional to leave the reference to Openstack :D
# external_huaweicloud_cloud: "{{ lookup('env','OS_CLOUD') }}" | ||
|
||
## The repo and tag of the external Huawei Cloud Controller image | ||
# external_huawei_cloud_controller_image_repo: "swr.ap-southeast-1.myhuaweicloud.com" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it the official way of pulling the image don't they have it published in a global registry?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
roles/kubernetes-apps/external_cloud_controller/huaweicloud/OWNERS
Outdated
Show resolved
Hide resolved
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution! :D
/lgtm
Hi Could you rebase your PR to fix the CI? 🙏 |
Delete owners who are not responsible here.
20a3ce1
to
15bafef
Compare
Ah there is an error in ansible-lint now :( |
Ah! well now your branch name doesn't play well with our testing scripts apparently, will send a PR for that 👍 |
/lgtm |
Thanks @dabeck |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dabeck, MrFreezeex, yankay 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 |
* Add huaweicloud as external cloud controller * Add huaweicloud example config * Rename AK,SK to ACCESS_KEY and SECRET_KEY * Add reference to huaweicloud * Fix variable naming * Fix env var name * Update example * Fix variable naming * Fix cloud_config path * Add namespace for leader election * Revert reviewers * Delete OWNERS Delete owners who are not responsible here. * Fix build validation
* Add huaweicloud as external cloud controller * Add huaweicloud example config * Rename AK,SK to ACCESS_KEY and SECRET_KEY * Add reference to huaweicloud * Fix variable naming * Fix env var name * Update example * Fix variable naming * Fix cloud_config path * Add namespace for leader election * Revert reviewers * Delete OWNERS Delete owners who are not responsible here. * Fix build validation
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adds the Huawei Cloud Controller which is used for Huawei compatbile cloud environments like Open Telekom Cloud. This is needed because these systems are based on openstack but do NOT support the octavia API. While the Neutron API isn't supported by the openstack provider anymore.
Does this PR introduce a user-facing change?: