Is your feature request related to a problem? Please describe.
We use Crossplane to manage infrastructure declaratively and provide self-service capabilities to developers. Currently, we use Jikkou to manage Kafka topics, users, and ACLs via CRDs. However, we can’t compose these resources with other infrastructure (e.g., secrets, databases, policies) in a Crossplane-native way. This limits our ability to build complete, platform-level abstractions for Kafka.
Describe the solution you'd like
A Crossplane provider (provider-jikkou) that can reconcile Kafka resources (e.g., KafkaTopic, KafkaPrincipal, KafkaAcl) using Jikkou under the hood. This would enable us to:
• Use Kafka resources in Crossplane Compositions and Claims
• Automate topic/user provisioning via Crossplane APIs
• Build fully declarative, GitOps-compatible workflows for Kafka alongside other cloud infrastructure
Describe alternatives you've considered
We considered continuing with standalone Jikkou CRDs and triggering reconciliation via CI/CD or controllers. However, this doesn’t integrate with Crossplane’s claim/composition model and creates fragmented infrastructure workflows.
Additional context
This would allow folks to provision a Kafka topic by submitting a KafkaTopicClaim and have it wired up with ACLs, secrets, and other components automatically - all within Kubernetes. It would also allow broader adoption of Jikkou among Crossplane users.
Is your feature request related to a problem? Please describe.
We use Crossplane to manage infrastructure declaratively and provide self-service capabilities to developers. Currently, we use Jikkou to manage Kafka topics, users, and ACLs via CRDs. However, we can’t compose these resources with other infrastructure (e.g., secrets, databases, policies) in a Crossplane-native way. This limits our ability to build complete, platform-level abstractions for Kafka.
Describe the solution you'd like
A Crossplane provider (provider-jikkou) that can reconcile Kafka resources (e.g., KafkaTopic, KafkaPrincipal, KafkaAcl) using Jikkou under the hood. This would enable us to:
• Use Kafka resources in Crossplane Compositions and Claims
• Automate topic/user provisioning via Crossplane APIs
• Build fully declarative, GitOps-compatible workflows for Kafka alongside other cloud infrastructure
Describe alternatives you've considered
We considered continuing with standalone Jikkou CRDs and triggering reconciliation via CI/CD or controllers. However, this doesn’t integrate with Crossplane’s claim/composition model and creates fragmented infrastructure workflows.
Additional context
This would allow folks to provision a Kafka topic by submitting a KafkaTopicClaim and have it wired up with ACLs, secrets, and other components automatically - all within Kubernetes. It would also allow broader adoption of Jikkou among Crossplane users.