Implement userData in Karpenter NodeClass Definitions
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Description:
Implement the userData feature in Karpenter NodeClass definitions to support SOCI-indexes. This will improve image pull times once we have the SOCI-indexed images.
Reference:
See the use of userData in this example:
karpenter_workbench_nodepools.yaml (Line 77)
Next Steps:
Discuss implementation strategies and prioritize this feature in the roadmap.
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
Start by reviewing the referenced karpenter_workbench_nodepools.yaml example at line 77 and inspect the repository's NodeClass definition entry points. The issue does not name implementation files, tests, or a chosen strategy; done would mean agreeing on an implementation and supporting userData for SOCI-indexed images.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100