KubeEdge 1.17.0 --with-mqtt=false Does not work

[zhuyaguang]

KubeEdge 1.17.0 --with-mqtt=false Does not work

[WillardHu]

By default, Cloudcore enable a daemonset eclipse-mosquitto. ref:

kubeedge/manifests/charts/cloudcore/values.yaml

Line 145 in 8badcf5

enable: true

If you want disable it, you can set a helm value mosquitto.enable=false when the cloud init or upgrade, or delete this daemonset.

The flag --with-mqtt of keadm join command for backward compatibility only, we will deprecate this flag in the future.

[Shelley-BaoYue]

cc @WillardHu

[WillardHu]

Since v1.16, the mqtt broker has been controlled by the cloud, you can set a helm value mosquitto.enable=false when the cloud init or upgrade. you can modify the spec of the DaemonSet eclipse-mosquitto in the namespace kubeedge to customize the mqtt broker.

The flag --with-mqtt of keadm join command is used to control whether the old static pod mqtt service needs to be installed, its default value is false now.

[zhuyaguang]

Since v1.16, the mqtt broker has been controlled by the cloud, you can set a helm value mosquitto.enable=false when the cloud init or upgrade. you can modify the spec of the DaemonSet eclipse-mosquitto in the namespace kubeedge to customize the mqtt broker.

The flag --with-mqtt of keadm join command is used to control whether the old static pod mqtt service needs to be installed, its default value is false now.

keadm init --advertise-address=10.11.140.131,10.11.140.86 cloudCore.featureGates.requireAuthorization=true,cloudCore.modules.dynamicController.enable=true --kubeedge-version=v1.17.0
this my init cmd ,mqtt its default value is false now，but edge-eclipse-mosquitto pods still create and CrashLoopBackOff

edgecore logs