[ 
https://issues.apache.org/jira/browse/SPARK-56078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dongjoon Hyun reassigned SPARK-56078:
-------------------------------------

    Assignee: Daniel Baron

> Expose failureThreshold and timeoutSeconds in operator livenessProbe schema
> ---------------------------------------------------------------------------
>
>                 Key: SPARK-56078
>                 URL: https://issues.apache.org/jira/browse/SPARK-56078
>             Project: Spark
>          Issue Type: Sub-task
>          Components: Kubernetes
>    Affects Versions: 1.5.0
>            Reporter: Daniel Baron
>            Assignee: Daniel Baron
>            Priority: Trivial
>              Labels: pull-request-available
>
> All {{livenessProbe}} configurations are not exposed in the values schema, 
> making configuring the {{livenessProbe}} difficult when consulting only the 
> information present in 
> [ArtifactHub|https://artifacthub.io/packages/helm/spark-kubernetes-operator/spark-kubernetes-operator?modal=values-schema].
> At my company we recently needed to alter these and did so using patches as 
> we were not aware that these configurations were available. The reason we 
> needed to alter them was due to the livenessProbe eagerly killing our 
> container whenever connections with the Kube API server reset. Being able to 
> set these resolved our issue.
> Users end up patching the configurations manually as they may not be aware 
> that these can easily be set in the `values.yaml` files without opening up 
> the code themselves.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to