chore: add liveness & readiness probes to the container

[fmuyassarov]

Add HTTP probes against /healthz on port 8080.
Verified locally:

kubectl debug -it dracpu-kg258  -n kube-system --image=curlimages/curl --target=dracpu -- curl -v http://localhost:8080/healthz

Targeting container "dracpu". If you don't see processes from this container it may be because the container runtime doesn't support this feature.
--profile=legacy is deprecated and will be removed in the future. It is recommended to explicitly specify a profile, for example "--profile=general".
Defaulting debug container name to debugger-97wnz.
* Host localhost:8080 was resolved.
* IPv6: ::1
* IPv4: 127.0.0.1
*   Trying [::1]:8080...
* Established connection to localhost (::1 port 8080) from ::1 port 36230
* using HTTP/1.x
> GET /healthz HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/8.18.0
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 200 OK
< Date: Fri, 13 Mar 2026 03:16:51 GMT
< Content-Length: 0
<
* Connection #0 to host localhost:8080 left intact

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: fmuyassarov
Once this PR has been reviewed and has the lgtm label, please assign pravk03 for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[fmuyassarov]

/cc @AutuSnow

[AutuSnow]

Since we haven't set up a startupProbe, I'm wondering if there might be scenarios where the discovery of CPU resources on nodes takes a long time, resulting in an insufficient tolerance window for initialDelaySeconds? But unexpectedly, it seems to be working fine

[AutuSnow]

Thank you for your revision
/lgtm

[fmuyassarov]

Since we haven't set up a startupProbe, I'm wondering if there might be scenarios where the discovery of CPU resources on nodes takes a long time, resulting in an insufficient tolerance window for initialDelaySeconds? But unexpectedly, it seems to be working fine

Yes, I think we'll need to revisit the timeouts once we have some/more feedback. For now, though, it seems sufficient.

[fmuyassarov]

/cc @ffromani