Move hns package out of hcsshim to its own repo

Open
#2,236 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
networking

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.

Description

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
Dominant language
Go
Stars
694
Forks
304
Avg merge
1d 19h
Merged PRs (30d)
28

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/hcsshim

All issues in microsoft/hcsshim

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.