kubernetes-demo-app VS kubernetes-demo-gitops

The sample app in the **repo** is a basic FastAPI application that I extracted from official docs, but I added a PostgreSQL database to make the whole tutorial a bit more challenging. The application is very simple, it exposes some endpoints to create Users and Items.

If we go to the **GitHub repo** you can find all the manifests that we worked on so far: Deployment, Service, ClusterIssuer, Ingress, and Secret. This is okay at some point… but look at that secret.yaml **file, which is very unlikely to be there, especially when it’s encoded with **base64 **when we know that is so easy to decrypt. Aside from that, it’s so hard to separate environments: **production, staging, development, etc. There can also be lots of inconsistencies, where I can have some manifest locally and apply it, and another version of that manifest exists in the repo, so it’s very hard to reproduce the same environment if we delete everything.

In our **GitOps repo** create a new directory named apps. This would be the directory where we would list all the apps that we want to manage with ArgoCD. Remember, your Git repo according to GitOps can (and should) manage all the projects and infrastructure for your projects or organization. Copy the deployment and the service that we created in previous parts to **apps/fastapi-service/base **without making any modification for now. The repository structure should be like this.