|
15 | 15 | | Operating ReplicaSets | ReplicaSet | [Exercise](replicaset_02.md) | [Solution](solutions/replicaset_02_solution.md)
|
16 | 16 | | ReplicaSets Selectors | ReplicaSet | [Exercise](replicaset_03.md) | [Solution](solutions/replicaset_03_solution.md)
|
17 | 17 |
|
18 |
| -### Kubernetes Self Assesment |
| 18 | +### Kubernetes Self Assessment |
19 | 19 |
|
20 | 20 | <details>
|
21 | 21 | <summary>What is Kubernetes? Why organizations are using it?</summary><br><b>
|
@@ -58,7 +58,7 @@ metadata, kind and apiVersion
|
58 | 58 | </b></details>
|
59 | 59 |
|
60 | 60 | <details>
|
61 |
| -<summary>What actions or operations you consider as best practices when it comes to Kuberentes?</summary><br><b> |
| 61 | +<summary>What actions or operations you consider as best practices when it comes to Kubernetes?</summary><br><b> |
62 | 62 |
|
63 | 63 | - Always make sure Kubernetes YAML files are valid. Applying automated checks and pipelines is recommended.
|
64 | 64 | - Always specify requests and limits to prevent situation where containers are using the entire cluster memory which may lead to OOM issue
|
@@ -749,7 +749,7 @@ It specifies what do with an incoming request to the Kubernetes cluster that isn
|
749 | 749 | <details>
|
750 | 750 | <summary>How to configure a default backend?</summary><br><b>
|
751 | 751 |
|
752 |
| -Create Service resource that specifies the name of the default backend as reflected in `kubectl desrcibe ingress ...` and the port under the ports section. |
| 752 | +Create Service resource that specifies the name of the default backend as reflected in `kubectl describe ingress ...` and the port under the ports section. |
753 | 753 | </b></details>
|
754 | 754 |
|
755 | 755 | <details>
|
@@ -967,7 +967,7 @@ In simpler words, Network Policies specify how pods are allowed/disallowed to co
|
967 | 967 | <summary>What are some use cases for using Network Policies?</summary><br><b>
|
968 | 968 |
|
969 | 969 | - Security: You want to prevent from everyone to communicate with a certain pod for security reasons
|
970 |
| - - Controling network traffic: You would like to deny network flow between two specific nodes |
| 970 | + - Controlling network traffic: You would like to deny network flow between two specific nodes |
971 | 971 | </b></details>
|
972 | 972 |
|
973 | 973 | <details>
|
@@ -1054,7 +1054,7 @@ When using the default namespace alone, it becomes hard over time to get an over
|
1054 | 1054 |
|
1055 | 1055 | Namespaces can also be useful for managing Blue/Green environments where each namespace can include a different version of an app and also share resources that are in other namespaces (namespaces like logging, monitoring, etc.).
|
1056 | 1056 |
|
1057 |
| -Another use case for namespaces is one cluster, multiple teams. When multiple teams use the same cluster, they might end up stepping on each others toes. For example if they end up creating an app with the same name it means one of the teams overriden the app of the other team because there can't be too apps in Kubernetes with the same name (in the same namespace). |
| 1057 | +Another use case for namespaces is one cluster, multiple teams. When multiple teams use the same cluster, they might end up stepping on each others toes. For example if they end up creating an app with the same name it means one of the teams overridden the app of the other team because there can't be too apps in Kubernetes with the same name (in the same namespace). |
1058 | 1058 | </b></details>
|
1059 | 1059 |
|
1060 | 1060 | <details>
|
@@ -1729,7 +1729,7 @@ Scale the number of pods automatically on observed CPU utilization.
|
1729 | 1729 | </b></details>
|
1730 | 1730 |
|
1731 | 1731 | <details>
|
1732 |
| -<summary>Describe how you one proceeds to run a containerised web app in K8s, which should be reachable from a public URL.</summary><br><b> |
| 1732 | +<summary>Describe how you one proceeds to run a containerized web app in K8s, which should be reachable from a public URL.</summary><br><b> |
1733 | 1733 | </b></details>
|
1734 | 1734 |
|
1735 | 1735 | <details>
|
|
0 commit comments