Updating Kubernetes to a later version
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go, kubernetes
- Domain
- backend, infrastructure
Research direction
Start in go/pkg/controller/controller.go, especially the UpdateStatus call at line 129, and run the controller package tests to reproduce the Kubernetes API mismatch. Review the existing Kubernetes dependencies and update the stack to a compatible later version; done means the controller package builds and its tests pass.
Written by the indexing model from the issue text.
Description
In Linux distribution, we are mostly packaging unbundled libraries. Vpnkit presents a challenge because it uses a very old (2017) K8S stack, which causes compatibility issues like:
# github.com/moby/vpnkit/go/pkg/controller [github.com/moby/vpnkit/go/pkg/controller.test]
./controller.go:129:68: not enough arguments in call to c.services.Services(service.Namespace).UpdateStatus
have (*"k8s.io/api/core/v1".Service)
want (context.Context, *"k8s.io/api/core/v1".Service, "k8s.io/apimachinery/pkg/apis/meta/v1".UpdateOptions)
FAIL github.com/moby/vpnkit/go/pkg/controller [build failed]
Would it be possible to update vpnkit to a more recent K8S stack?
- Dominant language
- OCaml
- Stars
- 1.2k
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from moby/vpnkit
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Compilation error due to "Unbound module Ethernet__Ethernet_wire"May be free again A pull request for this issue was closed without being merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 10/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Yeachan-Heo/gajae-code#6611 · 1 comment ·
Maintainers usually reply within 1 day
-
llm translation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
area: storage maintenance priority: low status: accepted
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
amatya-aditya/obsidian-rss-dashboard#1019 ·
Maintainers usually reply within 1 day