Repos-que-me-gustan/devops-exercises
1
0
Fork 0
Code Pull Requests Activity

Update

Browse Source
This commit is contained in:
abregman 2021-09-27 00:34:59 +03:00
parent e977f77933
commit 4cde87dc2c
2 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -7278,6 +7278,12 @@ The pod is automatically assigned with the default service account (in the names
`kubectl get serviceaccounts` `kubectl get serviceaccounts`
</b></details> </b></details>
<details>
<summary>Explain "Security Context"</summary><br><b>
[kubernetes.io](https://kubernetes.io/docs/tasks/configure-pod-container/security-context): "A security context defines privilege and access control settings for a Pod or Container."
</b></details>
#### Kubernetes - Patterns #### Kubernetes - Patterns
<details> <details>

2
exercises/kubernetes/solutions/replicaset_03_solution.md
View File

@ -51,7 +51,7 @@ kubectl label pod <POD_NAME> type-
5. List the Pods running. Are there more Pods running after removing the label? Why? 5. List the Pods running. Are there more Pods running after removing the label? Why?
``` ```
Yes, there is an additional Pod running because once the label, used as a matching selector, was removed, the Pod became independant meaning, it's not controlled by the ReplicaSet anymore and the ReplicaSet was missing replicas based on its definition so, it created a new Pod. Yes, there is an additional Pod running because once the label (used as a matching selector) was removed, the Pod became independant meaning, it's not controlled by the ReplicaSet anymore and the ReplicaSet was missing replicas based on its definition so, it created a new Pod.
``` ```
6. Verify the ReplicaSet indeed created a new Pod 6. Verify the ReplicaSet indeed created a new Pod