Windows node scheduling
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
### What problem are you trying to solve?
As of today, the proxy does not run on windows nodes. Unfortunately, injection will still happen and the pod will just not run.
### How should the problem be solved?
- Update `inject` to be aware of windows pods and skip injection on them.
- Update `check` to warn if there are windows nodes in the cluster.
### Open questions
- Are there any ways we can surface that a pod is failing because of the proxy in a clear way?
- Should we recommend taints in the documentation?
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 tracing the inject and check entry points to understand how pods and cluster nodes are evaluated. Update the behavior so Windows pods are skipped and Windows nodes produce a warning, then verify that injection is avoided and the warning is surfaced; resolve whether failure messaging and taint documentation are in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100