gustavocoding/oc-cluster-up

OKD 4.0.0 from master with the admin console and operatore-lifecycle-manager

oc-cluster-up's Issues

Unable to start

This is what i get:

[root@HOSTNAME ~]# docker run --name oc-cluster-up -it -p 9000:9000 -v /tmp/:/tmp/ -v /var/run/docker.sock:/var/run/docker.sock gustavonalle/oc-cluster-up
Using default tag: latest
Trying to pull repository docker.io/gustavonalle/openshift-dind-node ...
latest: Pulling from docker.io/gustavonalle/openshift-dind-node
Digest: sha256:fe1be2fad6c6c737422f166f17a4df8befc1def6be306ca0c4434a2688cae370
Status: Image is up to date for docker.io/gustavonalle/openshift-dind-node:latest
Using default tag: latest
Trying to pull repository docker.io/gustavonalle/openshift-dind-master ...
latest: Pulling from docker.io/gustavonalle/openshift-dind-master
Digest: sha256:0be3bcb22cbbdfebdd6ebc79360a714dce08da47a323f39ef8db74391ef3131c
Status: Image is up to date for docker.io/gustavonalle/openshift-dind-master:latest
Starting dind cluster 'openshift' with plugin 'redhat/openshift-ovs-multitenant' and runtime 'dockershim'

ERROR: Can't start.  Existing cluster parts (1 existing master or 1 existing nodes)

I'm on Centos 7. My docker info:

Containers: 3
 Running: 0
 Paused: 0
 Stopped: 3
Images: 20
Server Version: 1.13.1
Storage Driver: overlay2
 Backing Filesystem: xfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: journald
Cgroup Driver: systemd
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: docker-runc runc
Default Runtime: docker-runc
Init Binary: /usr/libexec/docker/docker-init-current
containerd version:  (expected: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1)
runc version: df5c38a9167e87f53a9894d77c0950e178a745e7 (expected: 9df8b306d01f59d3a8029be411de015b7304dd8f)
init version: fec3683b971d9c3ef73f284f176672c44b448662 (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Security Options:
 seccomp
  WARNING: You're not using the default seccomp profile
  Profile: /etc/docker/seccomp.json
 selinux
Kernel Version: 3.10.0-957.12.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 3
CPUs: 8
Total Memory: 7.587 GiB
Name: edaarah.app
ID: DNI6:YCBM:ALTQ:S2I3:DFWJ:KBGL:VT4L:MEA4:YIZ5:DKMG:RMFT:POJJ
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 172.30.0.0/16
 127.0.0.0/8
Live Restore Enabled: false
Registries: docker.io (secure)

Cluster size

By default one master and two nodes will be started, a parameter should exist to choose the number of nodes, where n=0 would launch only the master

Support for OKD 4.1

Recently the dind support in master has received some love in the form a PR: openshift/origin#22293
This should be enough to update the image to the latest code

console frontend redirect to localhost:9000

When installed on a external server the tool always redirect to localhost:9000.

Cannot build on dockerhub

The build fails due to memory exhaustion caused by the go linker

Registry support

Pre-install and configure a docker registry, accessible from outside , and make sure the docker engine in each node of the cluster is preconfigured to use that registry in addition to the public registries.

This will allow the user to push an image from outside and avoid that each node downlad the image redundantly.

Notify users of host modification to load the overlay and openvswitch modules

Since this deployment utilizes openshift/origin/hack/dind-cluster.sh, you might want to notify users in the README.md of the warning in dind-cluster.sh:

WARNING: The script modifies the host that docker is running on. It

attempts to load the overlay and openvswitch modules. If this modification

is undesirable consider running docker in a VM.

It would be nice to know that in advance, only reason I was aware is because I worked through the entire container Dockerfile build and then dind launch sequence and combed through all of the scripting to understand how it all worked.

Thanks.

Ubuntu support

Does this works on Ubuntu?

I'm getting this error:

[openshift/dind] Step 8/17 : RUN dnf -y update && dnf -y install docker glibc-langpack-en iptables openssh-clients openssh-server tcpdump
[openshift/dind] ---> Running in a43e799706b8
[openshift/dind] Error: Failed to synchronize cache for repo 'updates'
[openshift/dind] The command '/bin/sh -c dnf -y update && dnf -y install docker glibc-langpack-en iptables openssh-clients openssh-server tcpdump' returned a non-zero code: 1
[ERROR] hack/dind-cluster.sh:800: return "${result}" exited with status 1.
/root//go/src/github.com/openshift/origin/run.sh: line 6: /root/go/src/github.com/openshift/origin/dind-openshift.rc: No such file or directory

....

Error: No such object: openshift-master
2019/01/15 14:12:27 cmd/main: cookies are not secure because base-address is not https!
2019/01/15 14:12:27 cmd/main: Error initializing OIDC authenticator: file examples/ca.crt contained no CA data

Thank you

readme links are incorrectly formatted

links to external github repositories need to start with https:// so github knows to look outside of this repo for the URL.

Prometheus

The Prometheus operator should be installed to provide metrics. It should include all dependent services, like Grafana, Node Exporter and the Alert Manager.

Install Git on the nodes

S2I requires git presence in the cluster nodes.