[jayyyyqwq]

What this PR does / why we need it:

OptimizerClient.get_job_events says in its docstring that it raises RuntimeError if getting the events fails. In the Kubernetes backend only the timeout is handled, so any other error from list_namespaced_event (for example a 403 when the user cannot list events) comes out as the raw Kubernetes error.

The other methods in this backend already do it, for example list_jobs has except Exception and raises RuntimeError. I added the same for get_job_events.

I added a test that makes list_namespaced_event fail. On main (ee22b33) the timeout case passes and the other case fails with Exception: events are forbidden. With the change both pass. The existing "timeout" test for events goes through get_job first, so it never reached the events call.

I noticed TrainerClient.get_job_events has the same docstring and the same gap in the Trainer Kubernetes backend. I left it out to keep this small. Should I send that as a separate PR, or add it here?

Which issue(s) this PR fixes (optional, in Fixes #<issue number>, #<issue number>, ... format, will close the issue(s) when PR gets merged):

None.

Checklist:

• Docs included if any changes are user facing

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign andreyvelich for approval. For more information see the Kubernetes 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

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[github-actions]

🎉 Welcome to the Kubeflow SDK! 🎉

Thanks for opening your first PR! We're happy to have you as part of our community 🚀

Here's what happens next:

• If you haven't already, please check out our Contributing Guide for repo-specific guidelines and the Kubeflow Contributor Guide for general community standards
• Our team will review your PR soon! cc @kubeflow/kubeflow-sdk-team

Join the community:

• Slack: Join our #kubeflow-ml-experience and #kubeflow-trainer Slack channels
• Meetings: Attend the Kubeflow SDK and ML Experience bi-weekly meetings

Feel free to ask questions in the comments if you need any help or clarification!
Thanks again for contributing to Kubeflow! 🙏