Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support GPU types #18770

Open
9 tasks
Tracked by #18195
a-thaler opened this issue Jan 16, 2025 · 0 comments
Open
9 tasks
Tracked by #18195

Support GPU types #18770

a-thaler opened this issue Jan 16, 2025 · 0 comments
Assignees

Comments

@a-thaler
Copy link
Contributor

a-thaler commented Jan 16, 2025

Description

As Sebastian and Matthew, we would like to be able to run GPU-intensive workloads on Kyma Runtime so that we can build and deploy machine learning models or data analytics tasks efficiently. That story is part of https://github.tools.sap/kyma/backlog/issues/4633

Allowing GPU workloads would make Kyma Runtime a more versatile and competitive product, attracting users who require heavy computational tasks, including but not limited to data scientists, ML engineers, and computational physicists.

Acceptance Criteria

  1. Users should be able to specify GPU resources in their Kyma Runtime configurations.
  2. The system should schedule the workload on nodes with available GPU resources.
  3. Performance metrics specific to GPU should be available for monitoring.
  4. Must comply with security and resource isolation standards.
  5. Additional infrastructure setup like drivers provisioned via a DaemonSet should be provided in a convenient way

Non-functional Requirements

  1. Scalability: Should support clusters with multiple GPUs.
  2. Security: Isolation of GPU resources to prevent unauthorized access.
  3. Performance: Minimal latency when scheduling and running GPU workloads.

Useful Links

  1. Kubernetes GPU support documentation

Tasks

Preparation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant