I wanted to setup a complete CI/CD environment including GitLab pods to show webhooks on my local osx machine. As it's not possible to do this with an OSCP bound to 127.0.0.1, I wanted to test it with an OSCP bound to my WI-FI IP address.
As soon as I specify OC_CLUSTER_PUBLIC_HOSTNAME the whole installation still runs fine (no errors). But the resulting OpenShift environment is not usable, as there are no projects like openshift-infra, default etc. being created and provisioned.
I am using current enterprise oc client release 3.4.1.2.
export OC_CLUSTER_PUBLIC_HOSTNAME=10.1.2.2
oc-cluster up moscow --metrics --logging
[INFO] Running a new cluster
oc cluster up --public-hostname 10.1.2.2 --routing-suffix 10.1.2.2.xip.io --host-data-dir /Users/wanja/.oc/profiles/moscow/data --host-config-dir /Users/wanja/.oc/profiles/moscow/config --use-existing-config -e TZ=MSK --metrics --logging
-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for registry.access.redhat.com/openshift3/ose:v3.4.1.2 image ... OK
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... OK
-- Checking type of volume mount ...
Using Docker shared volumes for OpenShift volumes
-- Creating host directories ... OK
-- Finding server IP ... ***** look here *****
Using public hostname IP 10.1.2.2 as the host IP
Using 127.0.0.1 as the server IP
-- Starting OpenShift container ...
Creating initial OpenShift configuration
Starting OpenShift using container 'origin'
Waiting for API server to start listening
OpenShift server started
-- Adding default OAuthClient redirect URIs ... OK
-- Installing registry ... OK
-- Installing router ... OK
-- Installing metrics ... OK
-- Importing image streams ... OK
-- Importing templates ... OK
-- Installing logging ... OK
-- Login to server ... OK
-- Creating initial project "myproject" ... OK
-- Removing temporary directory ... OK
-- Server Information ...
OpenShift server started.
The server is accessible via web console at:
https://127.0.0.1:8443
The metrics service is available at:
https://metrics-openshift-infra.10.1.2.2.xip.io
The kibana logging UI is available at:
https://kibana-logging.10.1.2.2.xip.io
You are logged in as:
User: developer
Password: developer
To login as administrator:
oc login -u system:admin
-- Any user is sudoer. They can execute commands with '--as=system:admin'
-- 10 Persistent Volumes are available for use
-- User admin has been set as cluster administrator
switched to context "moscow".
-- Adding an oc-profile=moscow label to every generated image so they can be later removed
[INFO] Cluster created succesfully
Restarting openshift. Done
I wanted to setup a complete CI/CD environment including GitLab pods to show webhooks on my local osx machine. As it's not possible to do this with an OSCP bound to 127.0.0.1, I wanted to test it with an OSCP bound to my WI-FI IP address.
As soon as I specify OC_CLUSTER_PUBLIC_HOSTNAME the whole installation still runs fine (no errors). But the resulting OpenShift environment is not usable, as there are no projects like openshift-infra, default etc. being created and provisioned.
I am using current enterprise oc client release 3.4.1.2.