clean up the environment (#16430)

This commit is contained in:
diguage
2019-09-26 06:15:05 +08:00
committed by Kubernetes Prow Robot
parent b948ea293d
commit 3a2a59c3e3
4 changed files with 43 additions and 0 deletions
@@ -155,6 +155,14 @@ Here are two of the restrictions that a resource quota imposes on a namespace:
If a Container does not specify its own CPU limit, it is given the default limit, and then
it can be allowed to run in a namespace that is restricted by a quota.
## Clean up
Delete your namespace:
```shell
kubectl delete namespace default-cpu-example
```
{{% /capture %}}
{{% capture whatsnext %}}
@@ -162,6 +162,14 @@ Here are two of the restrictions that a resource quota imposes on a namespace:
If a Container does not specify its own memory limit, it is given the default limit, and then
it can be allowed to run in a namespace that is restricted by a quota.
## Clean up
Delete your namespace:
```shell
kubectl delete namespace default-mem-example
```
{{% /capture %}}
{{% capture whatsnext %}}
@@ -160,6 +160,22 @@ hostPath volume:
Hello from Kubernetes storage
## Clean up
Delete the Pod, the PersistentVolumeClaim and the PersistentVolume:
```shell
kubectl delete pod task-pv-pod
kubectl delete pvc task-pv-claim
kubectl delete pv task-pv-volume
```
Remove the file:
```shell
sudo rm -rf /mnt/data
```
{{% /capture %}}
@@ -353,6 +353,17 @@ label given to all Containers in the Pod as well as the Volumes.
After you specify an MCS label for a Pod, all Pods with the same label can access the Volume. If you need inter-Pod protection, you must assign a unique MCS label to each Pod.
{{< /warning >}}
## Clean up
Delete the Pod:
```shell
kubectl delete pod security-context-demo
kubectl delete pod security-context-demo-2
kubectl delete pod security-context-demo-3
kubectl delete pod security-context-demo-4
```
{{% /capture %}}
{{% capture whatsnext %}}