Managing Kubernetes CronJobs with Postman via ArgoCD and Kustomize

Creating a service to push changes to Git sounds like a solid plan. It not only allows you to manage the changes but also gives you an audit trail since you can log who made each request. Sure, setting up Git apps and credentials can be tricky, but it’s similar to what you did for ArgoCD, so it should be manageable.

I’m a bit puzzled why they’d want to manage Kubernetes jobs through Postman. I think it would be better to clarify the actual goals with management. There might be more effective solutions that can meet their needs without relying on Postman.

Another option could be setting up Tekton pipelines. You could have Postman trigger an event listener that sends a JSON payload, and then your pipeline checks out the repo, makes the necessary changes to the YAMLs, and pushes them back to the repo. It could streamline your process pretty well!

Have you thought about using ArgoWorkflows? It might be a better fit since it allows you to manage jobs and parameters without needing to commit changes directly. You could also consider parameterized templates for more flexibility.

Before diving into building APIs, have you considered using a Kubernetes dashboard like the K8s dashboard or Headlamp? It could simplify CronJob management for the team. However, you'd need to ensure proper authentication and permissions are set up. But given that you're fully committed to Argo, be cautious about potential conflicts with direct edits versus Argo's management.

It’s crucial to maintain a single source of truth with these systems. If management is okay with using Postman, why not get them accustomed to using the Git UI? If that’s not feasible, then building an API to help them make the necessary changes could work. Just be wary of directly modifying fields in Argo; it might lead to complications.