search

score-spec / spec

The Score Specification provides a developer-centric and platform-agnostic Workload specification to improve developer productivity and experience. It eliminates configuration inconsistencies between environments.
https://score.dev/
Apache License 2.0
7.81k stars 2.2k forks source link

[OTHER] Score to Helm or Score to Kustomize Mapper #83

Open kirkpabk opened 5 months ago

kirkpabk commented 5 months ago

What would you like to share?

So, I'm probably missing the connection somewhere (a gap between my ears), but hopefully your wonderful team could help me a bit here...

So, if our team develops a set of standard score specification templates based on services or capabilities we want to expose. Is there a "mapper" or does that need to be developed? If it needs to be developed, it seems that there would be a standard approach or standard mapper concept. Or is it based simply on existing crd specs? Am I making sense?

Additional information

No response

github-actions[bot] commented 5 months ago

We found the following entries in the FAQ which you may find helpful:

Feel free to close this issue if you found an answer in the FAQ. Otherwise, please give us a little time to review.

This is an automated reply, generated by FAQtory

sujaya-sys commented 5 months ago

Hi @kirkpabk thanks for reaching out! By "mapper" are you referring to "implementation" as illustrated in this graphic? If so, you can find an overview of available implementations here.

For context: The score-compose and score-k8s CLIs are reference implementations we developed as a blueprint / best practice on how to work with the Score spec. A POC for score-helm exists (https://github.com/score-spec/score-helm), however would require some additional reworking to be actually useful (e.g. support for resource provisioning).

If you are interested in developing a score-kustomize or score-helm implementation, let us know, we'd be happy to support you with that! We're still in the process of documenting our standards here i.e. discussing your use case and possible implementation approaches together might be the best way to go for now.

I hope this answers your question 🙂