Fix manila apiOverride route configuration haproxy timeout annotation under metadata.annotations#689
Conversation
… under metadata.annotations
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: MiguelCarpio The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @MiguelCarpio. Thanks for your PR. I'm waiting for a openstack-k8s-operators 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-sigs/prow repository. |
|
Are you sure the annotation way works at all? In some previous changes for cinder, glance and nove the way to configure the timeout turned out to be different, and the annotation was just the output. See: #596 |
|
/ok-to-test |
|
+1 on @tosky 's comment. While the change itself is syntactical correct, the recommended way to increase the timeout is to rely on |
fultonj
left a comment
There was a problem hiding this comment.
@MiguelCarpio please update as per @fmount's comment if you want to continue with this PR. Thanks.
All right, I will work on that, thank you all!! |
What does this PR do?
Fix manila apiOverride route configuration from the inline JSON format to the proper nested YAML structure with the HAProxy timeout annotation under
metadata.annotationsWhy do we need it?
Base openstackcontrolplane has haproxy timeout directly under route, but the CRD schema requires it to be under
route.metadata.annotations.