Can a kubernetes member verify that this patch is reasonable to test? If so, please reply with "ok to test" on its own line.

Regular contributors should join the org to skip this step.

While we transition away from the Jenkins GitHub PR Builder plugin, "ok to test" commenters will need to be on the admin list defined in this file.

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

I signed it!

CLAs look good, thanks!

@rootfs @luxas
@kubernetes/sig-storage do we need to add other client tools?

rbd will be another one.

does hyperkube mount a volume in host's namespace or it doesn't care?

ok to test

Does this package exist on all of the arches we support? (@luxas)

'hyperkube' is basically all of the binaries jammed together into one big ball, kinda like the openshift binary. Think of this as 'containerized kubelet' and what needs to be inside the container with the kubelet.

@eparis Yes, debian is the same everywhere.

Right now it's possible to use the --containerized hack in order to run in a container and use mount tools on host, but --containerized is a hack and half-deprecated, so we're not using it anymore.

The current solution (mounting /var/lib/kubelet as a shared volume) works very well, but then all volume deps have to be inside the container. So +1 for this, but only short term.

I'd really like to proceed on the containerized flexvolume proposal that we have, that would be an awesome feature and would help in other cases as well.

@eparis The e2e test is failed. But I have no idea about it. Can you give some suggestion?

@k8s-bot test this please, issue #IGNORE

@fangyuanziti That is completely unrelated to this patch.
We call it a flake where a test should pass but doesn't.

GCE e2e build/test passed for commit fe411b0.

• Test Results
• Build Log
• Test Artifacts
• Internal Jenkins Results

Automatic merge from submit-queue

@eparis is this available in the latest release (1.4.1) or earlier? Thanks!

Per info below, this looks causing trouble on glusterfs servers with higher rev
#43069