[🚀 Feature]: Support livenessProbe for the nodes in the Helm Chart #1895
Comments
|
@brunobritorj, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
In the Helm Chart, there was no ```livenessProbe``` support for option
```chromeNode```, ```firefoxNode```, and ```edgeNode```.
This commit adds these three Helm Chart values:
- ```chromeNode.livenessProbe: {}```
- ```firefoxNode.livenessProbe {}```
- ```chromeNode.livenessProbe: {}```
The bellow properties will end up in the pod livenessProbe for the
respective node pod.
Fixes SeleniumHQ#1895
In the Helm Chart, there was no ```livenessProbe``` support for option
```chromeNode```, ```firefoxNode```, and ```edgeNode```.
This commit adds these three Helm Chart values:
- ```chromeNode.livenessProbe: {}```
- ```firefoxNode.livenessProbe {}```
- ```edgeNode.livenessProbe: {}```
The bellow properties will end up in the pod livenessProbe for the
respective node pod.
Fixes SeleniumHQ#1895
In the Helm Chart, there was no ```livenessProbe``` support for option
```chromeNode```, ```firefoxNode```, and ```edgeNode```.
This commit adds these three Helm Chart values:
- ```chromeNode.livenessProbe: {}```
- ```firefoxNode.livenessProbe {}```
- ```edgeNode.livenessProbe: {}```
The bellow properties will end up in the pod livenessProbe for the
respective node pod.
Fixes SeleniumHQ#1895
In the Helm Chart, there was no ```livenessProbe``` support for option
```chromeNode```, ```firefoxNode```, and ```edgeNode```.
This commit adds these three Helm Chart values:
- ```chromeNode.livenessProbe: {}```
- ```firefoxNode.livenessProbe {}```
- ```edgeNode.livenessProbe: {}```
The bellow properties will end up in the pod livenessProbe for the
respective node pod.
Fixes #1895
Co-authored-by: Diego Molina <[email protected]>
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Feature and motivation
Currently, there is only
livenessProbeoption in the Helm Chart values for therouterandhubcomponents, there is no way to add the probe tochromeNode,firefoxNode, andedgeNode.Usage example
Currently, common properties such as
imageName,annotations,labels,resources,portsare supported and placed into the first level in each node. So, thevalues.yamlfile could be adapted to supportlivenessProbe:The text was updated successfully, but these errors were encountered: