Describe the request
Currently the Splunk operator for K8s deploys probes for readiness, startup and liveness. These all work well however within a search head cluster I have some additional customisations I would like.
Expected behavior
I would like to further customize the readinessProbe for search heads in particular, within an SHC there is the concept that a search head member can move into "ManualDetention" during a rolling restart.
During this time period the search head cannot run searches, and I'd prefer to not have the load balancer send traffic to the said search head, therefore I'd like to customise the probe to handle this scenario.
Splunk setup on K8S
Search head clusters have this feature on K8s, that's the only place I'd like to customize the probe on for now.
Reproduction/Testing steps
N/A
K8s environment
N/A
Proposed changes(optional)
Allow an easy method to specify probes to be used by any CRD
gjanders
commented
6 months ago
Please select the type of request
Enhancement
Tell us more
Describe the request Currently the Splunk operator for K8s deploys probes for readiness, startup and liveness. These all work well however within a search head cluster I have some additional customisations I would like.
Expected behavior I would like to further customize the readinessProbe for search heads in particular, within an SHC there is the concept that a search head member can move into "ManualDetention" during a rolling restart. During this time period the search head cannot run searches, and I'd prefer to not have the load balancer send traffic to the said search head, therefore I'd like to customise the probe to handle this scenario.
Splunk setup on K8S Search head clusters have this feature on K8s, that's the only place I'd like to customize the probe on for now.
Reproduction/Testing steps N/A
K8s environment N/A
Proposed changes(optional) Allow an easy method to specify probes to be used by any CRD
K8s collector data(optional) N/A
Additional context(optional) For the idea of having a readiness probe that checks the SHC status before declaring the SHC member "ready", this is raised as https://github.com/splunk/splunk-operator/issues/1322