Merge https://github.com/kubernetes/cloud-provider-openstack:release-1.23 into release-4.10 #167
Conversation
![shiftstack-merge-bot[bot]](https://avatars.githubusercontent.com/u/48560946?s=60&v=4){kind=small}
Co-authored-by: Lingxian Kong <anlin.kong@gmail.com>
Cinder v2 has been deprecated since Pike release, let's use v3.
…etes#1916) * POC PKCS8 * formatting fix with gofmt Co-authored-by: Laurence Gill <laurencegill@users.noreply.github.com>
This PR pinns k3s to v1.23.6+k3s1. We stick with that as long as we can't reliably say that newer versions work well enough for us. In the future, we must change code for k3s-v1.24.0 anywayse, because docker is not supported there anyways. Until we change away from docker we can't update to v1.24.
… not exist (kubernetes#1913) (kubernetes#1918) Co-authored-by: Ismail Alidzhikov <i.alidjikov@gmail.com>
Author: Florin Peter <public@florin-peter.de> Co-authored-by: Florin Peter <public@florin-peter.de>
…rder for node addresses (kubernetes#2031) * Support specifying a sort order for node addresses This introduces a configuration key which influences the way the provider reports the node addresses to the Kubernetes node resource. The default order depends on the hard-coded order the provider queries the addresses and what the cloud returns, which does not guarantee a specific order. To override this behavior it is possible to specify a comma separated list of CIDRs. Essentially, this will sort and group all addresses matching a CIDR in a prioritized manner, where the first item having a higher priority than the last. All non-matching addresses will remain in the same order they are already in. For example, this option can be useful when having multiple or dual-stack interfaces attached to a node and needing a user-controlled, deterministic way of sorting the addresses. * Update gofmt for various files
…1.23 into release-4.10
|
OK, I wanted to check the bot would produce the same PR I did manually in #158. We'll close one of them. |
|
@shiftstack-merge-bot[bot]: No Bugzilla bug is referenced in the title of this pull request. 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. |
openshift-ci
bot
added
the
needs-ok-to-test
|
Hi @shiftstack-merge-bot[bot]. 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. 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. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: shiftstack-merge-bot[bot] The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Dup of #158 |
|
@mandre: Closed this PR. 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. |
No description provided.