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

Issue with k8s.io/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/ #13746

Closed
Ragzputin opened this issue Apr 10, 2019 · 9 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. language/en Issues or PRs related to English language 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

@Ragzputin
Copy link

This is a Bug Report

Problem:
This is not a bug, more of an English language issue. The explanations in this page (like many others) are hard to understand.

Proposed Solution:
I have simplified the explanations under the "Kubernetes Cluster" section. Here are my proposed changes. Feel free to improve.

---Proposed Solution Starts Here---
"Kubernetes coordinates clusters of computers. These computers work as a single unit. Kubernetes allows you to deploy applications in containers to a cluster. It does this without tying them to a single machine. To use this deployment model, we first disconnect applications from their individual hosts. In other words, we put them in containers. Such applications are more flexible and available. In past deployment models, we would install applications onto specific machines as packages. These apps would be integrated into the host. Kubernetes distributes and schedules these containers. Kubernetes is open-source and ready to go live.

A Kubernetes cluster consists of two types of resources:
The Master coordinates the cluster
Nodes are the workers that run applications

Summary:

Kubernetes cluster
Minikube

Kubernetes is a production-grade, open-source platform that schedules and executes container clusters."
---Proposed Solution Ends Here---

Keep it simple!

Page to Update:
https://kubernetes.io/...

@Ragzputin Ragzputin added the kind/bug Categorizes issue or PR as related to a bug. label Apr 10, 2019
@thecrudge
Copy link
Contributor

Ill take it

@thecrudge
Copy link
Contributor

#13831

@sftim
Copy link
Contributor

sftim commented Jun 4, 2019

/language en

@k8s-ci-robot k8s-ci-robot added the language/en Issues or PRs related to English language label Jun 4, 2019
@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 2, 2019
@sftim
Copy link
Contributor

sftim commented Sep 10, 2019

/priority backlog
/kind feature

@k8s-ci-robot k8s-ci-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. kind/feature Categorizes issue or PR as related to a new feature. labels Sep 10, 2019
@sftim
Copy link
Contributor

sftim commented Sep 10, 2019

/remove-kind bug

@k8s-ci-robot k8s-ci-robot removed the kind/bug Categorizes issue or PR as related to a bug. label Sep 10, 2019
@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 11, 2019
@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. language/en Issues or PRs related to English language 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