score-k8s is a reference implementation of the Score specification that converts Score files into Kubernetes manifests deployable via kubectl.
The tool solves the problem of translating platform-agnostic workload definitions into Kubernetes-specific configuration. It reads Score files describing workloads and their resource requirements, then generates a single YAML file containing all necessary Kubernetes manifests. The implementation includes a resource provisioning system that converts abstract resource declarations (databases, queues, storage) into concrete Kubernetes objects or configurations. Users initialize a project with default provisioners, add Score files incrementally, and regenerate manifests as needed before deploying with kubectl apply.
The tool is positioned as a reference implementation suitable for demonstration and learning, though it may be used in pre-production or production environments if necessary. It supports the full Score Workload specification and provides extensibility through custom provisioner files. Teams can override default provisioners by placing custom YAML files in the .score-k8s directory, enabling integration with cluster-specific operators or infrastructure patterns. This makes it particularly useful for organizations that have invested in operator-based infrastructure or need to map workload definitions to specialized provisioning logic. The provisioning system works through a first-match policy on resource type, class, and id fields, allowing flexible customization without modifying core tool behavior.
Development activity shows consistent engagement with the specification and implementation details. The project maintains comprehensive documentation of provisioner mechanics through inline examples and reference implementations. The codebase includes built-in default provisioners using template and command-based approaches, providing working examples for users building custom extensions. The tool's design emphasizes extensibility as a core concern, with clear patterns for how teams should integrate their own provisioning logic.
