Skip to content

Commit

Permalink
clean up the environment (#16430)
Browse files Browse the repository at this point in the history
  • Loading branch information
diguage authored and k8s-ci-robot committed Sep 25, 2019
1 parent b948ea2 commit 3a2a59c
Show file tree
Hide file tree
Showing 4 changed files with 43 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -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 %}}
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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 %}}
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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 %}}


Expand Down
11 changes: 11 additions & 0 deletions content/en/docs/tasks/configure-pod-container/security-context.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 %}}
Expand Down

0 comments on commit 3a2a59c

Please sign in to comment.