Team is new to K8s. Wondering a couple things from the pros here.
Would Pulumi be a good start for a team writing Go to learn K8 without doing the normal yaml approach, or is there any opinion on starting with the yaml and maturing to Pulumi later?
I've considered one approach with
https://devspace.sh/ which seems to make this a nice smooth process, but was hoping to actually drive the config via code rather than piles of yaml if it made sense.
Context:
• All the folks in my team are software engineering background with no/little infrastructure/terraform/k8 experience.
• I'm basically transferring services that would be normally in docker compose to k8.
• I want to focus on local development to minikube/kind or such first and then start pushing to our shared AKS cluster.
If I start with Pulumi considering the group I'm with, does that make sense or adds more complexity than it's worth over just k8 yaml?
