Feature Request: Crossplane provider for HyperDX/ClickStack resources

[ankitcharolia]

Summary

We would like a Crossplane provider for managing HyperDX (ClickStack) observability resources as Kubernetes Custom Resources, enabling Kubernetes-native GitOps workflows and continuous reconciliation.

Motivation

Teams using Crossplane currently have no way to manage HyperDX resources through their existing Kubernetes-native infrastructure workflows. The ClickStack API now exposes the CRUD operations needed for provider integration, and the official ClickHouse Terraform provider already supports ClickStack resources. A Crossplane provider would avoid requiring teams to mix Terraform and Crossplane and would provide Kubernetes RBAC, GitOps, drift detection, and reconciliation for HyperDX configuration.

Desired scope

At minimum, the provider should expose saved searches, dashboards, alerts, webhooks, sources or connections, teams, and roles. Resources should support team scoping, secret-based authentication, observe-existing behavior where practical, status and conditions, and normal Crossplane create, update, delete, and drift-reconciliation behavior.

Implementation options

An Upjet-generated provider based on the existing ClickHouse Terraform provider could be a pragmatic starting point. A native provider using the HyperDX External API v2 would also work. The provider should use the team-scoped API behavior and must not expose write-only webhook headers or query parameters in resource status.

Context

The HyperDX saved-search and webhook CRUD API was added in #2586. The official Terraform provider and saved-search resource documentation are available at:

https://github.com/ClickHouse/terraform-provider-clickhouse
Crossplane Upjet: https://github.com/crossplane/upjet

Would the HyperDX team consider maintaining or supporting a Crossplane provider, or accepting a community contribution for this integration?

[wrn14897]

Thanks for the well-researched request!
We won't be maintaining a first-party Crossplane provider, but the pieces you need already exist:

• External API v2 has full team-scoped CRUD for alerts, dashboards, saved searches, webhooks, sources, and connections (feat: Adding remaining API v2 endpoints - saved searches & webhooks #2586 was merged specifically to unblock provider integrations). This is our supported integration contract.
• The official ClickHouse Terraform provider already covers every resource you listed, including team scoping and the write-only webhook header handling.

So for Crossplane you can use crossplane-contrib/provider-terraform against the TF provider today, or generate an Upjet provider from it — which, as you say, is mostly mechanical since the TF provider already encodes the API semantics.
We'd happily support a community-maintained Upjet provider — ideally hosted under crossplane-contrib or your own org, since providers tend to be best maintained by people running them in production. We're glad to answer API v2 questions and fix anything in the API that blocks reconciliation. Just open an issue if you hit something.

[ankitcharolia]

@wrn14897 we created crossplane provider from terraform provider and it works perfectly fine. Kindly have a look: https://github.com/justtrackio/provider-clickhouse