-
Notifications
You must be signed in to change notification settings - Fork 163
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
Fallback to in-tree cloud provider for OTC #5778
Fallback to in-tree cloud provider for OTC #5778
Conversation
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.
/approve
LGTM label has been added. Git tree hash: a37de608a2150d6c539acb60adeed2af30de34cb
|
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: irozzo-1A, xrstf, zreigz 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 |
/retest Review the full test history Silence the bot with an Also, here is a cat. |
In response to this:
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. |
* Fallback to in-tree cloud provider for OTC * Add unit test for isOTC function
What this PR does / why we need it:
When using OpenStack provider with Open Telekom Cloud we have to fallback to the in-tree cloud provider, otherwise services of type LoadBalancer do not work properly due to:
kubernetes/cloud-provider-openstack#960
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
This is a temporary solution and should be removed when/if OTC will have a dedicated K8C provider.
Documentation:
Does this PR introduce a user-facing change?: