From 7b718471e50b949579e50521bc8f1d22a3e9cd9d Mon Sep 17 00:00:00 2001 From: Sridhar Gaddam Date: Fri, 17 May 2019 14:12:03 +0530 Subject: [PATCH] Update SUBMARINER_BROKER_URL to use https endpoint Normally in a vanilla kubernetes deployment, there is a single endpoint for kubernetes. However, in some deployments (like OpenShift), there could be multiple endpoints. This patch updates the SUBMARINER_BROKER_URL to use the appropriate "https" endpoint. --- submariner-k8s-broker/templates/NOTES.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/submariner-k8s-broker/templates/NOTES.txt b/submariner-k8s-broker/templates/NOTES.txt index 58f463e..ddef796 100644 --- a/submariner-k8s-broker/templates/NOTES.txt +++ b/submariner-k8s-broker/templates/NOTES.txt @@ -2,7 +2,7 @@ The Submariner Kubernetes Broker is now setup. You can retrieve the server URL by running - $ SUBMARINER_BROKER_URL=$(kubectl -n default get endpoints kubernetes -o jsonpath="{.subsets[0].addresses[0].ip}:{.subsets[0].ports[0].port}") + $ SUBMARINER_BROKER_URL=$(kubectl -n default get endpoints kubernetes -o jsonpath="{.subsets[0].addresses[0].ip}:{.subsets[0].ports[?(@.name=='https')].port}") The broker client token and CA can be retrieved by running