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 /docs/getting-started-guides/ubuntu/ #1391

Closed
dannyman opened this Issue Oct 5, 2016 · 5 comments

Comments

Projects
None yet
6 participants
@dannyman

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

This comment has been minimized.

Member

errordeveloper commented Nov 11, 2016

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

@steveperry-53

This comment has been minimized.

Contributor

steveperry-53 commented Jan 11, 2017

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

@zacharysarah

This comment has been minimized.

Contributor

zacharysarah commented Aug 7, 2017

@steveperry-53 Can we close this issue?

@fejta-bot

This comment has been minimized.

fejta-bot commented Jan 2, 2018

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

@errordeveloper

This comment has been minimized.

Member

errordeveloper commented Jan 15, 2018

/close

Let's close, this is very old.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment