-
Notifications
You must be signed in to change notification settings - Fork 946
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
Missing timeout parameter in helm chart for agent-core container in openebs-agents-core deployment #3805
Missing timeout parameter in helm chart for agent-core container in openebs-agents-core deployment #3805
Comments
Thanks for creation this @oleksandr-shalbanov-fntext |
@tiagolobocastro Thank you. I can create pr for adding additional parameters to helm chart. Should I? :) |
That would be awesome, thank you! |
569: feat(chart): add requestTimeout for core-agent container r=tiagolobocastro a=oleksandr-shalbanov-fntext ## Description Adding helm chart value .agents.core.requestTimeout to be able to configure core agent timeout. ## Motivation and Context This is to resolve [#3805](openebs/openebs#3805) issue. ## Regression No ## How Has This Been Tested? Installed OpenEBS with helm chart to my test environment ## Types of changes - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Checklist: - [x] My code follows the code style of this project. - [x] My change requires a change to the documentation. - [x] I have updated the documentation accordingly. - [ ] I have added unit tests to cover my changes. Co-authored-by: Oleksandr Shalbanov <oleksandr.shalbanov@evry.com>
569: feat(chart): add requestTimeout for core-agent container r=oleksandr-shalbanov-fntext a=oleksandr-shalbanov-fntext ## Description Adding helm chart value .agents.core.requestTimeout to be able to configure core agent timeout. ## Motivation and Context This is to resolve [#3805](openebs/openebs#3805) issue. ## Regression No ## How Has This Been Tested? Installed OpenEBS with helm chart to my test environment ## Types of changes - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Checklist: - [x] My code follows the code style of this project. - [x] My change requires a change to the documentation. - [x] I have updated the documentation accordingly. - [ ] I have added unit tests to cover my changes. Co-authored-by: Oleksandr Shalbanov <oleksandr.shalbanov@evry.com>
569: feat(chart): add requestTimeout for core-agent container r=oleksandr-shalbanov-fntext a=oleksandr-shalbanov-fntext ## Description Adding helm chart value .agents.core.requestTimeout to be able to configure core agent timeout. ## Motivation and Context This is to resolve [#3805](openebs/openebs#3805) issue. ## Regression No ## How Has This Been Tested? Installed OpenEBS with helm chart to my test environment ## Types of changes - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Checklist: - [x] My code follows the code style of this project. - [x] My change requires a change to the documentation. - [x] I have updated the documentation accordingly. - [ ] I have added unit tests to cover my changes. Co-authored-by: Oleksandr Shalbanov <oleksandr.shalbanov@evry.com>
Description
I’m currently trying to configure openEBS replicated storage on my on-prem cluster(1.27 k8s based on Oracle Linux 8 )
I’ve installed openebs with the latest helm chart, with the following values:
The installation has finished successfully. I have 4 2TB disks attached to 4 of my nodes.
I’ve labeled them like this: kubectl label node selllvk8swrkr16 openebs.io/engine=mayastor
Expected Behavior
I expect that all disk pools, I create further, work without issues
Current Behavior
When I’m trying to create disk pools, on some nodes disk pull was created successfully, but on some of them I’m getting the following error:
Possible Solution
This could be solved by modifying exec command of agent-core container from openebs-agents-core deployment.
Following strings have to be added:
So I suggest to add the additional parameter to the helm chart values to be able to set
--request-timeout
during installation.The text was updated successfully, but these errors were encountered: