Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docs] Include an FAQ on how to bring your own Kubernetes cluster #115

Open
leecalcote opened this issue May 24, 2023 · 12 comments
Open

[Docs] Include an FAQ on how to bring your own Kubernetes cluster #115

leecalcote opened this issue May 24, 2023 · 12 comments
Assignees
Labels
area/docs Improvements or additions to documentation framework/jekyll help wanted Extra attention is needed issue/willfix This issue will be worked on language/markdown

Comments

@leecalcote
Copy link
Member

Current State

Desired State


Contributor Guides and Resources

@leecalcote leecalcote added area/docs Improvements or additions to documentation framework/jekyll language/markdown labels May 24, 2023
@Himral
Copy link

Himral commented Jun 1, 2023

@leecalcote Does this issue involve adding FAQ reagarding setting up kubernetes cluster on your local machine ? If yes then I can add the FAQ on how to bring your own Kubernetes cluster.

@leecalcote
Copy link
Member Author

Thanks for asking, @Himral. No, setting up your own classroom is out of scope for this issue. The goal of this FAQ is to concisely describe how it is that someone who is using the playground can connect their own K8s cluster to the playground environment.

@leecalcote
Copy link
Member Author

You are most welcome to give this a shot. Users will upload their own kubeconfig with context information on how to connect to their publicly accessible kubeapi.

@Himral
Copy link

Himral commented Jun 1, 2023

@leecalcote Thanks a lot I will try my best to give it my best shot . Please assign me this issue .

@Himral
Copy link

Himral commented Jun 2, 2023

Thanks @leecalcote I've started working on it

@stale
Copy link

stale bot commented Jul 17, 2023

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 stale bot added the issue/stale Issue has not had any activity for an extended period of time label Jul 17, 2023
@leecalcote leecalcote added the issue/willfix This issue will be worked on label Jul 17, 2023
@stale stale bot removed the issue/stale Issue has not had any activity for an extended period of time label Jul 17, 2023
@leecalcote leecalcote added the help wanted Extra attention is needed label Jul 31, 2023
@r0nz-29
Copy link

r0nz-29 commented Sep 21, 2023

I can work on this issue.
I am familiar with the codebase and I know where to make the changes, but I don't have any knowledge of setting up kubernetes / anything regarding k8 clusters.

@ayushrakesh
Copy link

@leecalcote Please assign this issue to me.

@ayushrakesh
Copy link

@leecalcote I have recently signup for meshery playground, their from where we can our connect our k8s cluster through config file? I couldn't find.

@komalverma04
Copy link

komalverma04 commented Aug 7, 2024

@leecalcote I have reviewed the code and will add the FAQ on how to bring your own Kubernetes cluster. I will research more on this. Please assign the issue to me so I can start working on it

@komalverma04
Copy link

komalverma04 commented Aug 7, 2024

@leecalcote Apologies to ask it here, but i want to ask that this FAQ has to be added under User FAQs in the Docs right?

image

Or i need to add it here:
image

@leecalcote
Copy link
Member Author

It wouldn't hurt to have a short version of the answer in the FAQs on play.meshery.io. If you search the docs.meshery.io pages, I think you'll find that there's a detailed answer to this question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docs Improvements or additions to documentation framework/jekyll help wanted Extra attention is needed issue/willfix This issue will be worked on language/markdown
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants