linode / linode/k8s-node-decorator
Support Getting Linode Metadata from APIv4
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Some regions doesn't have metadata services support yet. We may want to implement logic that gets Linode metadata from APIv4 (the REST API) with an API token for labeling the node.
Contributor guide
No contributing guide indexed for this repository
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 locating the existing metadata-reading and Kubernetes node-labeling entry points in the repository. Review how an APIv4 REST request would use an API token when regional metadata services are unavailable. Done means Linode metadata can be retrieved through APIv4 and used to label the node in unsupported regions, with the existing metadata path preserved where available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend-api-design, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100