-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Implement scripts to release che-operator #13780
Comments
There could Che CI or CRW CCI be used for this propose. |
@dmytro-ndp It seems we would plan to use Eclipse CI for the Che operator, as discussed in these PR comments: eclipse-che/che-operator#45 (comment) |
This sounds like good and important work, but I have two questions:
|
That's the idea yes. Maybe not a full automation of it (in CI I mean), but at least having the related files and scripts available in the repo, and a clear process documented about how to update / test / release the Operator OLM files.
I don't see any: this issue is mainly about adding new files and scripts that were not in the repository previously, and formalizing / scripting / documenting processes that were purely manual and informal until now. |
So what should I do to add it into the Endgame plan ? |
I confirm that this will be part of the endgame but the scope is only limited to what is needed to script a release of the che-operator, something that was done manually until now. |
Implementation of issue eclipse-che/che#13780 * complete cluster role * update operator.yaml * Add OLM files for openshift in beta-5 state * Add RC 2 release CSV * Reordered beta 5 csv in alphabetic order * Add first bits of OLM files management * lowercase `RC` and remove readiness probe * pre-release (with `rc-2.0`) and nightly channels * Add the kubernetes version of the OLM package * Adding operator sources * `OperatorSource`s should be in distinct namespaces * Change proposed by @l0rd * scripts to update nightly CSVs * script to release OLM files * Add the script to push OLM files as Quay apps * Add script to prepare `community-operators` PRs * script to release the operator Go code * Rename `*-test-*` to `*-preview-*` and rename the `pre-releases` channel to `stable` * `9.9.9` as semver-compliant prefix for nightlies Signed-off-by: David Festal <dfestal@redhat.com>
@davidfestal I believe we can close this one and have a CI for che-operator as part of the separate issue #13951 |
@ibuziuk sure. |
…just update deploy/cluster_role.yaml with 2 new verbs update and patch Change-Id: I1a51e11be9259e29f4eb4ccdcdcd950601e82c3b Signed-off-by: nickboldt <nboldt@redhat.com>
… deploy/cluster_role.yaml with 2 new verbs update and patch Change-Id: I1a51e11be9259e29f4eb4ccdcdcd950601e82c3b Signed-off-by: nickboldt <nboldt@redhat.com>
Setup a reproducible way to test / release the operator on OperatorHub
Current state of Testing / Release process
Until now releasing the che operator is a totally manual thing. Though it was still somewhat easy for the operator code itself (build, tag and deploy docker image), it isn't easy at all, and very error-prone to manually build OLM-related yaml files and submit them in PR to the
community-operators
repository for each release we want to deploy to the OperatorHub, especially due to the fact that we cannot test the whole package before deploying it to the marketplace.Detailed description
This issue defines what should be done to correctly and continuously test the Che Operator (including the OLM files and OperatorHub-based installation), and release it to the OperatorHub without risks.
This would be great if a decent minimal implementation of this purpose could be setup before Che 7 GA, to ensure a successful release to the marketplace.
The main purpose can be decomposed into several subtasks:
che-operator
repository for both the Openshift and the K8S cases,Quay.io
namespace and application, so that can be installed and tested independently from the official OperatorHub marketplace,community-operators
Repository) from the source CSV maintained our ownche-operator
repository,Quay.io
application repositoriescommunity-operators
repository, based on a given release of the OLM files hosted in our ownche-operator
repositoryThe text was updated successfully, but these errors were encountered: