Skip to content
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.

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

Stable v1beta1 APIs for managed databases and caches #863

Closed
6 tasks done
prasek opened this issue Oct 2, 2019 · 0 comments
Closed
6 tasks done

Stable v1beta1 APIs for managed databases and caches #863

prasek opened this issue Oct 2, 2019 · 0 comments
Assignees
Labels
Milestone

Comments

@prasek
Copy link
Member

prasek commented Oct 2, 2019

Beta meta model w/ DB & Redis, so users can deploy to dev/test/prod, align on shape of APIs & best practices, high-def CRDs & controllers, to provide a basis for for code generation in a future milestone.

Part of the 0.4 release

What seems to be the problem?

APIs are currently v1alpha and would like more stable v1beta APIs, so I can take a dependency on Crossplane in my dev/test/prod environments for key managed resources like databases and caches.

What could Crossplane do to help?

Align on shape of APIs & best practices across stacks, define a consistent Crossplane meta model as extensions to Kubernetes, model high-def CRDs and controllers for PostgreSQL, MySQL, and Redis.

What does it look like when we're done?

GCP, AWS and Azure database and Redis resources should be upgraded to v1beta1, which requires them to be refactored to use generic managed reconciler and adopt the patterns in managed resources api patterns one-pager.

How could this be demonstrated?

Possibly a demo showing how Crossplane covers most (if not all) possible configurations that you can have for these resources and consistency between their CR forms.

Related Issues

Nice to have

[#933] v1beta1 quality conformance doc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants