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

Add New Public Playground to Kubernetes Documentation #49978

Open
abhi-bhatra opened this issue Mar 3, 2025 · 1 comment · May be fixed by #49932
Open

Add New Public Playground to Kubernetes Documentation #49978

abhi-bhatra opened this issue Mar 3, 2025 · 1 comment · May be fixed by #49932
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@abhi-bhatra
Copy link

This is a Feature Request

What would you like to be added

I propose adding a new kubernetes playground, KodeKloud Kubernetes Playground, to the Kubernetes Documentation.

It should be listed alongside other public Kubernetes playgrounds to give users more options, especially those looking for a seamless experience without signups and with extended session capabilities.

Why is this needed
While there are existing Kubernetes playgrounds, it offers unique benefits:

  • No signup required – Users can instantly access the playground without creating an account.
  • Extendable sessions – Unlike some alternatives, it allows session extensions, making it more practical for deep learning and testing scenarios.
  • Reliable and stable – Designed to handle high user loads while ensuring performance stability.
  • AI-powered assistant

Comments

This public playground aligns with Kubernetes’ goal of fostering an open and inclusive learning ecosystem. It ensures a frictionless experience, reducing barriers for users trying to learn and experiment with Kubernetes.

@abhi-bhatra abhi-bhatra added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 3, 2025
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Mar 3, 2025
@abhi-bhatra abhi-bhatra linked a pull request Mar 3, 2025 that will close this issue
@sftim
Copy link
Contributor

sftim commented Mar 3, 2025

/triage accepted

I don't see grounds not to add it.

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants