I’ve built a lab project that provisions AKS with Terraform, uses Jenkins or Azure DevOps for CI, and deploys through Argo CD from Git. I also wrote a Python tool that parses resume PDFs and calls external APIs. What would you review first, especially before treating either project as production-ready?
What gaps would you look for in this Azure GitOps setup?
Asked by
8M+Pebble
Answers
The main GitOps questions I’d ask are how changes move between environments and what happens when a deployment fails. Show a clear dev-to-staging-to-production promotion path, integration tests against the deployed app, and a rollback plan. A cluster syncing to Git is a useful foundation, but it doesn’t by itself prove the release process is safe.
Reply to this answer
I’d want to see the boring operational details: where Terraform state lives, how secrets are handled, what permissions the pipeline and GitOps controller have, and how you recover if a cluster or deployment is unhealthy. Also explain which parts are intentionally managed by Terraform versus by Argo CD. Clear ownership boundaries prevent two tools from fighting over the same resources.
Reply to this answer
For the Python side, test ugly inputs, not just a few normal PDFs. Scanned documents, missing fields, unusual layouts, very large files, API timeouts, rate limits, and malformed responses are all worth covering. Be explicit about what happens to resume data, too. Parsing and sending personal information to an external service raises privacy and retention questions beyond whether the script handles errors.
A9~Fexdor:
Good point on privacy. I’d also show how the tool avoids logging the actual document contents when reporting errors.
Reply to this answer
One small architecture question: why use Jenkins alongside Azure DevOps, if both are part of the CI story? There may be a good reason, but a reviewer will want to understand the division of responsibility and how credentials, approvals, and build artifacts move between them. A simpler pipeline can be easier to secure and explain.
8M+Pebble:
I’ve used Azure DevOps too, so I can clarify which parts each tool handles and why I kept both in this version.
Reply to this answer
Add your answer
Answers are reviewed before publication.
8M+Pebble:
That’s helpful. I’ve focused more on syncing the desired state so far, and haven’t documented promotion or rollback yet.