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
Currently, score-k8s converts to the workload into either a Deployment or a Statefulset + a Service object. This behavior is hard coded.
However, some folks want to convert to ArgoCDRollouts, VMs, or other CRDs or inject specific translation logic that is not common to all score consumers.
We want to support these kinds of workloads in Score too through a "workload templates" concept.
This must be a template of some kind that can validate and convert the input workload. Validation is needed because while Score spec provides some base validations according to the Score spec, the particular CRD may enforce stricter requirements - for example, only 1 container allowed. Or, no ordered containers, or no memory limits higher than X.
While Go templates are possible here, it may be better to go for Kustomize, KCL, Rego, or something that understands the context better 🤔
The text was updated successfully, but these errors were encountered:
Currently, score-k8s converts to the workload into either a Deployment or a Statefulset + a Service object. This behavior is hard coded.
However, some folks want to convert to ArgoCDRollouts, VMs, or other CRDs or inject specific translation logic that is not common to all score consumers.
We want to support these kinds of workloads in Score too through a "workload templates" concept.
This must be a template of some kind that can validate and convert the input workload. Validation is needed because while Score spec provides some base validations according to the Score spec, the particular CRD may enforce stricter requirements - for example, only 1 container allowed. Or, no ordered containers, or no memory limits higher than X.
While Go templates are possible here, it may be better to go for Kustomize, KCL, Rego, or something that understands the context better 🤔
The text was updated successfully, but these errors were encountered: