New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Offer guidelines for GitOps friendly API designs #75

Open

emmanuelbernard opened this issue Sep 6, 2022 · 0 comments

Assignees

Contributor

emmanuelbernard commented Sep 6, 2022 •

edited

Loading

Present GitOps options and approach ideas from one service to help mature

When a concept is represented as a resource
- What about bidirectional synchronization from a “admin” protocol (Kafka admin) and the custom resource
- SR - schema creation ok
- Disallow schema creation if CR is enabled?
- What about de facto lead market
- CRD vs Git as source, where does it change
- [alec] tradeoffs in terms of ecosystems/reuse:
  - use CR only? full power of kube/gitops ecosystems
  - allow per-service API? bring in existing service ecosystem

emmanuelbernard assigned EricWittmann

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment