Moving on from Katacoda

[Debanitrkl]

As the katacoda.com has shut down from 15th of June, and our scenario is no longer available we have to look up for other alternatives outside to keep this contributor-katacoda running.
Here are few of the alternatives to look after:

1. https://killercoda.com/, also some discussions regarding this has been mentioned here: Address issues from Katacoda shutdown kubernetes/website#33918 (comment)
2. https://instruqt.com/, this suggestion came as a discussion here: Address issues from Katacoda shutdown kubernetes/website#33918 (comment)

[chris-short]

/label help-wanted

/label contributor-comms

[k8s-ci-robot]

@chris-short: The label(s) `/label help-wanted

, /label contributor-commscannot be applied. These labels are supported:api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor`

Details

In response to this:

/label help-wanted

/label contributor-comms

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[chris-short]

Blasted things

[MadhavJivrajani]

/help

[k8s-ci-robot]

@MadhavJivrajani:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

Details

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[MadhavJivrajani]

/area contributor-comms

[k8s-ci-robot]

@MadhavJivrajani: The label(s) area/contributor-comms cannot be applied, because the repository doesn't have them.

Details

In response to this:

/area contributor-comms

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[MadhavJivrajani]

Interesting
According to the source of truth: https://github.com/kubernetes/test-infra/blob/master/label_sync/labels.yaml, the contributor-comms label is only enabled on a select few repos. We'll need to add an entry for this repo in labels.yaml if we want to use that label here.

[Akshit42-hue]

Hello Folks, I have recently migrated Katacoda(Thanos) to Killercoda(Thanos) if you want any help I am happy to help you out 🙂

[Debanitrkl]

Hi @Akshit42-hue thanks for your interest, could you please try and make a POC for the scenario-setup-linux katacoda in Killercoda so that it could give us an idea on how things work on Killercoda because at the moment we are also considering using GitHub codespace.

[Akshit42-hue]

Yes @Debanitrkl, will be creating a Killercoda scenario and sharing the link with you ASAP

[craiglpeters]

I'd be thrilled to help get this going with GitHub Codespaces - I am a Codespaces product manager. Are the scenarios that were on https://katacoda.com/k8scontributors archived anywhere?

[Debanitrkl]

I'd be thrilled to help get this going with GitHub Codespaces - I am a Codespaces product manager. Are the scenarios that were on https://katacoda.com/k8scontributors archived anywhere?

No the oriely platform isn't available now so it couldn't be archived.

[Akshit42-hue]

Hey @Debanitrkl, here is the link for Killercoda. Sorry for the delay