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.

Sign up for GitHub

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

Jump to bottom

Issue with /docs/getting-started-guides/ubuntu/ #1391

Closed
1 task done
dannyman opened this issue Oct 5, 2016 · 5 comments
Closed
1 task done

Issue with /docs/getting-started-guides/ubuntu/ #1391

dannyman opened this issue Oct 5, 2016 · 5 comments
Assignees
@steveperry-53
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@dannyman
Copy link

dannyman commented Oct 5, 2016

This is a...

  • Feature Request

Problem:

Most of this doc is missing. It is worse than useless.

For example, the steps are

  1. git clone
  2. set some environment variables
  3. sudo service kube-controller-manager start

Somewhere between steps 1 and 3 should be a part where the software gets installed.

Proposed Solution:

This doc is a blind alley that delays efforts at deploying/understanding kubernetes. Please remove this doc.

Actually useful is http://kubernetes.io/docs/getting-started-guides/kubeadm/

I would really appreciate a bare-metal install for an HA cluster on ubuntu. The first step there would probably be the package installations detailed in the kubeadm doc.

Page to Remove:

http://kubernetes.io/docs/getting-started-guides/ubuntu/
@errordeveloper
Copy link
Member

@dannyman thanks for reporting this! I've opened #1659 to cover all of the outdated pages we have. Help would be really welcome, by the way!

@castrojo castrojo mentioned this issue Jan 9, 2017
Merged
@steveperry-53
Copy link
Contributor

Closed #703 in an effort to consolidate.
703 want k8s to work on Ubuntu 16.04.

@steveperry-53 steveperry-53 mentioned this issue Jan 11, 2017
Closed
@zacharysarah
Copy link
Contributor

@steveperry-53 Can we close this issue?

@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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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 Jan 2, 2018
@errordeveloper
Copy link
Member

/close

Let's close, this is very old.

mikutas pushed a commit to mikutas/k8s-website that referenced this issue Sep 22, 2022
@CathPag @C-Mejlak
July Hero blog (kubernetes#1391)
55701ab 
* July Hero blog

* update: July's hero blog post

Signed-off-by: Christian Mejlak <chris@mejlak.com>

* add: Dominik Taskai as hero

Signed-off-by: Christian Mejlak <chris@mejlak.com>

* fix: add linkedin link

Signed-off-by: Christian Mejlak <chris@mejlak.com>

* Update july-hero.md

Co-authored-by: Christian Mejlak <chris@mejlak.com>
Okabe-Junya pushed a commit to Okabe-Junya/website that referenced this issue Dec 4, 2023
@electrocucaracha
[es] Sync continuous-integration term (kubernetes#1391)
33ff95d 
Signed-off-by: Victor Morales <chipahuac@hotmail.com>
Okabe-Junya pushed a commit to Okabe-Junya/website that referenced this issue Dec 4, 2023
@electrocucaracha @ramrodo
[es] Sync continuous-integration term (kubernetes#1391)
05873d6 
Signed-off-by: Victor Morales <chipahuac@hotmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@steveperry-53 steveperry-53

Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@errordeveloper @dannyman @zacharysarah @steveperry-53 @k8s-ci-robot @fejta-bot