Move hns package out of hcsshim to its own repo
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 694
- Forks
- 304
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 28
Description
- HNS package is quite independent and it can be moved out of hcsshim to its own repo.
- In k8s/k8s repo hcsshim is being imported only for using hns constructs (in 3 files only https://github.com/search?q=repo%3Akubernetes%2Fkubernetes%20%22hcsshim.%22&type=code) :
hcsshim tag used in k8s/k8s is more that 2-3 years old and is blocking certain updates from happening like https://github.com/kubernetes/kubernetes/pull/126361#issuecomment-2264232155
- Also, HNS can stop depending on hcsshim release process if it is moved out to its own repo
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 auditing the HNS package in hcsshim and the three Kubernetes files that use hcsshim HNS constructs. Define the repository split and migration path with both projects; done means HNS has its own repository and Kubernetes no longer depends on the hcsshim release process for these constructs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100