kubernetes upstream: add rook operator #348
Conversation
openshift-ci-robot
added
the
size/XL
leseb
changed the title
leseb
force-pushed
the
rook-upstream
branch
2 times, most recently
from
a391d7f to
c9b18da
Compare
|
PR includes changes to only the [upstream-community-operators] directory. No pipeline will be launched. |
1 similar comment
|
PR includes changes to only the [upstream-community-operators] directory. No pipeline will be launched. |
|
PR includes changes to only the [upstream-community-operators] directory. No pipeline will be launched. |
|
Current Total Score: 32%... |
|
The logs are full of errors, yet the CI is green https://travis-ci.com/operator-framework/community-operators/builds/111611074 🤔 |
|
@leseb The scorecard passes since your operator is running. Our CI also prints out the operator logs as well, which is where you are seeing the errors like this: https://travis-ci.com/operator-framework/community-operators/builds/111611074#L419 |
|
PR includes changes to only the [upstream-community-operators] directory. No pipeline will be launched. |
|
@SamiSousa looks like the issues are solved, I don't understand "CVP/pr-sanity-check"'s error here, am I missing something obvious? Thanks! |
|
Looks good. Can you elaborate in the description a little more what the Operator does? E.g. that it stands up a Ceph cluster with StatefulSets and whether or not it supports upgrades of Ceph as well as advanced lifecycle features as claimed in the capability level ("Full Lifecycle"). |
|
Note: I successfully deployed a cluster using the same Travis job (injected a minimal CR). |
|
PR includes changes to only the [upstream-community-operators] directory. No pipeline will be launched. |
|
PR includes changes to only the [upstream-community-operators] directory. No pipeline will be launched. |
upstream-community-operators/rook/rook.v0.1.0.clusterserviceversion.yaml
Outdated
Show resolved
Hide resolved
leseb
force-pushed
the
rook-upstream
branch
7 times, most recently
from
186ece7 to
ff20180
Compare
Create a new operator under community-operators for Rook the Storage Orchestrator for Kubernetes. This is the Kubernetes upstream version. The initial implementation expects the Ceph cluster to be part of the same namespace as the operator. It also has all Rook's capabilities when it comes to creating, managing and upgrading a cluster. Simply edit the cluster CR to apply any changes to your deployment. Signed-off-by: Sébastien Han <seb@redhat.com>
|
/lgtm |
The rook-ceph operator already existed in the catalog for kubernetes by way of PR operator-framework#348. This adds those same files to the catalog for okd/openshift. There is precedent for both upstream and downstream operators: * Strimzi / AMQ Streams * Infinispan / JBOSS Data Grid
6 participants
Create a new operator under community-operators for Rook the Storage
Orchestrator for Kubernetes. This is the upstream version.
The initial implementation expects the Ceph cluster to be part of the
same namespace as the operator.
It also has all Rook's capabilities when it comes to creating, managing
and upgrading a cluster. Simply edit the cluster CR to apply any changes
to your deployment.
Signed-off-by: Sébastien Han seb@redhat.com