pulumi-aws

Sure, but the providers for some of the biggest platforms are maintained by HashiCorp[1] - like the AWS, Azure, GCP, and Kubernetes providers[2], and it appears the Pulumi AWS provider (for example) _does_ use the Terraform AWS provider, even to this day[3]. 1. https://developer.hashicorp.com/terraform/registry/providers... - "official" providers are maintained by HashiCorp 2. https://registry.terraform.io/browse/providers?tier=official - The filtered list of "official" providers maintained by HashiCorp 3. https://github.com/pulumi/pulumi-aws/tree/008c4360bc9fc24303... - Just prove it to myself, I can see the `upstream` git submodule, which embeds pulumi/terraform-provider-aws, which is a fork of hashicorp/terraform-provider-aws, although the repo was not created as a fork in Github, so it is not marked as a "fork" and so I have to compar

>Isn't pulumi aws just terraform under the hood still? It depends. The AWS "Classic" provider uses the terraform provider [1]. The AWS "Native" provider does not, and instead uses the AWS Cloud Control API [2]. [1]: https://github.com/pulumi/pulumi-aws [2]: https://github.com/pulumi/pulumi-aws-native

Everything you describe is also straightforward with Pulumi using `pulumi-gcp` [1], `pulumi-aws` [2] and friends - Kubernetes is one of many libraries. On top of this, you can build actual abstractions thanks to the configuration being written using a general purpose programming language - I don't think there is a first-party set of abstractions for GKE yet but there is for EKS [3]. Many of the most compelling examples deploy entire infrastructure stacks from "empty account" to multi-cloud Kubernetes. Disclaimer: I have worked extensively on Terraform (both core and providers) at and after HC, and have also contributed to Pulumi since it was open sourced. Edited for formatting. [1]: https://github.com/pulumi/pulumi-gcp [2]: https://github.com/pulumi/pulumi-aws [3]: https://github.com/pulumi/pulumi-eks