---
title: "Discussion on \"Anatomy of a score.yaml: How Resolution Actually Works\" | Hashnode"
description: "Discussion on \"Anatomy of a score.yaml: How Resolution Actually Works\". A hands-on look at how score-compose and score-k8s turn a workload spec into resolved resource outputs and manifests"
url: "https://hashnode.com/posts/anatomy-of-a-score-yaml-how-resolution-actually-works/6a480df9a0a91cbf571b08e1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Anatomy of a score.yaml: How Resolution Actually Works](https://rootcause.hashnode.dev/anatomy-of-a-score-yaml-how-resolution-actually-works?utm_source=hashnode&utm_medium=feed)

A hands-on look at how score-compose and score-k8s turn a workload spec into resolved resource outputs and manifests

Jul 3 · 8 min read · rootcause.hashnode.dev  
Read the article

-   [#score](https://hashnode.com/tag/score)
-   [#score-spec](https://hashnode.com/tag/score-spec)
-   [#cncf](https://hashnode.com/tag/cncf)
-   [#docker](https://hashnode.com/tag/docker)
-   [#docker-compose](https://hashnode.com/tag/docker-compose)
-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#helm](https://hashnode.com/tag/helm)
-   [#yaml](https://hashnode.com/tag/yaml)
-   [#platform-engineering](https://hashnode.com/tag/platform-engineering)

## Written by

[Prashantkumar Khatri](https://hashnode.com/@prashantkhatri)

@prashantkhatri · Delhi, India

  
[View profile](https://hashnode.com/@prashantkhatri)

Engineer by day. Root cause analyst by habit.

Software and infrastructure engineer. Open source contributor. The person behind root.cause.dev. I build things, break them on purpose, and write about what I find underneath. Two-time GSoC alum. Speaker at OpenSearch Ahmedabad. BazelCon &amp; OpenSearchCon Korea &amp; Japan attendee.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
