-
Notifications
You must be signed in to change notification settings - Fork 53
Open
Description
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 andkubectl
. - 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
brunocascio
Metadata
Metadata
Assignees
Labels
No labels