Add container probes for the Server RGW containers. Each probe is an httpGet to the /swift/healthcheck API which returns always returns status 200 OK when responding.
For now, the probes are disabled by default and will be enabled by default in the future (except the startup probe).
The probes are not exposed in the solution file, instead they can be customized using a custom values.yaml file.
Type of change
[ ] Bug fix (non-breaking change that fixes an issue)
[X] New feature (non-breaking change that adds new functionality)
[ ] Breaking change (bug fix or new feature that breaks existing functionality)
[ ] Third-party dependency update
[ ] Documentation additions or improvements
[ ] Code quality improvements to existing code or test additions/updates
Applicable issues
This change fixes an issue: CORTX-32850
How was this tested?
Deployed with defaults, no probes defined
Deploy with probes on, confirmed statefulset defines probes
Manually caused probes to fail by attaching gdb to radosgw process to make it hang
Defined custom probes and observed they were applied correctly
Defined custom probes that failed intentionally, observed containers restarted, not ready, etc.
Additional information
The probes are currently disabled for now so we can gather some experience as to what the right default settings are. Once we have a better sense of the correct default values, we can enable the liveness and readiness probes by default (leaving startup disabled, assuming it's not really needed).
The custom probes do not support templates, it would be nice if the did. Consider that for future updates.
Checklist
[X] The change is tested and works locally.
[ ] New or changed settings in the solution YAML are documented clearly in the README.md file.
Description
Add container probes for the Server RGW containers. Each probe is an
httpGetto the/swift/healthcheckAPI which returns always returns status200 OKwhen responding.For now, the probes are disabled by default and will be enabled by default in the future (except the startup probe).
The probes are not exposed in the solution file, instead they can be customized using a custom values.yaml file.
Type of change
Applicable issues
How was this tested?
Additional information
The probes are currently disabled for now so we can gather some experience as to what the right default settings are. Once we have a better sense of the correct default values, we can enable the liveness and readiness probes by default (leaving startup disabled, assuming it's not really needed).
The custom probes do not support templates, it would be nice if the did. Consider that for future updates.
Checklist
If this change requires newer CORTX or third party image versions:
imagefields in solution.example.yaml have been updated to use the required versions.appVersionfield of the Helm chart has been updated to use the new CORTX version.If this change addresses a CORTX Jira issue:
CORTX-XXXXX:)View rendered charts/cortx/README.md