You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 30, 2021. It is now read-only.
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!
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: