zalando / zalando/postgres-operator
Populate contexts in k8s API calls
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
#882 upgraded client-go to the version that uses Context in k8s API calls. The code now uses empty contexts with context.TODO(); in the future we may need to evaluate the need to explicitly manipulate contexts to get access to upcoming k8s features such as distributed tracing.
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 locating the Kubernetes API calls that still use context.TODO() and review the client-go upgrade in #882. Define which request contexts must be propagated and verify that the chosen context behavior supports the intended Kubernetes features, such as distributed tracing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100