-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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 scenarios run old / unsupported Minikube and Kubernetes version #37817
Comments
@medyagh: This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the The 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. |
/retitle Katacoda scenarios run old / unsupported Kubernetes version |
If someone improves this, then the minikube version used by "Interactive Tutorials" might be updated as well, if needed. e.g., https://kubernetes.io/docs/tutorials/kubernetes-basics/explore/explore-interactive/
GitHub repo: https://github.com/katacoda-scenarios/kubernetes-bootcamp-scenarios |
Hi @jihoon-seo , Katacoda is not maintained anymore so highly unlikely the scenarios will be updated. |
Katacoda for Kubernetes is maintained a bit. The main thing we're short of is contributor time. |
@sftim alright, I was talking about the main katacoda site. |
is there a repo you could point us to , we could contribute a PR for it |
The repo is https://github.com/katacoda-scenarios/kubernetes-bootcamp-scenarios - as mentioned in #37817 (comment) |
I also looked into killercoda (mentioned in another thread as an alternative) and it seems a migration should be doable. We would need to contact them to add minikube however, as none of their images appear to include it. |
I've recently left O'Reilly and as such Katacoda so no longer the person to
ask. I believe the Kubernetes.io integration is in a functional but
unsupported position.
Sorry I can't be of any more help now.
…On Wed, 7 Dec 2022, 06:13 nikitar, ***@***.***> wrote:
I also looked into killercoda (mentioned in another thread as an
alternative) and it seems a migration should be doable. We would need to
contact them to add minikube however, as none of their images appear to
include it.
—
Reply to this email directly, view it on GitHub
<#37817 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAUFNS3ZGYDN6CJJE3FZJLWMATJTANCNFSM6AAAAAAR34BNS4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This comment was marked as duplicate.
This comment was marked as duplicate.
See #33936 (comment) |
/close Won't fix because we're removing Katacoda. |
@tengqm: Closing this issue. In response to this:
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. |
in this minikube tutorial I see Katakoda
https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/
but the minikube version in it is ancient it is v.1.18.0
the latest minikube version is 1.28.0
is there a way to update Katakoda in Kubernetes website?
The text was updated successfully, but these errors were encountered: