as your suggest, I just enable TEMPLATE_SERVICE_BROKER, then I can get pod
in namespace openshift-template-service-broker and kube-service-catalog
[root@origin-master1 ~]# oc get pods -n kube-service-catalog
>
> NAME READY STATUSRESTARTS AGE
>
> apiserver-4gwx91/1 Running 0 2d
>
> controller-manager-nqr87 1/1 Running 0 2d
>
> [root@origin-master1 ~]# oc get pods -n openshift-template-service-broker
>
> NAME READY STATUSRESTARTS AGE
>
> apiserver-7xjbq 1/1 Running 0 2d
>
> apiserver-b8g4w 1/1 Running 0 2d
>
> apiserver-dk445 1/1 Running 0 2d
>
> apiserver-mfx2s 1/1 Running 0 2d
>
> apiserver-ntd7l 1/1 Running 0 1d
>
> apiserver-ws28t 1/1 Running 0 2d
>
> apiserver-xclwr 1/1 Running 0 2d
>
> apiserver-zvmdw 1/1 Running 0 2d
>
> [root@origin-master1 ~]# oc get template
>
>
On Fri, Dec 8, 2017 at 11:34 PM, Sam Padgett wrote:
> On Fri, Dec 8, 2017 at 9:19 AM, Tran Tien Dung
> wrote:
>
>> Thanks for your responding. There is no namespaces kube-service-catalog
>> and openshift-template-service-broker
>>
>
> If you run...
>
> curl -k https:///console/scripts/extensions.js
>
> Do you see a line like this?
>
> window.OPENSHIFT_CONSTANTS.TEMPLATE_SERVICE_BROKER_ENABLED = true;
>
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev