dongjoon-hyun opened a new pull request, #836:
URL: https://github.com/apache/spark-kubernetes-operator/pull/836

   ### What changes were proposed in this pull request?
   
   This PR aims to add an opt-in Kueue `Workload` informer, enabled by a new 
configuration: `spark.kubernetes.operator.kueue.workloadInformer.enabled` 
(default: `false`).
   
   - When the configuration is enabled, `SparkAppReconciler` and 
`SparkClusterReconciler` watch the `Workload`s that have the 
`spark.operator/spark-app-name` or `spark.operator/spark-cluster-name` label.
   - The Helm chart enables this configuration when 
`operatorRbac.kueue.enabled` is `true`.
   
   Nothing creates a `Workload` yet. Follow-up PRs will use this informer in 
`AppInitStep` and `ClusterInitStep`.
   
   ### Why are the changes needed?
   
   The follow-up PRs will make `AppInitStep` and `ClusterInitStep` wait until 
the `Workload` is admitted. Without this informer, an admission is noticed only 
on the next periodic reconcile, which runs every 1800 seconds by default.
   
   The informer is opt-in because Kueue may be installed for other purposes. 
The default Helm values do not grant access to Kueue `Workload`s. An informer 
that cannot sync makes the health probe fail, and the operator pod would keep 
restarting.
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes, a new configuration with the default value `false`; Helm enables it 
with `operatorRbac.kueue.enabled`.
   
   ### How was this patch tested?
   
   Pass the CIs with the newly added test cases in `SparkAppReconcilerTest` and 
`SparkClusterReconcilerTest`.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Opus 5


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to