-
Notifications
You must be signed in to change notification settings - Fork 31
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
Katacoda closed #66
Comments
Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Community Welcome Guide and sure to join the community Slack. |
Oh, no. This is a shame. The good news is that we have planned an alternative: https://play.meshery.io, which is intended to be a hosted version of Meshery in which learners can walk-through the same labs in context of our learning paths. Sounds like its time to ramp up effort on the Cloud Native Playground. |
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. |
Checking in... it has been awhile since we've heard from you on this issue. Are you still working on it? Please let us know and please don't hesitate to contact a MeshMate or any other community member for assistance.
|
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. |
Working on converting those labs to killercoda |
Description
Katacoda closed. What we should do now? In my opinion, those are options:
Expected Behavior
Working scenarios to learn through labs.
Screenshots
The text was updated successfully, but these errors were encountered: