k3s/examples/nfs/nfs-server-rc.yaml

apiVersion: v1
kind: ReplicationController
metadata:
  name: nfs-server
spec:
  replicas: 1
  selector:
    role: nfs-server
  template:
    metadata:
      labels:
        role: nfs-server
    spec:
      containers:
      - name: nfs-server
        image: gcr.io/google_containers/volume-nfs
        ports:
          - name: nfs
            containerPort: 2049
        securityContext:
          privileged: true
NFS: Revamp example, add nfs-common to debian saltbase This ensures nfs-common is installed on GCE, and provides a more functional explanation/example. I launched two replication controllers so that there were busybox pods to poke around at the NFS volume, and so that the later wget actually works (the original example would have to work on the node, or need some other access to the container network). After switching to two controllers, it actually makes more sense to use PV claims, and it's probably a configuration that makes more sense for indirection for NFS anyways. 2015-10-20 23:56:55 +00:00			`apiVersion: v1`
			`kind: ReplicationController`
			`metadata:`
			`name: nfs-server`
			`spec:`
			`replicas: 1`
			`selector:`
			`role: nfs-server`
			`template:`
			`metadata:`
			`labels:`
			`role: nfs-server`
			`spec:`
			`containers:`
			`- name: nfs-server`
Fix volumes/test/nfs: Needs to run insecure to allow container connections Since this is a container service port anyways, "insecure" is a bit of a red herring. There's no real security relevance to the incoming port numbers for the NFS server pod. This lets us get rid of the examples/nfs/exporter Docker build (@jsafrane's personal image). 2015-10-23 18:24:59 +00:00			`image: gcr.io/google_containers/volume-nfs`
NFS: Revamp example, add nfs-common to debian saltbase This ensures nfs-common is installed on GCE, and provides a more functional explanation/example. I launched two replication controllers so that there were busybox pods to poke around at the NFS volume, and so that the later wget actually works (the original example would have to work on the node, or need some other access to the container network). After switching to two controllers, it actually makes more sense to use PV claims, and it's probably a configuration that makes more sense for indirection for NFS anyways. 2015-10-20 23:56:55 +00:00			`ports:`
			`- name: nfs`
			`containerPort: 2049`
			`securityContext:`
			`privileged: true`