Skip to main content

Final Thoughts

At this point, a complete software development cycle has been architected with applications running on Kubernetes. All future applications leverage this infrastructure to streamline deployments.

Review of Completed Setup

The following has been configured:

  1. On-premise hardware configured to run Kubernetes
  2. Online services for code hosting, container creation, and log aggregation
  3. Notification services for code changes, pull requests, and Kubernetes actions
  4. ArgoCD automation for the majority of deployment processes

Focus Going Forward

The primary goal is configuration once, then focus exclusively on code development. Deployment and updates should be automated and methodical, requiring minimal manual intervention. As the development cycle progresses, changes to deployments and microservice configurations should be handled by the existing infrastructure.

One advantage of this self-hosted approach is minimal operational costs. Cloud platforms like Azure and AWS offer similar capabilities but may incur substantial bills when handling large data volumes typical in fintech applications.