-
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 additional metadata configuration options to external Openstack CCM (kubernetes-sigs#6338) #6339
Conversation
Hi @Sryther. 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. |
I change the author mail on my commit. |
/retest |
@Sryther: Cannot trigger testing until a trusted user reviews the PR and leaves an 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. |
@Sryther Thank you for the PR, could you please sign CLA ? |
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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. I understand the commands that are listed here. |
Hello, you tested this against which OpenStack version? and which OpenStack CCM version? Thanks. |
I tested this with OpenStack CCM 1.18.1 and OpenStack (Nova) 2.38. |
@@ -57,3 +57,6 @@ internal-network-name="{{ network_name }}" | |||
{% for network_name in external_openstack_network_public_networks %} | |||
public-network-name="{{ network_name }}" | |||
{% endfor %} | |||
|
|||
[Metadata] | |||
search-order="{{ external_openstack_metadata_search_order }}" |
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.
Can we wrap this with if external_openstack_metadata_search_order is defined
? and make the default value being undefined?
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.
Sure.
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.
Anyway if the value is undefined, the cloud-provider-openstack will use by default search-order=configDrive,metadataService
as mentionned here.
Are you sure you removing the default value won't be ambiguous?
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.
What do you think @alijahnas ?
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.
The default value of configDrive,metadataService is the right one for most deployments. I am not sure in which cases these values will need to be specifically defined. Maybe for optimization.
If the default value of the CCM is the same as the one declared in kubespray-defaults, adding the line won't affect much. I am okay with @Miouge1 to add the wrapping if external_openstack_metadata_search_order is defined
and remove the default. The commented group_vars variable is enough I think.
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.
Alright then, I did the changes :).
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Miouge1, Sryther 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 |
Thanks! |
I rebased because a test was timing out. |
As @alijahnas already lgtm this, let's merge |
* 'master' of https://github.com/kubernetes-sigs/kubespray: Patch Calico for V3.14.0 missing CR and CRD (kubernetes-sigs#6276) Explicitly set ETCDCTL_API and use ETCDCTL_ENDPOINTS (kubernetes-sigs#6327) Add additional metadata configuration options to external Openstack CCM (kubernetes-sigs#6338) (kubernetes-sigs#6339)
…CM (kubernetes-sigs#6338) (kubernetes-sigs#6339) * Add additional metadata configuration option to external Openstack CCM (kubernetes-sigs#6338) * Set the variable external_openstack_metadata_search_order undefined by default
What type of PR is this?
/kind feature
What this PR does / why we need it:
Additional configuration options for external OpenStack CCM:
Which issue(s) this PR fixes:
Fixes #6338
Special notes for your reviewer:
Does this PR introduce a user-facing change?: