ASM Mesh Id should be - proj-${PROJECTNUMBER}

GoogleCloudPlatform / kubeflow-distribution

Blueprints for Deploying Kubeflow on Google Cloud Platform and Anthos

Apache License 2.0

78 stars 63 forks source link

ASM Mesh Id should be - proj-${PROJECTNUMBER} #117

Closed jlewi closed 3 years ago

jlewi commented 4 years ago

According to the latest ASM instructions https://cloud.google.com/service-mesh/docs/gke-install-asm#validating_the_installation

the mesh id should be "proj-${PROJECTNUMBER}" it looks like this changed in a recent release.

In my case no services showed up in the ASM dashboard until I

Upgraded to ASM 1.4.10 from 1.4.7
Set the mesh id to "proj-${PROJECTNUMBER}"

I'm not sure which or both of these actually fixed my problem.

issue-label-bot[bot] commented 4 years ago

Issue-Label Bot is automatically applying the labels:

Label	Probability
kind/bug	0.65
platform/gcp	0.96

Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: app homepage, dashboard and code for this bot.

Bobgy commented 4 years ago

Let me send a PR for the fix, I tried to use ASM dashboard but couldn't find anything useful there. It would be a waste of ASM if the dashboard doesn't work.

jlewi commented 4 years ago

I also needed to register my cluster with Anthos.