-
Notifications
You must be signed in to change notification settings - Fork 715
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
controller-manager flex volume path is hardcoded (fails on coreos) #476
Milestone
Comments
f0
changed the title
controller-manager flex volume path is hardcoded
controller-manager flex volume path is hardcoded (fails on coreos)
Oct 2, 2017
f0
changed the title
controller-manager flex volume path is hardcoded (fails on coreos)
controller-manager flex volume path is hardcoded (fails on coreOS)
Oct 3, 2017
f0
changed the title
controller-manager flex volume path is hardcoded (fails on coreOS)
controller-manager flex volume path is hardcoded (fails on coreos)
Oct 3, 2017
To make this configurable, we'd probably need to:
|
@jamiehannaford please see kubernetes/kubernetes#49840. Once this merged it will allow you to override the default path with something like this:
|
@andrewrynhard will send one more PR for fixing this without user intervention and we'll backport to v1.8 |
k8s-github-robot
pushed a commit
to kubernetes/kubernetes
that referenced
this issue
Nov 15, 2017
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. kubeadm: Conditionally mount flexvolume **What this PR does / why we need it**: See kubernetes/kubeadm#476 **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: Fixes kubernetes/kubeadm#476 ```release-note kubeadm: Fix a bug on some OSes where the kubelet tried to mount a volume path that is non-existent and on a read-only filesystem ``` /cc @luxas
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a BUG REPORT or FEATURE REQUEST?
BUG REPORT
Versions
kubeadm version (use
kubeadm version
):kubeadm version: &version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.0", GitCommit:"6e937839ac04a38cac63e6a7a306c5d035fe7b0a", GitTreeState:"clean", BuildDate:"2017-09-28T22:46:41Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Environment:
VMWare
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1520.2.0
VERSION_ID=1520.2.0
BUILD_ID=2017-09-13-2048
PRETTY_NAME="Container Linux by CoreOS 1520.2.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"
uname -a
):4.13.1-coreos
What happened?
In /etc/kubernetes/manifests/kube-controller-manager.yaml the path to the flex volume plugin dir is hardcoded to /usr/libexec/kubernetes/kubelet-plugins/volume/exec
On CoreOS /usr/libexec is ReadOnly, and the controller manager fails to start
I can chenge the controller manager path with a flag, but this does not change the hardcoded hostpath
What you expected to happen?
i can chage the hardcoded mount path with a config option
How to reproduce it (as minimally and precisely as possible)?
Install coreos + kubeadm init
The text was updated successfully, but these errors were encountered: