Openshift: use of external Kubernetes is no longer supported

[andybrucenet]

Can no longer use the openshift-origin recipe to deploy openshift over existing kubernetes.

docker run --privileged -v /Users/l.abruce/proj/git/lmgitlab.hlsdev.local/l.lmil/lmil_sysadmin/demos/JMorenz/2017-03-MDE-ATO/poc/localdata/openshift/config:/config --name default-mde-ato-openshift-origin-openshift-master-run openshift/origin start master --kubeconfig=/config/kubeconfig --master=https://localhost:8443 --public-master=https://192.168.98.100:17082 --etcd=http://etcd:2379

W0715 18:12:48.465226       1 start_master.go:294] Warning: assetConfig.loggingPublicURL: Invalid value: "": required to view aggregated container logs in the console, master start will continue.
W0715 18:12:48.465357       1 start_master.go:294] Warning: assetConfig.metricsPublicURL: Invalid value: "": required to view cluster metrics in the console, master start will continue.
W0715 18:12:48.465371       1 start_master.go:294] Warning: serviceAccountConfig.publicKeyFiles: Invalid value: "": no service account tokens will be accepted by the API, which will prevent builds and deployments from working, master start will continue.
W0715 18:12:48.465381       1 start_master.go:294] Warning: auditConfig.auditFilePath: Required value: audit can not be logged to a separate file, master start will continue.
F0715 18:12:48.465397       1 start_master.go:115] KubernetesMasterConfig is required to start this server - use of external Kubernetes is no longer supported.

[ahmetb]

/assign @Kargakis
can you take a look?

Ideally we'd want to move these 3rd party recipes out of this repository. If you've got a Helm chart or another repository that supersedes this example, we should point users in the right direction.

[0xmichalis]

/unassign
/assign @derekwaynecarr

[livsky87]

Hello @derekwaynecarr ,

I wonder the current status of this issue.
Is it deprecated?

I have same issue "KubernetesMasterConfig is required to start this server - use of external Kubernetes is no longer supported."

[tiagorosendo]

any update ?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close