Updating Kubernetes to a later version
Open
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 1.2k
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
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?
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 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.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100