Deploy kube-proxy as DaemonSet
Open
area/networking
lifecycle/frozen
- Dominant language
- Go
- Stars
- 16.7k
- Forks
- 4.7k
- Avg merge
- 17h 21m
- Merged PRs (30d)
- 68
Description
**1. Describe IN DETAIL the feature/behavior/change you would like to see.**
Kubernetes best practices state that kube-proxy is best deployed as a DaemonSet. As kops - as of now - places the kube-proxy manifest into /etc/kubernetes/manifests as a file, this is against this best practice.
**2. Feel free to provide a design supporting your feature request.**
We could deploy kube-proxy using the addon mechanisms
Contributor guide
Research direction
Start by tracing how kOps currently places the kube-proxy manifest in /etc/kubernetes/manifests, then read the addon mechanisms mentioned in the issue. Done means kube-proxy is deployed as a DaemonSet through the addon mechanism rather than as a static manifest.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100