Meshery: [meshery] Meshery was deployed in the cluster but discover the cluster did not work

[Aisuko]

Description

I deployed Meshery into our cluster and wanna detect the cluster-config.yaml but it no working well, the issue that you're describing is #921

Expected Behavior

import the local user's ~/.kube/config and connect to their current context.

[kushthedude]

@Aisuko Is this related for #1257, if yes then we can fix it in #1257 itself?

[Aisuko]

No, there are two different types of issues.

@Aisuko Is this related for #1257, if yes then we can fix it in #1257 itself?

No, these are two different types of issues.

[kushthedude]

Oh thanks for informing!

[Aisuko]

Oh thanks for informing!

You are welcome.

[leecalcote]

@Aisuko is this the issue that you're describing? https://github.com/layer5io/meshery/issues/921

[Aisuko]

@Aisuko is this the issue that you're describing? #921

Yes, I deployed Meshery into our cluster and wanna detect the cluster-config.yaml but it no working well

[leecalcote]

@Aisuko Oh, I see. Ok, #921 describes the a regression issue in which Meshery does not automatically import the local user's ~/.kube/config and connect to their current context. In the scenario in #921, Meshery is deployed out of cluster. // @kumarabd

You may want to include a description in this issue (the boilerplate text is in the description now).

[leecalcote]

@kumarabd, perhaps, you can look at #1272 as you're fixing #921?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.

[Aisuko]

@kushthedude thanks

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Aisuko]

We Can close this issue first and if the same type of issue appears again, we can reopen or create a new one.