meshery: Unable to install `mesheryctl` v0.6.5, `meshery-perf` and `meshery-cillium` are crashing

Current Behavior

Current release v0.6.5 failed to complete installation, both meshery-perf and meshery-cillium are crashing. From the previous release, meshery-perf and meshery-cpx are supposed to be deprecated, however, installing the Helm charts, still pulled in meshery-perf even though it is disabled.

For Cillium, here is an existing issue open #71 at the meshery-cillium error provided still persist in my cluster.

I have a possible fix but I’m currently testing it at this time, I would like to submit a PR and I am open to anyone willing to help with me.

Expected Behavior

Installation is supposed to be successful.

Screenshots/Logs

kubectl get pods -n meshery
NAME                                    READY   STATUS             RESTARTS        AGE
meshery-meshery-cpx-5b49b48fdf-7h4g5    1/1     Running            0               5m45s
meshery-istio-65f67fb978-rtfgr          1/1     Running            0               5m45s
meshery-linkerd-cc65f9d78-fspnl         1/1     Running            0               5m44s
meshery-consul-8484fbcc96-kxkjx         1/1     Running            0               5m45s
meshery-operator-7bb97dfdb-j796z        2/2     Running            0               5m44s
meshery-osm-6fbc9769cd-lcpjs            1/1     Running            0               5m43s
meshery-697fd8446-4zgbz                 1/1     Running            0               5m43s
meshery-app-mesh-67c78f557d-xgww5       1/1     Running            0               5m45s
meshery-kuma-785765997-xfzcc            1/1     Running            0               5m44s
meshery-nsm-7788546ff6-wbzgz            1/1     Running            0               5m44s
meshery-traefik-mesh-c5548d4f6-7wk4t    1/1     Running            0               5m43s
meshery-nginx-sm-5c5569dbf4-dx9kg       1/1     Running            0               5m44s
meshery-broker-0                        2/2     Running            0               5m39s
meshery-meshsync-7b498c5686-dwstd       1/1     Running            2 (5m24s ago)   5m38s
meshery-meshery-perf-5bbd4f86df-89pp8   0/1     CrashLoopBackOff   5 (2m39s ago)   5m43s
meshery-cilium-7757c94c4d-46225         0/1     CrashLoopBackOff   5 (2m11s ago)   5m45s

Environment

Host OS: Linux and Ubuntu 22 WSL2
Platform: Kubernetes k3d
Meshery Server Version: stable-v
Meshery Client Version: stable-v

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation
- Meshery documentation site and source
🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 16 (15 by maintainers)

Commits related to this issue

Fix #6178 Setting the `values.yaml` to disable `meshery-perf` and `meshery-cpx` from being deployed via Helm deployment within the `meshery` directory. Setting the definitions via `Chart.yaml` from ... — committed to nebula-aac/meshery by acald-creator 2 years ago
Fix #6178 Setting the `values.yaml` to disable `meshery-perf` and `meshery-cpx` from being deployed via Helm deployment within the `meshery` directory. Setting the definitions via `Chart.yaml` from ... — committed to nebula-aac/meshery by acald-creator 2 years ago
Fix #6178 Setting the `values.yaml` to disable `meshery-perf` and `meshery-cpx` from being deployed via Helm deployment within the `meshery` directory. Setting the definitions via `Chart.yaml` from ... — committed to nebula-aac/meshery by acald-creator 2 years ago
Merge pull request #6182 from acald-creator/test-helm [Helm] Preventing meshery-perf and meshery-cpx from installing by default || Fix #6178 — committed to meshery/meshery by leecalcote 2 years ago

Most upvoted comments

Hmm… I need to talk with @CyrineG about this, will get back to you soon!

alphaX86 on Sep 6, 2022

@alphaX86 Hi there, the names being appended with meshery- that’s when I did a local installation trying to test the changes.

However, using the curl -L https://meshery.io/install | PLATFORM=kubernetes bash - resulted in this output.

kubectl get pods -n meshery
NAME                                   READY   STATUS             RESTARTS      AGE
meshery-nsm-7788546ff6-hrhvp           1/1     Running            0             13m
meshery-consul-8484fbcc96-wkbxh        1/1     Running            0             13m
meshery-cpx-7c6885bcfc-h92ld           1/1     Running            0             13m
meshery-operator-7bb97dfdb-f9jp5       2/2     Running            0             13m
meshery-cilium-7757c94c4d-xxgtz        1/1     Running            0             13m
meshery-osm-6fbc9769cd-sq78k           1/1     Running            0             13m
meshery-app-mesh-67c78f557d-rm7jq      1/1     Running            0             13m
meshery-nginx-sm-5c5569dbf4-f5xsj      1/1     Running            0             13m
meshery-linkerd-cc65f9d78-thdxx        1/1     Running            0             13m
meshery-istio-65f67fb978-gh4sg         1/1     Running            0             13m
meshery-broker-0                       2/2     Running            0             12m
meshery-traefik-mesh-c5548d4f6-5g7bt   1/1     Running            0             13m
meshery-kuma-785765997-52wrm           1/1     Running            0             13m
meshery-meshsync-689bb4f698-pdhcl      1/1     Running            1 (11m ago)   12m
meshery-5d8d749fb4-x7zrm               1/1     Running            0             13m
meshery-perf-794bb4f4c7-dccz5          0/1     CrashLoopBackOff   7 (28s ago)   13m

But meshery-perf and meshery-cpx are still being pulled in, even though they are deprecated? Are they meant not to be pulled in the Helm deployment?

acald-creator on Sep 6, 2022