Backend for delete functionality

[Shrutim1505]

Description:
This PR introduces the backend implementation for the delete functionality. It includes the necessary route, controller logic, and service integration to handle delete operations securely and efficiently.

Changes Made:

Added DELETE API endpoint in the backend

Implemented controller and service logic for delete operation

Integrated appropriate validations and error handling

Updated documentation (if applicable)

Testing:

Verified delete functionality with valid and invalid inputs

Ensured proper status codes and messages are returned

Confirmed no unintended side effects on other endpoints

[Shrutim1505]

/assign @Monokaix
There were some mistakes in #88
I am closing #88 please consider this one

[Shrutim1505]

[JesseStutler]

I tried to construct a 403 request (no clusterrole), but the error message was incorrect. I checked the error and it was a 502 error.

[Shrutim1505]

i am not getting this error @JesseStutler , but i modified error handling part, can u check it once more??

[Shrutim1505]

@Monokaix @JesseStutler

Screen.Recording.2025-05-21.223457.mp4

[JesseStutler]

Sorry my previous mistake, I think we still need to wrap the error message returned from the kube-apiserver, directly return the whole body is not enough, like this pic:

We can show the message : Can not delete "queue-a", error message: queues.scheduling.volcano.sh "queue-a" is forbidden: User "system:serviceaccount:volcano-system:volcano-dashboard" cannot delete resource "queues" in API group "scheduling.volcano.sh" at the cluster scope，Note that you need to delete those \\ @Shrutim1505

[JesseStutler]

@Shrutim1505 BTW, please clean your commit message:

[de6p]

However, the current approach can be a bit verbose and hard to maintain as the app scales.

[de6p]

same here

[Shrutim1505]

resolved

[Shrutim1505]

@JesseStutler @Monokaix please check it

[JesseStutler]

Still incorrect, where is the error message got from kube-apiserver returned status...?

[Shrutim1505]

check it now @JesseStutler

[JesseStutler]

Now it's OK, please clean your commit message, thanks

[Shrutim1505]

@JesseStutler please check

[JesseStutler]

/lgtm

[Monokaix]

/approve

[volcano-sh-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Monokaix

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [Monokaix]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment