Hello everyone, I’m a totally Pulumi newbie :sligh...
# getting-startedr
rapid-belgium-27383
08/01/2024, 9:01 AMHello everyone, I’m a totally Pulumi newbie 🙂
I’d like to use Pulumi in my CICD pipeline. Each time I push a Pulumi yaml files in my GitHub config repo I’d like the Kubernetes cluster defined in this yaml to be created. Is there a reference setup for that purpose (folder structure, file names, …) ? I was thinking about having a single project and have different stack in that one (each stack having the name of the cluster to be created). Doing so, how can I have a main Pulumi.yaml file describing the k8s cluster’s base configuration and several file with each cluster’s specific details (name, ...)
Thanks a lot for your help 👍
f
future-hairdresser-70637
08/01/2024, 1:55 PM👋 Have you seen/read about the Kubernetes Operator? That might fit well for your use case
r
rapid-belgium-27383
08/01/2024, 1:59 PMHi @future-hairdresser-70637 from what I understand this operator is used to deployed things in kube cluster. For my use case I’d like to define my CD so that each time a Pulumi yaml (in which is defined my cluster) is pushed to the git config repo then the cluster is actually created automatically. I was wondering if there is best practices for that use case
f
future-hairdresser-70637
08/01/2024, 2:15 PMAhhh, you're thinking of a cluster per stack, right, okay
future-hairdresser-70637
08/01/2024, 2:36 PMI can't find an exact example for your use case - in terms of "best practices", how about the k8s playbook? If you decide to follow that pay special attention to Stack 3 "Kubernetes Cluster": for this stack your Pulumi program would parse/ingest the config as you mention and loop through each cluster's definition, specifying them to be created via whichever provider/resources are needed
r
rapid-belgium-27383
08/01/2024, 4:46 PMThanks a lot, I will check this carefully
9 Views