- OpenShift v3.7+ or higher deployed. We recommend using minishift to get a cluster up quickly.
oc
installed on your local machine.
Once your OpenShift cluster is up and running, run the following command to deploy Gloo and Envoy to the gloo-system
namespace:
oc apply \
--filename https://raw.githubusercontent.com/solo-io/gloo/master/install/openshift/install.yaml
Check that the Gloo pods and services have been created:
oc project gloo-system
oc get all
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deploy/function-discovery 1 1 1 1 3m
deploy/gloo 1 1 1 1 3m
deploy/ingress 1 1 1 1 3m
deploy/ingress-controller 1 1 1 1 3m
deploy/k8s-service-discovery 1 1 1 1 3m
NAME DESIRED CURRENT READY AGE
rs/function-discovery-74cbdb66b5 1 1 1 3m
rs/gloo-6f68b9f7d6 1 1 1 3m
rs/ingress-controller-78cfcd7f78 1 1 1 3m
rs/ingress-d5478d8c8 1 1 1 3m
rs/k8s-service-discovery-84744c4676 1 1 1 3m
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deploy/function-discovery 1 1 1 1 3m
deploy/gloo 1 1 1 1 3m
deploy/ingress 1 1 1 1 3m
deploy/ingress-controller 1 1 1 1 3m
deploy/k8s-service-discovery 1 1 1 1 3m
NAME DESIRED CURRENT READY AGE
rs/function-discovery-74cbdb66b5 1 1 1 3m
rs/gloo-6f68b9f7d6 1 1 1 3m
rs/ingress-controller-78cfcd7f78 1 1 1 3m
rs/ingress-d5478d8c8 1 1 1 3m
rs/k8s-service-discovery-84744c4676 1 1 1 3m
NAME READY STATUS RESTARTS AGE
po/function-discovery-74cbdb66b5-zknxp 1/1 Running 0 3m
po/gloo-6f68b9f7d6-hn46t 1/1 Running 0 3m
po/ingress-controller-78cfcd7f78-nmqm6 1/1 Running 0 3m
po/ingress-d5478d8c8-w6kxs 1/1 Running 0 3m
po/k8s-service-discovery-84744c4676-sdtgt 1/1 Running 0 3m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/gloo ClusterIP 10.107.176.154 <none> 8081/TCP 3m
svc/ingress NodePort 10.96.48.30 <none> 8080:30145/TCP,8443:31071/TCP 3m
Everything should be up and running. If this process does not work, please open an issue. We are happy to answer questions on our diligently staffed Slack channel.
See Getting Started on OpenShift to get started creating routes with Gloo.