Merge pull request #1 from lexxnsk/task_5

Task 5

Author: lexxnsk

PR_descriptions/task_5.md

@@ -0,0 +1,31 @@
+# Task 4 - Pull Request description
+1. Task: [CLICK ME](https://github.com/rolling-scopes-school/tasks/blob/master/devops/modules/3_ci-configuration/task_5.md)
+2. Screenshots (if needed): Check ./screenshots/ folder
+3. Code: [CLICK ME](https://github.com/lexxnsk/rsschool-devops-course-tasks-application/tree/task_5)
+4. Done 2024-11-09 19:00 / deadline 2024-11-11 00:59
+5. Score: 100 / 100
+
+###### Evaluation Criteria (100 points for covering all criteria)
+
+1. **Helm Chart Creation (40 points)**
+
+   - [+] A Helm chart for the WordPress application is created.
+
+2. **Application Deployment (30 points)**
+
+   - [+] The application is deployed using the Helm chart.
+   - [+] The application is accessible from the internet.
+
+3. **Repository Submission (5 points)**
+
+   - [+] A new repository is created with the WordPress and Helm chart.
+
+4. **Verification (5 points)**
+
+   - [+] The application is verified to be running and accessible.
+
+5. **Additional Tasks (20 points)**
+   - **CI/CD Pipeline (10 points)**
+     - [+] A CI/CD pipeline is set up to automate the deployment of the application.
+   - **Documentation (10 points)**
+     - [+] The application setup and deployment process are documented in a README file.

README.md

@@ -11,9 +11,6 @@ This repository contains all necessary resources and configurations to deploy an
 ├── screenshots/
 ├── .gitignore
 ├── README.md
-├── jenkins-sa.yaml
-├── jenkins-values.yaml
-├── jenkins-volume.yaml
 ```
 
 ### Directory & File Overview
@@ -135,4 +132,40 @@ sudo python3 -m http.server 32000
 
 ---
 ## Task 5 clarifications:
-**XXXXXXXXXXXXXXXXXXXXXXx:**
+**Helm Chart file structure description:**
+WordPress Helm Chart has next file structure:
+```
+tree helm-charts/wordpress
+helm-charts/wordpress
+├── Chart.yaml
+├── templates
+│   ├── deployment-mariadb.yaml
+│   ├── deployment-wordpress.yaml
+│   ├── service-mariadb.yaml
+│   └── service-wordpress.yaml
+├── values.yaml
+├── wordpress-deployment.yaml
+└── wordpress-service.yaml
+```
+
+- **```Chart.yaml```**:  
+  This is the metadata file for the Helm chart. It contains essential information about the chart, such as its name, version, description, and dependencies.
+- **```templates/deployment-mariadb.yaml```**:  
+  This file defines the Kubernetes deployment for the MariaDB database. It specifies how the MariaDB container should be deployed, the replica count, container image, and other configurations specific to the database.
+- **```templates/deployment-wordpress.yaml```**:  
+  This file defines the Kubernetes deployment for the WordPress application. It specifies how the WordPress container should be deployed, including settings such as replicas, container images, and environment variables like the database connection.
+- **```templates/service-mariadb.yaml```**:  
+  This file defines the Kubernetes service for MariaDB, allowing communication between the WordPress application and the database. It exposes MariaDB internally within the cluster to other services, such as WordPress.
+- **```templates/service-wordpress.yaml```**:  
+  This file defines the Kubernetes service for WordPress. It exposes the WordPress application to external traffic and allows access to the application from outside the Kubernetes cluster.
+- **```values.yaml```**:  
+  This file contains the default configuration values for the Helm chart. It provides values for various parameters like image versions, replica counts, database credentials, and other configurable aspects of the WordPress and MariaDB deployments. These values can be overridden during the Helm installation or upgrade process.
+  ## How to Use it manually:
+  **Helm CLI:**
+  ```
+  kubectl create namespace wordpress
+  helm install wordpress helm-charts/wordpress --namespace wordpress
+  ```
+## How to Use it automatically:
+  **GitHub Actions:**  
+   Before committing, check the ```.github/workflows/deploy-wordpress.yaml.yml``` file and update the branch name to trigger the GitHub workflow automatically.​