Origin: Cluster Up/Down document is missing

[lveyde]

[A cluster up/down document that was available at https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md got missing]

Version

[provide output of the openshift version or oc version command]

Steps To Reproduce

1. [Try to open https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md]

Current Result

The document is missing.

Expected Result

The document should be available or at least to point to the new location.

[jwforres]

@mfojtik @derekwaynecarr second bz/issue i've seen today about this doc missing, people are expecting it to be there, should we put in a tombstone or something

[matihost]

...after digging it was removed on 14NOV with this commit:

https://github.com/openshift/origin/commit/f1206f2e637b4cc958fc7ef7dfca0015f43deb58#diff-e3e2a9bfd88566b05001b02a3f51d286

intention was to favor
https://github.com/openshift/installer to start cluster
but main readme.md still shows that oc cluster up is to be used to start the cluster.

and
https://github.com/openshift/installer show that it needs KVM to start openshift.
so essentially it differs from what 'oc cluster up' does .

so the question is - whether it is or will be in the future possible to start local OKD cluster w/o virtualization?

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[matihost]

/remove-lifecycle stale

[matihost]

It would be nice if OpenShift / OKD 4.x supports local development with OpenShift and not require virtualization, AWS deployment etc - like it was possible with OKD 3.x

[AndrewMorsillo]

I'm just starting to explore OpenShift and I've run into a bunch of confusion and inconsistent documentation. How do I start a local cluster? Do I use oc cluster up? Do I use minishift? Do I use openshift/installer (which appears to be linux only)? Do I use oc-cluster-wrapper? I've seen pointers to all four of those in various documentation. This is very confusing for people new to OpenShift.

[devops-csaa]

The best documentation for OKD is often found in archive.org - thanks
cluster_up_down.md is at:
https://web.archive.org/web/20180925151411/https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md

[magick93]

It would be nice if OpenShift / OKD 4.x supports local development with OpenShift and not require virtualization, AWS deployment etc - like it was possible with OKD 3.x

If this is what RedHat expects people to do then they should expect an exodus of users. oc cluster up is extremely useful. And the ansible approach to installing is also very good. Its a shame what they are doing.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[erickhagstrom]

/remove-lifecycle stale

[erickhagstrom]

I'm working through the O'Reilly book, _DevOps with OpenShift_. It guides readers through the oc cluster up process, and references the subject document (_cluster_up_down.md_). If you don't want people to use that process any more, that's cool, but please provide SOME document called _cluster_up_down.md_ so that people can learn about the new process when they come here looking for the old one. As things stand, one must do a bit of research just to find this issue. And eventually this issue will go away.

Thanks

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[matihost]

My research update:
okd 3.11 is more than 1 year old and no more releases - forget about it
okd 4.x is alpha - openshift-intaller - aka cloud only installer

For local usage only OCP 4.x - only with embedded VM : https://code-ready.github.io/crc/ - for Ubuntu requires customization: https://github.com/code-ready/crc/issues/917#issuecomment-573460297

However it requires spawning VM, it needs additional ~10 GB RAM just to run it and 27 GB storage, but it is full OpenShift with operators, dashboard, etc.

If you need something smaller - try minikube with "none" provider (aka no VM) or microk8s - but it will differ from OpenShift a lot.

if you need similar to OCP stack (k8s with crio, podman, buildah stack), run minikube with crio as container engine - however it is challenging to run (and minikube warns that it is not tested config permutation).

I was able to run it with tons of workaround: https://github.com/matihost/learning/blob/master/k8s/minikube/start-minikube.sh - with ./start-minikube.sh --with-crio in case you want to minikube w/o VM with crio as container engine (works under Ubuntu). Of course it has no operators, okd dashboard, htpasswd authen etc.

[magick93]

You can find the oc cluster up docs at https://github.com/openshift/origin/blob/release-3.11/docs/cluster_up_down.md

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

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