Dev, Ops & FinOps

All that remains is to explore the issues specific to Dev and Ops, and to integrate FinOps into the pipeline.

First of all, Dev need a Dev environment to share their common work. Gitlab comes into play and allows with its Merge Requests to monitor and group the work of the Dev team. Merge requests will therefore serve as a Dev environment.

The Ops team will need to deploy the infrastructure in which the application will be installed. The most efficient solution is to follow the GitOps concept: the infrastructure will be deployed in Infrastructure as Code (IaC) via Terraform, and maintained within the Gitlab repository. Ops will also be entitled to the Dev environment, since they too will need to share and centralize their work.

Finally, FinOps will be integrated at the Merge requests level, in order to allow Dev and Ops teams to preview the new costs incurred when modifying the infrastructure capacity; before pushing it to review and then to production. The FinOps tool used will be Infracost, which is perfectly implemented in this way.

Another FinOps tool named Kubecost will also be implemented, but rather to monitor and optimize the costs of the Kubernetes cluster once the application is deployed.

All topics have been covered, it is now time to complete the pipeline.