Skip to content
This repository has been archived by the owner on Jul 30, 2021. It is now read-only.

Standard Resource Definition #515

Closed
pierreozoux opened this issue Jul 12, 2019 · 1 comment
Closed

Standard Resource Definition #515

pierreozoux opened this issue Jul 12, 2019 · 1 comment

Comments

@pierreozoux
Copy link

I'm trying to standardize the way we describe operator dependencies (like PostreSQL to start with), and make this part of upstream, in alpha for the 1.16 version.

This is basically the problem I'm trying to solve:
As a WordPress operator developer, I want to specify MySQL dependency in a standard way, the same as when I use Ingress or PVC

Currently there are various oeprator provider for MySQL, and the CRD are not compatible between them, I aim at fixing that upstream.

I'd love your feedback on this. And I think this is one issue that would be nice to tackle as the operator framework.
What is the biggest challenge you see in this initiative?

If you think this is valuable for the community as a whole like I do, please comment on the draft here.

Thanks for your valuable time!

@github-actions
Copy link
Contributor

github-actions bot commented Jun 1, 2021

This issue is stale because it has been open for 30 days with no activity.

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

No branches or pull requests

1 participant