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 command for a "Getting Started" workshop using eduk8s as addon #8482

Closed
blues-man opened this issue Jun 15, 2020 · 8 comments
Closed

Add command for a "Getting Started" workshop using eduk8s as addon #8482

blues-man opened this issue Jun 15, 2020 · 8 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@blues-man
Copy link
Contributor

blues-man commented Jun 15, 2020

/kind feature

Hello,

I was thinking that it would be nice having a katacoda-like tutorial for beginners for local Kubernetes with Minikube, available from cli command and implemented as addon.

One good candidate for this could be creating an addon for eduk8s, a workshop framework installable via Operator and providing CR for creating interactive content, containing the Kubernetes Foundamentals 1h workshop (or creating a new one).

The flow would be similar to minikube dashboard command which activates dashboad addon, in this case it would be:

$ minikube getstarted

or

$ minikube tutorial

activating eduk8s addon or getstarted addon (containing eduk8s + workshop), opening the browser pointing to eduk8s ingress.

eduk8s

This would help people that'd love to learn Kubernetes doing it from their workstation with Minikube, having so a local persistent env were to execute exercises, and taking benefit from storage and ingress components already available, needed by the workshop framework in this case.

How does that sound?

@k8s-ci-robot
Copy link
Contributor

@blues-man: The label(s) kind/ cannot be applied, because the repository doesn't have them

In response to this:

/kind feature

Hello,

I was thinking that it would be nice having a katacoda-like tutorial for beginners for local Kubernetes with Minikube, available from cli command and implemented as addon.

One good candidate for this could be creating an addon for eduk8s, a workshop framework installable via Operator and providing CR for creating interactive content, containing the Kubernetes Foundamentals 1h workshop (or creating a new one).

The flow would be similar to minikube dashboard command which activates dashboad addon, in this case it would be:
minikube getstarted or minikube tutorial
activating eduk8s addon or getstarted addon (containing eduk8s + workshop)

This would help people that'd love to learn Kubernetes doing it from their workstation with Minikube, having so a local persistent env were to execute exercises, and taking benefit from storage and ingress components already available, needed by the workshop framework in this case.

How does that sound?

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.

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 15, 2020
@blues-man blues-man changed the title Add "getstarted" command for a "Getting Started" workshop using eduk8s as addon Add command for a "Getting Started" workshop using eduk8s as addon Jun 15, 2020
@priyawadhwa priyawadhwa added the triage/discuss Items for discussion label Jun 15, 2020
@priyawadhwa
Copy link

Hey @blues-man thanks for opening this issue, I think this could be really cool. Would you be interested in first implementing this as an addon? You can find docs around implementing addons here and some recent example PRs adding other addons here: #8129

@blues-man
Copy link
Contributor Author

blues-man commented Jun 18, 2020

Hi @priyawadhwa, thanks for the feedback!

I'm discussing also with eduk8s folks for possibly collaborating on this, we would need to check couples of things like everything is fine their side, all software license involved are OK and workshops tuning for minikube.

I would be happy to contribute to the addon, I understood the mechanism from doc and previous contribution I did there, what I'm missing for this one, and I would like to discuss here, are points like:

  • Is it possible to declare a dependency between addons? (this one would require ingress addon for instance, I haven't seen this possibility from the code, but there is a validation block that may be used for that?)
  • At the moment the container image that would be used by the addon is above 500MB, if we would add a command like minikube getstarted, would be ok then, from user perspective, the waiting time of such container images download? At least for the first time it is invoked.

I would also add the integration tests for this addon because the installation of the Operator and CRs for the Workshop are part of a sequence of tasks that need to be validated and consistent.

@priyawadhwa
Copy link

Hey @blues-man awesome! To address your questions:

  1. Yup, the validation block is the best spot for this. If both aren't enabled, just return a clear message asking the user to enable both via:
minikube addons enable ingress
minikube addons enable eduk8s

or

minikube start --addons=ingress,eduk8s
  1. I think that should be fine

Sounds good! An integration test would be key here.

@tstromberg tstromberg added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed triage/discuss Items for discussion labels Jun 24, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 22, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 22, 2020
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

5 participants