caigy commented on issue #5612: URL: https://github.com/apache/rocketmq/issues/5612#issuecomment-1337226187
@john1337 I've tried deploying rocketmq-opertor as directions on [OperatorHub](https://operatorhub.io/operator/banzaicloud-kafka-operator), but all works well: ``` # curl -sL https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.22.0/install.sh | bash v0.22.0 customresourcedefinition.apiextensions.k8s.io/catalogsources.operators.coreos.com created customresourcedefinition.apiextensions.k8s.io/clusterserviceversions.operators.coreos.com created customresourcedefinition.apiextensions.k8s.io/installplans.operators.coreos.com created customresourcedefinition.apiextensions.k8s.io/olmconfigs.operators.coreos.com created customresourcedefinition.apiextensions.k8s.io/operatorconditions.operators.coreos.com created customresourcedefinition.apiextensions.k8s.io/operatorgroups.operators.coreos.com created customresourcedefinition.apiextensions.k8s.io/operators.operators.coreos.com created customresourcedefinition.apiextensions.k8s.io/subscriptions.operators.coreos.com created customresourcedefinition.apiextensions.k8s.io/catalogsources.operators.coreos.com condition met customresourcedefinition.apiextensions.k8s.io/clusterserviceversions.operators.coreos.com condition met customresourcedefinition.apiextensions.k8s.io/installplans.operators.coreos.com condition met customresourcedefinition.apiextensions.k8s.io/olmconfigs.operators.coreos.com condition met customresourcedefinition.apiextensions.k8s.io/operatorconditions.operators.coreos.com condition met customresourcedefinition.apiextensions.k8s.io/operatorgroups.operators.coreos.com condition met customresourcedefinition.apiextensions.k8s.io/operators.operators.coreos.com condition met customresourcedefinition.apiextensions.k8s.io/subscriptions.operators.coreos.com condition met namespace/olm created namespace/operators created serviceaccount/olm-operator-serviceaccount created clusterrole.rbac.authorization.k8s.io/system:controller:operator-lifecycle-manager created clusterrolebinding.rbac.authorization.k8s.io/olm-operator-binding-olm created olmconfig.operators.coreos.com/cluster created deployment.apps/olm-operator created deployment.apps/catalog-operator created clusterrole.rbac.authorization.k8s.io/aggregate-olm-edit created clusterrole.rbac.authorization.k8s.io/aggregate-olm-view created operatorgroup.operators.coreos.com/global-operators created operatorgroup.operators.coreos.com/olm-operators created clusterserviceversion.operators.coreos.com/packageserver created catalogsource.operators.coreos.com/operatorhubio-catalog created Waiting for deployment "olm-operator" rollout to finish: 0 of 1 updated replicas are available... deployment "olm-operator" successfully rolled out deployment "catalog-operator" successfully rolled out Package server phase: Installing Package server phase: Succeeded deployment "packageserver" successfully rolled out # # kubectl create -f https://operatorhub.io/install/banzaicloud-kafka-operator.yaml subscription.operators.coreos.com/my-rocketmq-operator created # kubectl get csv -n operators NAME DISPLAY VERSION REPLACES PHASE rocketmq-operator.0.3.0 RocketMQ Operator 0.3.0 rocketmq-operator.0.2.1 Succeeded ``` You should check if `Subscription` was installed successfully in your environment. **For deploying RocketMQ 5.0:** - If you just want to update versions of name servers or brokers to 5.x, just update the docker image. - If you want to deploy new modules in 5.x, you can use `apache/rocketmq-operator:0.4.0-snapshot`, which has not been published to OperatorHub yet: - Clustering with new DLedger Controller: Pls deploy [Controller](https://github.com/apache/rocketmq-operator/blob/master/example/rocketmq_v1alpha1_console_cr.yaml) first and specify `clusterMode` as `CONTROLLER` for `Broker` cr. - Proxy mode: It's still under development, you can refer this [pr](https://github.com/apache/rocketmq-operator/pull/134) for details. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
