ManageIQ / ManageIQ/kubeclient
Surface `Warning` header
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 426
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
Since 1.19, apiserver may set `Warning:` header on responses. https://kubernetes.io/blog/2020/09/03/warnings/
How may we expose it to callers?
NOT an exception, this is for stuff like deprecated APIs that however _should still work_.
The common use case is probably to log them, but should be customizable.
So, add a param to `Client.new()` specifying a callback / logger object?
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 at Client.new and trace how HTTP responses and headers are handled. Define how callers can receive Kubernetes Warning headers through a callback or logger without raising an exception, and verify that existing requests continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, ruby
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100