Kubeadm possible uses wrong image for kube-controller-manager

[valumar]

The page related to Storage classes tells us that RBD Plugin realized as an Internal provisioner but it's not true since kubeadm uses image: k8s.gcr.io/kube-controller-manager which doesn't have rbd on board. If you try to create PVC with kubeadm provisioned cluster you get the message:

Events:
  Type     Reason              Age                  From                         Message
  ----     ------              ----                 ----                         -------
  Warning  ProvisioningFailed  2m5s (x20 over 30m)  persistentvolume-controller  Failed to provision volume with StorageClass "rbd-data": failed to create rbd image: executable file not found in $PATH, command output:

But changing the image for Controller Manager to hyperkube solves the issue.

[neolit123]

hello, hyperkube is being deprecated in kubeadm and the support will be removed in the next releases.
this is tracked here:
#1889

in terms of the problems related to RBD, this is not a kubeadm issue. i see you logged kubernetes/kubernetes#85454 but i think an issue about that existed already and it had many comments in kubernetes/kubernetes.

on the side of kubeadm, you have the option of rebuilding all control-plane components (with KCM having RDB) and pushing them to a custom registry. then using kubeadm's imageRepository option you can use your custom build.

this is really something that should be discussed with sig-release and sig-storage. try joining their slack channels and/or meetings.

thanks
/sig release storage
/triage support
/close

[k8s-ci-robot]

@neolit123: Closing this issue.

In response to this:

hello, hyperkube is being deprecated in kubeadm and the support will be removed in the next releases.
this is tracked here:
#1889

in terms of the problems related to RBD, this is not a kubeadm issue. i see you logged kubernetes/kubernetes#85454 but i think an issue about that existed already and it had many comments in kubernetes/kubernetes.

on the side of kubeadm, you have the option of rebuilding all control-plane components (with KCM having RDB) and pushing them to a custom registry. then using kubeadm's imageRepository option you can use your custom build.

this is really something that should be discussed with sig-release and sig-storage. try joining their slack channels and/or meetings.

thanks
/sig release storage
/triage support
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.