You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Organizations will deploy a variety of workloads on their IDP. This includes but is not limited to stateless microservices, APIs, stateful workloads, distributed databases, caches, machine learning training, inference, etc. A category for defining workloads and the supporting projects/technologies to support the required capabilities is needed. Leveraging the CNOE community, it may be possible to drive further standardization of common frameworks required to unlock the capabilities needed to support these workload patterns.
Possible Solution
Adding this category will help to support downstream capabilities that organizations are needing to deploy on their IDP. This includes projects from the Data on EKS ecosystem (data workloads) or other completely unrelated projects such as kubevirt (to support Windows), knative or openwhisk for Function as a Service capability. It may be necessary to create a parallel tech radar to cover the workload categories, gathering input from the CNOE community.
Alternatives Considered
No response
The text was updated successfully, but these errors were encountered:
Have you searched for this feature request?
Problem Statement
Organizations will deploy a variety of workloads on their IDP. This includes but is not limited to stateless microservices, APIs, stateful workloads, distributed databases, caches, machine learning training, inference, etc. A category for defining workloads and the supporting projects/technologies to support the required capabilities is needed. Leveraging the CNOE community, it may be possible to drive further standardization of common frameworks required to unlock the capabilities needed to support these workload patterns.
Possible Solution
Adding this category will help to support downstream capabilities that organizations are needing to deploy on their IDP. This includes projects from the Data on EKS ecosystem (data workloads) or other completely unrelated projects such as kubevirt (to support Windows), knative or openwhisk for Function as a Service capability. It may be necessary to create a parallel tech radar to cover the workload categories, gathering input from the CNOE community.
Alternatives Considered
No response
The text was updated successfully, but these errors were encountered: