Skip to content
Permalink
Browse files

change minion-group to node-pool (#14976)

  • Loading branch information...
medmedchiheb authored and k8s-ci-robot committed Jun 19, 2019
1 parent 31fce9b commit efe2d0fd99df85139cc5b5a285a605b12e875088
@@ -212,10 +212,10 @@ You can check node capacities and amounts allocated with the
`kubectl describe nodes` command. For example:

```shell
kubectl describe nodes e2e-test-minion-group-4lw4
kubectl describe nodes e2e-test-node-pool-4lw4
```
```
Name: e2e-test-minion-group-4lw4
Name: e2e-test-node-pool-4lw4
[ ... lines removed for clarity ...]
Capacity:
cpu: 2
@@ -159,7 +159,7 @@ To verify that the profile was applied, you can look for the AppArmor security o
kubectl get events | grep Created
```
```
22s 22s 1 hello-apparmor Pod spec.containers{hello} Normal Created {kubelet e2e-test-stclair-minion-group-31nt} Created container with docker id 269a53b202d3; Security:[seccomp=unconfined apparmor=k8s-apparmor-example-deny-write]
22s 22s 1 hello-apparmor Pod spec.containers{hello} Normal Created {kubelet e2e-test-stclair-node-pool-31nt} Created container with docker id 269a53b202d3; Security:[seccomp=unconfined apparmor=k8s-apparmor-example-deny-write]
```

You can also verify directly that the container's root process is running with the correct profile by checking its proc attr:
@@ -315,8 +315,8 @@ Tolerations: <none>
Events:
FirstSeen LastSeen Count From SubobjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
23s 23s 1 {default-scheduler } Normal Scheduled Successfully assigned hello-apparmor-2 to e2e-test-stclair-minion-group-t1f5
23s 23s 1 {kubelet e2e-test-stclair-minion-group-t1f5} Warning AppArmor Cannot enforce AppArmor: profile "k8s-apparmor-example-allow-write" is not loaded
23s 23s 1 {default-scheduler } Normal Scheduled Successfully assigned hello-apparmor-2 to e2e-test-stclair-node-pool-t1f5
23s 23s 1 {kubelet e2e-test-stclair-node-pool-t1f5} Warning AppArmor Cannot enforce AppArmor: profile "k8s-apparmor-example-allow-write" is not loaded
```

Note the pod status is Failed, with a helpful error message: `Pod Cannot enforce AppArmor: profile

0 comments on commit efe2d0f

Please sign in to comment.
You can’t perform that action at this time.