k3s/test/images/volumes-tester/nfs
Tim Hockin 3586986416 Switch to k8s.gcr.io vanity domain
This is the 2nd attempt.  The previous was reverted while we figured out
the regional mirrors (oops).

New plan: k8s.gcr.io is a read-only facade that auto-detects your source
region (us, eu, or asia for now) and pulls from the closest.  To publish
an image, push k8s-staging.gcr.io and it will be synced to the regionals
automatically (similar to today).  For now the staging is an alias to
gcr.io/google_containers (the legacy URL).

When we move off of google-owned projects (working on it), then we just
do a one-time sync, and change the google-internal config, and nobody
outside should notice.

We can, in parallel, change the auto-sync into a manual sync - send a PR
to "promote" something from staging, and a bot activates it.  Nice and
visible, easy to keep track of.
2018-02-07 21:14:19 -08:00
..
Dockerfile Remove all MAINTAINER statements in the codebase as they aren't very useful and now deprecated 2016-12-17 20:34:10 +02:00
Makefile Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00
README.md Add test for supplemental gid annotation to pv e2e test 2016-08-09 18:23:06 -04:00
index.html
run_nfs.sh Enable NFS volume test 2016-11-03 12:48:09 -07:00

README.md

NFS server container for testing

This container exports '/' directory with an index.html inside. NFSv4 only.

Accepts a -G option for specifying a group id to give exported directories. Clients in the specified group will have full rwx permissions, others none.

Inspired by https://github.com/cpuguy83/docker-nfs-server.

Used by test/e2e/* to test NFSVolumeSource. Not for production use!

Analytics