kubernetes-kubeadm depends on kubernetes package
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 692
- PR merge metrics
- No merged PRs in 30d
Description
Following official kubernetes upgrade guide with kubeadm: https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-12/
kubeadm package needs to be installed first and then after performing control plane upgrade with "kubeadm upgrade apply" the kubelet (which is included in kubernetes package in PhotonOS) needs to be updated.
However running tdnf upgrade kubernetes-kubeadm-1.12.7-2.ph2 on PhotonOS2 also upgrades it's dependency kubernetes package:
tdnf upgrade kubernetes-kubeadm-1.12.7
Upgrading:
kubernetes x86_64 1.12.7-1.ph2 photon-updates 675.29M 708090036
kubernetes-kubeadm x86_64 1.12.7-1.ph2 photon-updates 30.65M 32138441
This interdependency breaks kubeadm upgrade process and makes kubernetes cluster upgrade v1.11 -> v1.12 on PhotonOS impossible.
Expected behaviour: kubernetes-kubeadm and kubernetes packages (v > 1.11) can be upgraded independently.
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 with the Kubernetes 1.11 to 1.12 upgrade guide and reproduce the reported tdnf upgrade kubernetes-kubeadm-1.12.7-2.ph2 behavior on PhotonOS 2. Inspect the package dependency metadata for kubernetes-kubeadm and kubernetes; done means upgrading kubeadm does not force an upgrade of the kubernetes package for versions above 1.11.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100