Enhancements to sysbox-deploy-k8s
Open
Nobody has claimed this yet.
Epic
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
The following enhancements to sysbox-deploy-k8s are needed (as of 04/15/22):
Add K8s 1.22 & 1.23 support.- Add support for systemd-managed cgroups.
- Add a way to configure sysbox-deploy-k8s (e.g., via K8s config map).
- Handle scenarios where host uses mutliple kubelet systemd drop-in files (issue #525).
- Handle installation behind HTTPS proxy (issue #522).
- Have the sysbox-deploy-k8s daemonset monitor the kernel version periodically and if it detects changes, reinstall shiftfs with the appropriate version
- Handle scenario where CRI-O is already installed in cluster.
- Handle single-node clusters (i.e,. currently sysbox-deploy-k8s requires >= 2 nodes).
- Create a Helm chart for sysbox-deploy-k8s.
- Add support for more host distros (e.g., Debian, RedHat, Fedora, CentOS-Stream, etc.)
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 at the sysbox-deploy-k8s entry point and review the daemonset behavior, Kubernetes configuration, and the related concerns in issues #525 and #522. This issue contains multiple independent enhancements, so a contributor should first choose one item and define its scope, tests, and completion criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100