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 operator API #758

Closed
5 tasks done
pohly opened this issue Sep 30, 2020 · 5 comments
Closed
5 tasks done

stable operator API #758

pohly opened this issue Sep 30, 2020 · 5 comments
Assignees
Labels

Comments

@pohly
Copy link
Contributor

pohly commented Sep 30, 2020

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.

@avalluri
Copy link
Contributor

@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?

@pohly
Copy link
Contributor Author

pohly commented Jan 26, 2021

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.

@avalluri
Copy link
Contributor

avalluri commented Jan 28, 2021

Where do we have up- and downgrade tests?

I was mistaken, we have this for the driver but not the operator.

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.

Currently, we cannot support this as our v1beta1 CRD API is not backward compatible. Probably we should target this post 0.9 release, what do you think?

@pohly
Copy link
Contributor Author

pohly commented Jan 28, 2021

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.

@pohly pohly added 1.0 and removed 0.9 labels Mar 10, 2021
@avalluri
Copy link
Contributor

avalluri commented Jun 7, 2021

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.

@avalluri avalluri closed this as completed Jun 7, 2021
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

2 participants