Add FAQ on connecting your own Kubernetes cluster to Meshery Playground #209
Conversation
Signed-off-by: komalverma04 <[email protected]>
✅ Deploy Preview for meshery-play ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@leecalcote Please give feedbacks on it. |
There was a problem hiding this comment.
Avoid regurgitating the same content from Meshery Docs. This is more to maintain and incomplete (not what fits everyone's situation).
The real question that needs answered here is how the hosted instance of Meshery in the Playground can connect (over the network) to their cluster's API.
P.S. It's just "feedback".
Signed-off-by: komalverma04 <[email protected]>
Signed-off-by: komalverma04 <[email protected]>
|
@leecalcote Please guide me and check the new commits once. |
| To connect your Kubernetes cluster to the Meshery Playground, follow these steps: | ||
| 1. **Generate a Kubeconfig File**: Run the following command to generate a kubeconfig file for your cluster, including the necessary context information for connecting to your publicly accessible Kubernetes API: | ||
| \`\`\`bash | ||
| kubectl config view --minify --flatten > config_minikube.yaml |
There was a problem hiding this comment.
Why are we naming the file "minikube"?
There was a problem hiding this comment.
Why are we naming the file "minikube"?
Yes, I can change it to a more general name. I will add that the file can be named, for example, 'config.yaml,' to reflect the specific cluster context.
There was a problem hiding this comment.
Why are we naming the file "minikube"?
Yes, I can change it to a more general name. I will add that the file can be named, for example, 'config.yaml,' to reflect the specific cluster context.
It will work right?
Notes for Reviewers
This PR fixes #115
Details of Changes:
Signed commits