-
Notifications
You must be signed in to change notification settings - Fork 15.1k
Restructure the Ubuntu Getting Started section. #1932
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
Restructure the Ubuntu Getting Started section. #1932
Conversation
|
@kubernetes/sig-cluster-lifecycle @roberthbailey Is this something cluster lifecycle should look at? |
| path: /home/ubuntu/etcd-snapshots/etcd-snapshot-2016-11-09-02.41.47.tar.gz | ||
| sha256: 1dea04627812397c51ee87e313433f3102f617a9cab1d1b79698323f6459953d | ||
| size: 68K | ||
| status: completed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
close this code block
| The cluster must be in a state of only having a single member. So it's best to | ||
| deploy a new cluster using the etcd charm, without adding any additional units. | ||
|
|
||
| juju deploy etcd new-etcd |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be in a code block?
|
|
||
| > The above code snippet will deploy a single unit of etcd, as 'new-etcd' | ||
|
|
||
| juju run-action etcd/0 restore target=/mnt/etcd-backups |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be in a code block?
| @@ -0,0 +1,11 @@ | |||
| # GLossary and Terminology | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GLossary
|
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ to sign the CLA. Once you've signed, please reply here (e.g. "I signed it!") and we'll verify. Thanks.
If you have questions or suggestions related to this bot's behavior, please file an issue against the kubernetes/test-infra repository. |
|
Sorry, bad rebase, sorry for the spam folks, fixed. |
|
@castrojo - needs rebase |
|
Also assigning @jaredbhatti for tech writer review. |
|
Tech LGTM |
|
Fixes #2041 |
|
Fixes #1952 |
|
Pinged to put content into our new templates: Thanks! |
| Copy the snapshot to the local disk and then check the sha256sum. | ||
|
|
||
| ``` | ||
| juju scp etcd/0:/home/ubuntu/etcd-snapshots/etcd-snapshot-2016-11-09-02.41.47.tar.gz . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you're using a code block (```), the indentation isn't necessary. On the deploy preview, it's indented farther than the other code blocks.
|
@castrojo Docs LGTM modulo one wording issue in the main landing page. I think we can merge this once that's fixed. However, we'll do so with the caveat that these kinds of guides to Bare Metal installation/running guides might/should move to a dedicated portion of the site. |
| --- | ||
|
|
||
| {% capture overview %} | ||
| There are multiple ways to run a Kubernetes with Ubuntu. These pages explain how to deploy Kubernetes on Ubuntu on multiple public and private clouds, as well as bare metal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"run a Kubernetes" -> "run Kubernetes" or "run a Kubernetes cluster"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will be happy to move to a dedicated bare metal section once that's in place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm putting together a proposal that I hope to get out to sig-docs within a week.
- This supercedes PR #1770 - This breaks up the section from one huge installation page into: - A new index page. - New support grid with commercial and community support options. - Move to lifecycle-based pages based on operational tasks. - Add support for local deployments via LXD. - Added screenshots to images/docs/ubuntu - Add backup page. - Add decommissioning page. - Add a glossary of terms page. - Rewritten installation page. - Add logging page. - Add monitoring page. - Add networking page, flannel only for now, calico in progress. - Add a scaling page. - Add a security page. - Add a storage page. - Add a troubleshooting page. - Add an upgrade page. - Add a cluster validation page. - Add new ubuntu content to the index page. - Add Ubuntu to _data TOC. - Add warning about choosing ipv6 with LXD, thanks Ed Baluf. - Template-ize all the pages per jaredb's review.
|
Thanks! Merging now. |
As per discussions on sig-cluster-lifecycle, we'd like our docs to be more lifecycle focused instead of one huge installation page. This breaks down the one big page into multiple smaller pages, it is mostly all new content.
This change is