kubernetes-sigs / kubernetes-sigs/image-builder
Need to rationalize the Windows paths across the project
- Dominant language
- Go Template
- Stars
- 550
- Forks
- 508
- Avg merge
- 7d 10h
- Merged PRs (30d)
- 8
Description
@dkoshkin Makes sense. That in combination with using capi's kubeadmconfig as mentioned in https://github.com/kubernetes-sigs/image-builder/issues/709#issuecomment-948373697 make it easy to customize.
If you can update the windows part to `/containerd` to `\\\\containerd` here https://github.com/kubernetes-sigs/image-builder/pull/711#discussion_r729910223 I think we are good to go! @perithompson and I will looking to normalizing the paths across all the Windows parts in a follow up.
_Originally posted by @jsturtevant in https://github.com/kubernetes-sigs/image-builder/issues/711#issuecomment-948776390_
Contributor guide
Research direction
Start by locating the Windows-specific parts of the image-builder project and inventorying the path conventions they use. Compare those paths with the normalization requested in the issue and its linked discussion; done means the Windows paths are consistent across the project.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100