Allow adding extraVolumes in ClusterConfiguration for local etcd manifests #1455
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Milestone
What keywords did you search in kubeadm issues before filing this one?
etcd, localEtcd, extraVolumes
Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST
Versions
kubeadm version (use
kubeadm version
):Environment:
kubectl version
): kubeadm version: &version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:35:32Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}uname -a
): 4.19What happened?
I required to mount the hosts' /etc/hosts file to the etcd container / pod as the etcd peers are referenced by their names and those are updated automatically there.
With the etcd manifest file
kubeadm init
creates out of a provided ClusterConfiguration adding extraVolumes to the local etcd section throws a schema validation varning.What you expected to happen?
Looking at the extraVolumes parameter that can be used for all other ControlPlaneComponents (https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm#ControlPlaneComponent)
I expected the same to be possible to do so for etcd as well, but until now this is unfortunately not the case.
How to reproduce it (as minimally and precisely as possible)?
The text was updated successfully, but these errors were encountered: