kubernetes/pkg/volume
Jan Safranek 0293c6b7f0 Use pod namespace when looking for its GlusterFS endpoints.
I have a pod, which exports a Gluster filesystem in non-default namespace.
When I try to use this FS as a GlusterfsVolumeSource in a 'client' pod
definition, Kubernetes looks for the appropriate endpoint in 'default'
namespace instead of the namespace where the client pod is being defined.
2015-04-21 12:33:59 +02:00
..
aws_ebs Refactored Volume plugins to use InternalVolume instead of API types 2015-04-14 14:25:01 -04:00
empty_dir Refactored Volume plugins to use InternalVolume instead of API types 2015-04-14 14:25:01 -04:00
gce_pd Refactored Volume plugins to use InternalVolume instead of API types 2015-04-14 14:25:01 -04:00
git_repo Refactored Volume plugins to use InternalVolume instead of API types 2015-04-14 14:25:01 -04:00
glusterfs Use pod namespace when looking for its GlusterFS endpoints. 2015-04-21 12:33:59 +02:00
host_path Refactored Volume plugins to use InternalVolume instead of API types 2015-04-14 14:25:01 -04:00
iscsi Refactored Volume plugins to use InternalVolume instead of API types 2015-04-14 14:25:01 -04:00
nfs Refactored Volume plugins to use InternalVolume instead of API types 2015-04-14 14:25:01 -04:00
persistent_claim PVClaim volume plugin 2015-04-14 16:21:29 -04:00
secret Refactored Volume plugins to use InternalVolume instead of API types 2015-04-14 14:25:01 -04:00
doc.go Promote volume plugins, prep for persistent vols 2015-03-20 13:49:40 -07:00
plugins.go Refactored Volume plugins to use InternalVolume instead of API types 2015-04-14 14:25:01 -04:00
plugins_test.go Refactored Volume plugins to use InternalVolume instead of API types 2015-04-14 14:25:01 -04:00
testing.go Refactored Volume plugins to use InternalVolume instead of API types 2015-04-14 14:25:01 -04:00
util.go Added validation to prevent mutating Claim.Spec after binding 2015-04-06 08:46:44 -04:00
volume.go Promote volume plugins, prep for persistent vols 2015-03-20 13:49:40 -07:00