-
Notifications
You must be signed in to change notification settings - Fork 408
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
Enable consumption and configuration of specific hyperscaler resources #18195
Comments
|
cKMS team is evaluating the usage of Kyma. |
SAP for Me would like to use m6g and m6in machine types |
+1 for GPUs |
Thanks Valentin for reporting it. I think it's worth mentioning the context and let me do it on behalf of you for simplicity 😄 : it's to make it possible for Core AI to run on Kyma (subject to future discussions and agreements) |
+1 team for GPU (ICN Munich) |
Enable more private connectivity (e.g. via firewall), requested by not less than 3 teams (e.g. S/4HANA ABAP Machines) |
Enable assured workload GCP module (relevant for KSA), requested by BTP email service |
A customer is looking for very high IOPS storage. |
At present, customers are able to use resources for which they are not charged such as
We should somehow make the customers aware that they might have to pay for this in the future, so it should not come as a surprise for them. @NHingerl , could you please help? IMHO, putting this info out might not need to wait until this epic is done. |
Description
Provide a way for end users to consume and be charged for a pre-defined set of hyperscaler resources:
Context
Problem
Currently, Kyma is a layer on top of Kubernetes and as such provides a very limited set of infrastructure configuration options at provisioning time.
However, customers looking to adopt Kyma that already use existing hyperscaler offerings already take advantage of specialized resources as part of their workloads (for example faster storage, GPU nodes, network optimized nodes, etc). This prevents those users from on-boarding on Kyma without having to re-engineer their workloads.
Benefits
For customers:
For us:
Potential problems
Acceptance criteria
Tasks
The text was updated successfully, but these errors were encountered: