Cost Allocation
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
- Generic tagging to support cost centers.
- kubecost?
- how can we support passing these tags downstream to workbench/connect so launcher sessions can be tagged as well?
- Could we tag connect content pods based on the connect group that authored?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by mapping how tags could flow from cost centers through Workbench/Connect to launcher sessions and Connect content pods, including the role of Kubecost. Done requires an agreed design for downstream tagging, not just a single code change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100