DevOps

1685 readers

3 users here now

DevOps integrates and automates the work of software development (Dev) and IT operations (Ops) as a means for improving and shortening the systems development life cycle.

Rules:

Posts must be relevant to DevOps
No NSFW content
No hate speech, bigotry, etc
Try to keep discussions on topic
No spam of tools/companies/advertisements
It’s OK to post your own stuff part of the time, but the primary use of the community should not be promotional content.

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

Ategon

RandomDevOpsDude

Opinion on Pulumi vs cdk8s for provisioning Kubernetes? (lemmy.sdf.org)

submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/devops

2 comments fedilink hide all child comments

I can't seem to find any trace of comparison between these specific libraries. I'm planning on using Python for them. I just don't wanna write YAML.

Pulumi seems more prone to the "single vendor is the new proprietary" theory, because they're an actual business and shit, so might do a bait and switch here Terraform-style. But that's the only difference I can spot besides obvious API differences.

Does anyone have an opinion?:)

top 2 comments

sorted by: hot top controversial new old

[–] nous 6 points 7 months ago* (last edited 7 months ago)

Cdk8s is better at generating yaml. Pulumi is more of a terraform replacement that has a good kubernetes provider (the tf one sucks). Though it can generate yaml as well it is really not designed for this.

IMO there is something nice about having all your infra, both inside and outside kube, controlled by one thing. Then you can declare a whole application in one rather then half of it in one tool and half in another.

[–] [email protected] 2 points 7 months ago* (last edited 7 months ago)

I would prefer pulumi as this would allow me to spin up the entire infra and manage k8s from it.

do note, js/ts typically are tier 1 language for aws cdk and pulumi.