Our great sponsors
-
-
terraform
Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
I've implemented a couple metacontroller operators for cdktf and cdk8s, with a custom cluster autoscaler cloud provider targetting abstract cdktf modules... Don't really like the idea of Crossplane, making a set of CRD's out of every TF provider is just nuts. While managing a set of dependent cdktf workspaces (to unravel multi-stage deployments due to infamous #2430), where CRD's only contain a map of tf variables, seams reasonable.
I've implemented a couple metacontroller operators for cdktf and cdk8s, with a custom cluster autoscaler cloud provider targetting abstract cdktf modules... Don't really like the idea of Crossplane, making a set of CRD's out of every TF provider is just nuts. While managing a set of dependent cdktf workspaces (to unravel multi-stage deployments due to infamous #2430), where CRD's only contain a map of tf variables, seams reasonable.
I find weave's Terraform operator somewhat usable after the CRD refactoring last year. Right now there are three main design issues preventing from adopting it: 1. No direct CDKTF integration - that's a huge deal breaker for me, my team do tend to work with plain YAML settings files which are passed as a single TF object, so being able to pre-process it, and codegen the respective TF code, without relying on complex flatMap constructs (nested for expressions with a flatten), is a must. Same goes for tf deep-merge - it's more convenient to codegen, instead of something like Inviction Labs deepmerge module.