Skip to content

Kubernetes Operator for Drasi #312

@amansinghoriginal

Description

@amansinghoriginal

Overview of feature request

Currently, Drasi resources (Sources, Queries, Reactions, etc.) are managed exclusively through the drasi CLI, which interacts with the mgmt_api. While functional, this approach presents challenges for users who want a more Kubernetes-native management experience. Specifically, it hinders the ability to:

  • Manage Drasi resources using kubectl: Users familiar with the Kubernetes ecosystem expect to manage all their application resources, including those from Drasi, through the standard Kubernetes API and kubectl.
  • Integrate with GitOps workflows: Tools like ArgoCD and Flux, which are standard for continuous deployment in the Kubernetes world, rely on declarative resource definitions in Git. The current CLI-based approach does not fit well with these workflows.
  • Unify resource management: A Kubernetes-native approach would allow users to manage Drasi resources alongside their other Kubernetes resources, providing a single, unified view of their applications.

Acceptance criteria

No response

Additional context

No response

Would you like to support us?

  • Yes, I would like to support you

Metadata

Metadata

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions