Persistent Volume size vs nfs

[zolij]

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug
/sig storage

What happened:
I created a nfs persistent volume with 1 Gi size, then I created persistent volume claim and pod with that claim attached. After that inside the pod I write ~2G data with dd (from /dev/urandom). If I check nfs data from other location, the whole data is there.

What you expected to happen:
Say no more space or terminate pod

How to reproduce it (as minimally and precisely as possible):
kubectl create -f nfs-pv.yaml.txt
kubectl create -f nfs-pvc.yaml.txt
kubectl create -f nfs-pod.txt

Exec shell into pod and overcommit the 1 Gi persistent volume size (it's mounted under /mnt).

Anything else we need to know?:
I tried with the static method and with dynamic proviser too (from external storage repo), it's the same result.

Environment:

• Kubernetes version (use kubectl version): v1.9.6+coreos.0
• Cloud provider or hardware configuration: bare metal (on top of vmware)
• OS (e.g. from /etc/os-release): Container Linux by CoreOS
• Kernel (e.g. uname -a): 4.14.19-coreos
• Install tools: kubespray
• Others: yaml files attached

nfs-pod.yaml.txt
nfs-pv.yaml.txt
nfs-pvc.yaml.txt

[msau42]

Kubernetes does not do capacity enforcement of PVs. It is up to the underlying storage backend to enforce capacity. So you may need to configure your nfs server to use quota.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.