Skip to content

Commit

Permalink
Merge branch 'inno-2023-masters:main' into main
Browse files Browse the repository at this point in the history
  • Loading branch information
kolayne authored May 3, 2024
2 parents e3ce449 + cf38477 commit 3b2f234
Show file tree
Hide file tree
Showing 3 changed files with 10 additions and 14 deletions.
6 changes: 0 additions & 6 deletions lab11.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,12 +28,6 @@ In this lab, you will learn how to manage sensitive data, such as passwords, tok
- Retrieve the list of pods using the command `kubectl get po`. Use the name of the pod as proof of your success within the report.
- Verify your secret inside the pod, for example: `kubectl exec demo-5f898f5f4c-2gpnd -- printenv | grep MY_PASS`. Share this output in `11.md`.

4. Create a Pull Request:
- Generate a PR to the main branch of the forked repository.

5. Create a Pull Request in Your Own Repository:
- Create a PR in your repository from the lab11 branch to the main one. This will facilitate the grading process.

## Task 2: Vault Secret Management System

**4 Points:**
Expand Down
4 changes: 0 additions & 4 deletions lab12.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,10 +20,6 @@ In this task, you'll enhance your application to persist data and explore Config
- Verify that the enhancements work as expected, you must see the updated number in the `visits` file on the host machine.
- Update the `README.md` for your application.

2. Create Pull Requests:
- Submit a PR to merge your changes into the main branch of the forked repository.
- Create a PR from the `lab12` branch to the main branch in your own repository.

## Task 2: ConfigMap Implementation

**4 Points:**
Expand Down
14 changes: 10 additions & 4 deletions lab14.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,19 +8,25 @@ In this lab, you will explore Kubernetes cluster monitoring using Prometheus wit

**6 Points:**

1. Read about `Kube Prometheus Stack`:
1. This lab was tested on a specific version of components:
- Minikube v1.33.0
- Minikube kubectl v1.28.3
- kube-prometheus-stack-57.2.0 v0.72.0
- the minikube start command - `minikube start --driver=docker --container-runtime=containerd`

2. Read about `Kube Prometheus Stack`:
- [Helm chart with installation guide](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack)
- [Explanation of components](https://github.com/prometheus-operator/kube-prometheus#kubeprometheus)

2. Describe Components:
3. Describe Components:
- Create `14.md` and detail the components of the Kube Prometheus Stack, explaining their roles and functions. Avoid direct copy-pasting; provide a personal understanding.

3. Install Helm Charts:
4. Install Helm Charts:
- Install the Kube Prometheus Stack to your Kubernetes cluster.
- Install your app's Helm chart.
- Provide the output of the `kubectl get po,sts,svc,pvc,cm` command in the report and explain each part.

4. Utilize Grafana Dashboards:
5. Utilize Grafana Dashboards:
- Access Grafana using `minikube service monitoring-grafana`.
- Explore existing dashboards to find information about your cluster:
1. Check CPU and Memory consumption of your StatefulSet.
Expand Down

0 comments on commit 3b2f234

Please sign in to comment.