Open joseparajelesGL opened 2 years ago
@joseparajelesGL Did you find any temporary solution for this one?
@joseparajelesGL Did you find any temporary solution for this one?
@yliu224 I had to do a patch to the status subresource. You will need an updated version of kubectl (1.24+) or a client that can update status
I used this patch
kubectl patch --subresource status -n $NAMESPACE ScheduledSparkApplication $SCHEDULED_SPARK_APPLICATION --type json -p '[{"op":"replace", "path":"/status/nextRun", "value":"2023-01-01T00:00:00Z"}]'
That will make the system run it next. If you want an specific time feel free to change it to the proper time
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Currently the ScheduledSparkApplication creates a next run on the next window of the cron configuration, could it be possible to have an annotation that tells the controller to trigger a new run? This will be particularly useful when testing application with long cron schedules.