Updated README to reflect the changes in installer

Links for the installer, secrets, etc.. have changed lately. Update
the documentation to reflect that.
Also remove the images section, that is not currently used.

Change-Id: I351134335b3b73efcfb36542e0785ccc357208d9

diff --git a/README.md b/README.md
index aa4ec46..50db330 100644 (file)
--- a/README.md
+++ b/README.md
@@ -4,10 +4,9 @@ This repository contains the installer for the Akraino KNI deployment. Along wit
 
 ## Dependencies
 
-You will need to create an account on [http://cloud.openshift.com/](http://cloud.openshift.com/)
-This is needed to have download access to the OpenShift installer artifacts.
-After that, you will need to download the Pull Secret from
-[https://cloud.openshift.com/clusters/install](https://cloud.openshift.com/clusters/install) - Step 4: Deploy the Cluster
+You will need to create a Red Hat account on [https://www.redhat.com/wapps/ugc/register.html](https://www.redhat.com/wapps/ugc/register.html), then login with your account into [https://cloud.redhat.com/openshift](https://cloud.redhat.com/openshift). This is needed to have download access to the OpenShift installer artifacts.
+After that, you will need to get the Pull Secret from
+[https://cloud.redhat.com/openshift/install/metal/user-provisioned](https://cloud.redhat.com/openshift/install/metal/user-provisioned) - Copy Pull Secret link.
 
 ## How to build
 
@@ -145,8 +144,7 @@ build/auth directory:
     export KUBECONFIG=./build/auth/kubeconfig
 
 Then cluster can be managed with oc. You can get the client on this link
-[https://cloud.openshift.com/clusters/install](https://cloud.openshift.com/clusters/install)
-- Step 5: Access your new cluster.
+[https://mirror.openshift.com/pub/openshift-v4/clients/ocp/latest/](https://mirror.openshift.com/pub/openshift-v4/clients/ocp/latest/), and check for `openshift-client` files (there are versions for Linux, Mac and Windows). Once downloaded, uncompress it, give it execution permissions and move to the desired path. After that, regular `oc` commands can be executed over the cluster.
 
 ## How to destroy the cluster
 
@@ -155,9 +153,9 @@ In order to destroy the running cluster, and clean up environment, just use
 
 ## Building and consuming your own installer
 
-The openshift-installer binaries are published on [https://github.com/openshift/installer/releases](https://github.com/openshift/installer/releases).
-For faster deploy, you can grab the installer from the upper link. However, there may be situations where you need to compile your own installer (such as the case of libvirt), or you need a newer version.
-You can build the binary following the instructions on [https://github.com/openshift/installer](https://github.com/openshift/installer) , or you can use the provided target from our project.
+The openshift-installer binaries are published on [https://mirror.openshift.com/pub/openshift-v4/clients/ocp/latest/](https://mirror.openshift.com/pub/openshift-v4/clients/ocp/latest/).
+For faster deploy, you can grab the installer from the upper link. However, there may be situations where you need to compile your own installer (such as the case of libvirt), or when you need a newer version.
+You can build the binary following the instructions on [https://github.com/openshift/installer](https://github.com/openshift/installer) - Quick Start section, or you can use the provided target from our project.
 The binary can be produced with the following command:
 
     make binary
@@ -180,16 +178,4 @@ This will generate a pair of folders: manifests and openshift. Those manifests
 can be modified with the desired values. After that this code can be executed to
 generate a new cluster based on the modified manifests:
 
-    /path/to/openshift-install create cluster
-
-## How to create images (WIP)
-
-For the installer to work on baremetal, it needs a different type of images: installer image (kernel, ramdisk), and the deployment image (raw). To generate the images please execute:
-
-    make images
-
-By default it will generate RHCOS Maipo images. But ootpa can be generated by:
-
-    make images RHCOS_VERSION=ootpa
-
-And this will leave the needed images inside your build directory. Those can be used later for a baremetal deploy.
+    /path/to/openshift-install create cluster
\ No newline at end of file