New Pulumi Open Source Projects for Kubernetes

think about huge CloudFormation yaml files with repetitive logic copy pasted, instead, you can build private subnet with couple of code and assign instances using OOP methods.

    subnet = aws.vpc.Create()
    subnet.Add(webServerInstance)
    subnet.Add(appInstance)
    appToDB = iam.create('name')
    appToDB.add(appInstance)
    appToDB.add(rds1)

and so on

Here’s a recent example I came across — data is set as a JSON string in an annotation, and the user wanted to use a nested value from that annotation in a later function call. Normally, this type of thing would involve some glue code in a scripting language, but it’s fairly easy to implement as a callback in Pulumi. As someone who had to do a bunch of that prior to Pulumi, I think it’s a great improvement to keep all that logic in the same place. (disclaimer: I work on Kubernetes at Pulumi)

Here’s the annotation:

  cloud.google.com/neg-status: '{"network_endpoint_groups":{"443":"k8s1-5487ae62-istio-system-istio-ingressgateway-443-811432aa"},"zones":["us-east1-d"]}'

And here’s the Pulumi code snippet in TypeScript required to parse it.

  // This defines a callback that runs once the Service is provisioned.
  const neg_status = svc.metadata.annotations.apply(x => {
      const status = x['cloud.google.com/neg-status'];
      const obj = JSON.parse(status);
      return obj["network_endpoint_groups"]["443"]
  });
  // Using the computed value from the callback to dynamically retrieve another value.
  const neg = gcp.compute.getNetworkEndpointGroup({
      name: neg_status,
      zone: "us-east1-d"
  });

I was able to dynamically issue a key file from GCP IAM with stackdriver access (a JSON file), base64 decode it and pass part of it into an env variable of an AWS Fargate task--- all with Pulumi and all at deploy time. I don't know how I might have done that otherwise, but I can't imagine the alternative would have been as elegant by any other means.

Terraform has been making great strides, but at this point Pulumi really leads in policy, modularity, extensibility via Dynamic providers etc.

I think what they are doing with a K8s provisioner is really interesting. I know that the Kubernetes ecosystem has a dizzying amount of ways to build yaml (and json) config, but Pulumi can reach many other places, all with great type hints.