-
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
[ru] Screen resolution compatibility issue for online interactive tutorial terminal in the "Create a cluster" page #42455
Comments
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. |
Page related to issue: https://kubernetes.io/ru/docs/tutorials/kubernetes-basics/create-cluster/cluster-interactive/ |
/retitle [ru] Screen resolution compatibility issue for online interactive tutorial terminal in the "Create a cluster" page |
@kborovikov Katacoda environment for the Kubernetes tutorial has been shut down. Refer the announcement here. We have an umbrella issue raised #41496 to remove tutorials that rely on Katacoda for all localized documents. |
The actual bug here is that the Russian page is out of date. I'm afraid that we're short of capacity in this team, partly as a result of the war where Russia has invaded Ukraine. |
/kind bug |
|
I am currently working on this page (among many others) in #41923. Hopefully, I'll finish the remaining pages soon, and it will go live. |
With #42530 merged, this issue is now also resolved. Please, follow the instructions provided on this page now: https://kubernetes.io/ru/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/ |
resolution of my 4k screen. I received a warning "This screen is too small to work with the terminal, please use your computer or tablet."
The text was updated successfully, but these errors were encountered: