- ks-installer开启servicemesh，pod都运行起来了
- ks-installer关闭servicemesh
- kubesphere dashboard上服务组件已经没有了service mesh
[root@kube222 ~]# k get po -n istio-system
NAME READY STATUS RESTARTS AGE
istio-ingressgateway-7d7fd96b9-jjkf9 1/1 Running 6 19d
istiod-1-6-10-5c8cc86fb4-kb9kn 1/1 Running 6 19d
jaeger-collector-557f8795cb-t4pvr 1/1 Running 3101 19d
jaeger-es-index-cleaner-1629215700-k6j45 0/1 Completed 0 17d
jaeger-es-index-cleaner-1629302100-vtbfx 0/1 Completed 0 16d
jaeger-es-index-cleaner-1629388500-fcl8s 0/1 Completed 0 15d
jaeger-es-index-cleaner-1630684500-dq5fz 0/1 Error 0 16h
jaeger-es-index-cleaner-1630684500-lrdcn 0/1 Error 0 16h
jaeger-es-index-cleaner-1630684500-t495x 0/1 Error 0 16h
jaeger-es-index-cleaner-1630684500-tl8zw 0/1 Error 0 16h
jaeger-es-index-cleaner-1630684500-vd845 0/1 Error 0 16h
jaeger-es-index-cleaner-1630684500-x2rkg 0/1 Error 0 16h
jaeger-operator-79ddbc974-ft52h 1/1 Running 6 19d
jaeger-query-667b645b7d-8m9st 2/2 Running 3103 16d
kiali-68f784dcf9-4vz2v 1/1 Running 9 19d
kiali-operator-76cd67fb59-7j9sk 1/1 Running 6 19d
但是对应的namespace和pod依然存在，这符合设计吗?还是一个不应该出现的现象?
如果是设计使然我可能会希望能增加一个配置项，能够在关闭service mesh组件时清理对应的namespace和pod.
这对于还原回干净的环境很重要.
例如
servicemesh:
enabled: false
clean: true (false by default)
KS: 3.1.1
