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

Remove or migrate katacoda integration #494

Closed
3 of 4 tasks
AidanDelaney opened this issue Jun 4, 2022 · 6 comments
Closed
3 of 4 tasks

Remove or migrate katacoda integration #494

AidanDelaney opened this issue Jun 4, 2022 · 6 comments
Labels
team/learning type/enhancement Issue that requests a new feature or improvement.

Comments

@AidanDelaney
Copy link
Member

Summary

Our documentation relies on katacoda.com for interactive exploration of buildpacks. O'Reilly is shutting down katacoda.com. Either remove katacoda integration or migrate to a katacoda alternative.

What questions should this documentation answer?

  • Should we move to a katacoda competitor such as killercoda?
  • How can we replace the feel of interactive tutorials without using a katacoda-style system?

Who is the target audience for this documentation?

  • App Developer
  • Buildpack Author
  • Operator
  • Other:

Additional Information

Hard deadline of June 15th 2022.

@AidanDelaney AidanDelaney added type/enhancement Issue that requests a new feature or improvement. team/learning labels Jun 4, 2022
@sambhav
Copy link
Member

sambhav commented Jun 4, 2022

@AidanDelaney
Copy link
Member Author

O'Reilly have "set up a separate server for Kubernetes.io". We're looking at whether we can also get access to this.

@ramiyengar
Copy link
Contributor

There have been a few mentions of Instruqt (instruqt.com) recently. Worth investigationg.

@ghost
Copy link

ghost commented Oct 25, 2022

Hello, My name is Jesse Meeks, I am a product manager with O'Reilly and I am responsible for Katacoda here. I'm following up on a prior notification concerning the shutdown of Katacoda back on June 15, 2022. I believe my SVP Adam Witwer reached out a few months ago on another issue and mentioned that O'Reilly had set up a dedicated server for Kubernetes.io which would allow the project to continue to use Katacoda. Unfortunately, the dedicated server that was setup for kubernetes.io still relies on an API running on Katacoda.com that is essentially the last remaining service under that domain. While I am mindful of the longstanding partnerships our organizations have enjoyed, I am compelled to share that there are some forces, internal and external, that are increasing the urgency around fully shutting Katacoda.com down.

I noticed that Katacoda is still referenced in your documentation and assume it's still an important part of that resource. Again, mindful of the history between our orgs, I wanted to reach out to try and get a sense for whether there had been any further discussion on moving away from using Katacoda in your docs?

Regards,
Jesse

@AidanDelaney
Copy link
Member Author

@meeksOreilly Does this mean you have no estimated delivery date for a kubernetes.io katacoda instance? We have "parked" our katacoda documentation while we await a kubernetes.io instance, would you advise removing these docs instead of waiting for a katacoda instance?

@AidanDelaney
Copy link
Member Author

Removed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team/learning type/enhancement Issue that requests a new feature or improvement.
Projects
None yet
Development

No branches or pull requests

3 participants