Explanation

This PR improves error handling in the create, update, and patch operations by implementing proper retry logic for transient errors. Previously, the code had TODO comments indicating the need to determine which errors could be retried. This PR addresses these TODOs by implementing specific logic to identify and handle retryable errors like conflicts, server timeouts, too many requests, and service unavailability.

Additionally, the create operation has been simplified to directly check for the AlreadyExists error from the API server instead of making a separate Get request followed by a Create request.

Related issue

This PR addresses TODO comments found in the code that were highlighting the need for better error handling in the Kubernetes resource operations. It improves the reliability of the application when interacting with Kubernetes API server under load or unstable network conditions.

Proposed Changes

• Added specific error type checking to determine which errors are retryable in all three operations (create, update, patch)
• Improved the create operation to directly use the AlreadyExists error from the Kubernetes API instead of making a separate Get call first
• Added proper handling for various error types with appropriate retry behavior
• Ensured permanent errors (like NotFound or AlreadyExists) are immediately returned without unnecessary retries

Checklist

• I have read the contributing guidelines.
• I have read the PR documentation guide and followed the process including adding proof manifests to this PR.
• This is a bug fix and I have added unit tests that prove my fix is effective.

Signed-off-by: Karthik babu Manam [email protected]