Phase 3 : Kubernetes-Manifest Deployment

Directory: kubernetes-manifest

This repository contains the Kubernetes manifest files used to deploy the frontend and backend of a Bank App to an EKS cluster, managed declaratively via Argo CD.

Project Purpose

To define and manage application workloads using Kubernetes YAML files for seamless deployment via GitOps, using Argo CD and GitHub Actions.

Prerequisites

EKS cluster already provisioned via Terraform
kubectl and aws CLI configured locally
Argo CD installed on the cluster
GitHub repository containing your Kubernetes manifests

ConfigMap, Secrets, and deployment YAMLs available in the repo

Files and Their Purpose

File Name	Description
`bankend-ingress.yaml`	Defines ingress rules using NGINX Ingress Controller for the backend.
`bankendapi.yaml`	Kubernetes Deployment for the backend API (Spring Boot container).
`backend-service.yaml`	ClusterIP service for internal communication with backend pods.
`configmap.yaml`	Stores environment configuration such as `DB_HOST`, `DB_PORT`, etc.
`secrets.yaml`	Contains sensitive credentials like `DB_USERNAME` and `DB_PASSWORD`, base64-encoded.
`frontend-service.yaml`	ClusterIP service to expose frontend pods internally.
`frontend.yaml`	Kubernetes Deployment for the frontend app (React/Vue/etc.).

All manifests are deployed into the default namespace.