Minecraft Infrastructure as Code Deployment.

Change Summary

This commit introduces a new Minecraft module and its associated configurations, providers, and dependencies. The changes encompass the addition of new Terraform files, configuration updates, and the integration of the Minecraft module into the existing infrastructure.

Technical Details

• New Files:
  • IaC/_envcommon/locks/minecraft.terraform.lock.hcl: A new lock file for Minecraft-related Terraform configurations.
  • IaC/_envcommon/minecraft.hcl: Configuration file for the Minecraft module, including provider inclusions and Terraform source.
  • IaC/modules/minecraft/main.tf: Defines Kubernetes resources and ArgoCD application for Minecraft.
  • IaC/modules/minecraft/variables.tf: Declares variables for the Minecraft module.
  • IaC/modules/minecraft/versions.tf: Specifies required provider versions.
  • IaC/production/homelab/minecraft/.terraform.lock.hcl: Lock file for Minecraft Terraform providers in the production environment.
  • IaC/production/homelab/minecraft/terragrunt.hcl: Terragrunt configuration pointing to the common Minecraft HCL file.
  • IaC/production/homelab/terragrunt.stack.hcl: Stack configuration including units for metallb, storage, traefik, and cert-manager.
• Configuration Changes:
  • Removed kube_provider inclusion from IaC/_envcommon/metrics.hcl.
  • Added kube_provider, aws_provider, and argocd_provider inclusions in IaC/_envcommon/minecraft.hcl.
• Resource Definitions:
  • Defined a kubernetes_namespace and argocd_application in IaC/modules/minecraft/main.tf.
  • Configured ArgoCD application with annotations for image updates and sync policies.
• Provider Versions:
  • Specified versions for kubernetes, argocd, and aws providers in IaC/modules/minecraft/versions.tf.

Key Learnings & Insights

• Modularization: The introduction of the Minecraft module demonstrates a move towards greater modularization of the infrastructure code. This approach enhances reusability and maintainability.
• Automation: The use of ArgoCD for automated deployments and self-healing ensures that the Minecraft server remains up-to-date and operational with minimal manual intervention.
• Configuration Management: The removal and addition of provider inclusions indicate a refined approach to configuration management, ensuring that only necessary providers are loaded for specific modules.

Impact Assessment

• Performance: The introduction of the Minecraft module should not significantly impact overall system performance, as it is isolated within its namespace.
• Security: Proper configuration of the ArgoCD application and Kubernetes resources ensures that the Minecraft server is securely deployed.
• Maintainability: The modular approach and clear separation of concerns make the codebase more maintainable and easier to update.

Developer Notes

• Gotchas: Ensure that the required providers are correctly versioned and available in the Terraform registry to avoid deployment issues.
• Edge Cases: Monitor the ArgoCD application for any image update failures and ensure that the specified update strategy aligns with the team’s deployment practices.
• Future Improvements: Consider adding more granular variables and outputs to the Minecraft module for better configurability and integration with other modules.