How to quickly deploy RocketMQ 5.0 on k8s? · Issue #5612 · apache/rocketmq

link管理

链接快照平台

输入网页链接，自动生成快照
标签化管理网页链接

相关文章推荐

失望的鸡蛋面 · 網路購買國外貨物案例說明-財政部稅務入口網· 9 月前 ·

文质彬彬的斑马 · 隨身印相機 - SELPHY CP1500 ...· 10 月前 ·

酒量小的春卷 · 林永健去世引热议？这谣言太离谱了，看完原委哭笑不得· 1 年前 ·

有情有义的蟠桃 · 这些地方为何有不少百年温州村？古代温州移民脚 ...· 1 年前 ·

任性的香瓜 · esc命令集+cpcl命令集+tspl命令集 ...· 1 年前 ·

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

@john1337 Could you provide more failure information when using rocketmq-operator? Actually rocketmq-operator does not depend on helm.
错误信息如下：
error: unable to recognize " https://operatorhub.io/install/stable/rocketmq-operator.yaml ": no matches for kind "Subscription" in version "operators.coreos.com/v1alpha1"

@john1337 I've tried deploying rocketmq-opertor as directions on OperatorHub , 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 first and specify clusterMode as CONTROLLER for Broker cr.
Proxy mode: It's still under development, you can refer this pr for details.