Remove OKD/OCP cluster provision (#413)

* Remove OKD/OCP cluster provision As second part of ocp/okd kubevirtci cleanup this commits remove the provision part the gocli and the pack8s from it. Signed-off-by: Quique Llorente <[email protected]> * Update images.sh with gocli sha Signed-off-by: Quique Llorente <[email protected]>
kubevirt · Jul 22, 2020 · 74fb303 · 74fb303
1 parent 9e259e4
commit 74fb303
Show file tree

Hide file tree

Showing 45 changed files with 1 addition and 3,021 deletions.
diff --git a/OKD.md b/OKD.md
diff --git a/cluster-provision/README.md b/cluster-provision/README.md
@@ -22,19 +22,6 @@
 * `kubevirtci/k8s-1.15.1`: `sha256:14d7b1806f24e527167d2913deafd910ea46e69b830bf0b094dde35ba961b159`
 * `kubevirtci/k8s-1.16.2`: `sha256:5bae6a5f3b996952c5ceb4ba12ac635146425909801df89d34a592f3d3502b0c`
 
-# OKD clusters in the container with libvirt
-
-* `okd-base` contains all needed packages to provision and run OKD cluster on top of the libvirt provider
-* `okd-4.1` okd-4.1 cluster provisioned with OpenShift installer on top of the libvirt provider, this image contains custom libvirt image that includes fixes to deploy new nodes without need to apply any W/A
-* `okd-4.3` okd-4.3 cluster provisioned with OpenShift installer on top of the libvirt provider, this image contains custom libvirt image that includes fixes to deploy new nodes without need to apply any W/A
-
-## Versions to use
-
-* `kubevirtci/okd-base`: `sha256:73ede51ce464546a82b81956b7f58cf98662a4c5fded9c659b57746bc131e047`
-* `kubevirtci/okd-4.1`: `sha256:e7e3a03bb144eb8c0be4dcd700592934856fb623d51a2b53871d69267ca51c86`
-* `kubevirtci/okd-4.2`: `sha256:a830064ca7bf5c5c2f15df180f816534e669a9a038fef4919116d61eb33e84c5`
-* `kubevirtci/okd-4.3`: `sha256:63abc3884002a615712dfac5f42785be864ea62006892bf8a086ccdbca8b3d38`
-
 ## Using gocli
 
 `gocli` is a tiny go binary which helps managing the containerized clusters. It
@@ -46,54 +33,6 @@ alias gocli="docker run --net=host --privileged --rm -it -v /var/run/docker.sock
 gocli help
 ```
 
-### How to provision OKD cluster
-
-First you will need to create installer pull token file with the content:
-```
-{"auths":{...}}
-```
-
-and after you should run `gocli` command:
-```bash
-gocli provision okd \
---prefix okd-4.1 \
---dir-scripts <scripts_folder>/scripts \
---dir-hacks <hacks_folder>/hacks \
---master-memory 10240 \
---installer-pull-secret-file <installer_pull_secret_file> \
---installer-repo-tag release-4.1 \
---installer-release-image quay.io/openshift-release-dev/ocp-release:4.1 \
-kubevirtci/okd-base@sha256:73ede51ce464546a82b81956b7f58cf98662a4c5fded9c659b57746bc131e047
-```
-
-***
-NOTE: you can get the pull secret [here](https://cloud.redhat.com/openshift).
-***
-
-***
-NOTE: OpenShift cluster consumes a lot of resources, you should have at least 18Gb of the memory on the machine where do you run the container.
-***
-
-### How to run OKD cluster
-
-You should run `gocli` command:
-```bash
-gocli run okd --prefix okd-4.1 --ocp-console-port 443 --installer-pull-secret-file <installer_pull_secret_file> --background kubevirtci/okd-4.1@sha256:e7e3a03bb144eb8c0be4dcd700592934856fb623d51a2b53871d69267ca51c86
-```
-
-### How to connect to the OKD console
-
-To connect the OKD console you should add once hosts to the `/etc/hosts`
-
-```bash
-127.0.0.1 console-openshift-console.apps.test-1.tt.testing
-127.0.0.1 oauth-openshift.apps.test-1.tt.testing
-```
-
-and specify the `--ocp-console-port` under the `gocli` run command to `443`.
-
-After you can connect to the https://console-openshift-console.apps.test-1.tt.testing and login via `htpasswd_provider` provider with `admin` user and password.
-
 ## Quickstart Kubernetes
 
 ### Start the cluster