-
Notifications
You must be signed in to change notification settings - Fork 55
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 operator API #758
Comments
@pohly I think all the listed issues got addressed, Do you still have any in your mind before closing this and calling the operator API is stable? |
Where do we have up- and downgrade tests? What I meant with "test up- and downgrade scenarios", I meant installing one version of the operator, deploying a driver, and then updating resp. downgrading the operator. |
I was mistaken, we have this for the driver but not the operator.
Currently, we cannot support this as our |
It feels too early to define a new API in 0.9.0 and immediately declare it "stable" without any outside feedback - that will prevent all future backwards incompatible changes or at least make them more difficult. With that in mind I think we should move this issue to 1.0. |
Operator downgrade is not supported by the OLM hence we can't test that using OLM. Other than this all others listed in this issue are fixed. |
Currently the operator is considered "alpha" (https://github.com/intel/pmem-csi/blob/devel/README.md#feature-status).
Before we can commit to maintaining a stable API, we need to:
Once we are done, we need to change the channel in Operator Hub from alpha to beta.
The text was updated successfully, but these errors were encountered: