Support Crossplane as an IaCM Provider (Starting with Chaos Engineering)
C
Crimson Warbler
Many enterprise teams are standardizing on Crossplane to manage infrastructure declaratively from Kubernetes. Today, Harness does not natively support Crossplane as an IaCM provider, which creates friction for customers trying to onboard Harness modules, especially Chaos Engineering, at scale.
While Crossplane providers can theoretically be generated from existing Terraform providers, the current process is complex, undocumented, and unstable in practice. This makes adoption risky and slows down production rollouts.
Proposed Improvements:
- Add official Crossplane support within Harness IaCM
- Provide a supported and documented way to generate Crossplane providers from Harness Terraform providers
- Deliver a stable Crossplane provider for Chaos Engineering as an initial use case
- Clearly document required fields, lifecycle behavior, and limitations
Why This Matters:
- Unblocks large-scale, Kubernetes-native onboarding workflows
- Reduces dependency on custom tooling and deep Go expertise
- Improves Chaos Engineering adoption for customers operating in Crossplane-first environments
- Strengthens Harness’ IaCM story beyond Terraform-only workflows
Log In