kubeflow / kubeflow/spark-operator

Use RequeueAfter after instead of Requeue

Open
#2,991 1 comment 0 reactions 0 assignees View on GitHub
kind/bug
Dominant language
Python
Stars
3.2k
Forks
1.5k
Avg merge
5d 10h
Merged PRs (30d)
13

Description

### What happened?

With the update to K8s version 1.35, Requeue is now deprecated, we need to explictly define when to requeue.

https://github.com/kubeflow/spark-operator/blob/e2ee1635c1675c28c9002d50b40fbb9f30543cb6/.golangci.yaml#L51-L56

### Reproduction Code

_No response_

### Expected behavior

_No response_

### Actual behavior

_No response_

### Environment & Versions

- Kubernetes Version:
- Spark Operator Version:
- Apache Spark Version:

### Additional context

_No response_

### Impacted by this bug?

Give it a 👍 We prioritize the issues with most 👍

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the linked .golangci.yaml lines and locating the controller code that uses Requeue. Identify each affected requeue path, define the intended delay with RequeueAfter, and run the repository's existing checks to confirm the deprecation warning is resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.