<div dir="ltr">Hi Markus,<div> </div><div>0.9.0 should work fine with with Kubernetes 1.9 / OpenShift 3.9. Could you share the complete log from the CO? The Kubernetes client normally takes the address of the Kubernetes APi from the Kubernetes environment variables and connects there. Maybe in your case there is something strange / wrong with your cluster configuration.</div><div> </div><div>Thanks & Regards</div><div>Jakub</div></div> <div class="gmail_quote"><div dir="ltr">On Mon, Jan 7, 2019 at 2:40 PM Schwarz, Markus <<a href="mailto:M.Schwarz@prosoz.de">M.Schwarz@prosoz.de</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div lang="DE"> <div class="gmail-m_-214744936782785207WordSection1"> Hi, We are currently running strimzi 0.4.0 ( I know, it’s old) on our Openshift Origin 3.9 cluster and everything is working about fine. I know try to update to 0.9.0 to catch up to things and implement some security. So I took all the yaml-files from the cluster-operator install folder, made the necessary namespace amendments and gave it a try. The strimzi-cluster-operator pod tries to start but then dies with the following error message: --- 2019-01-07 12:49:29 WARN WatchConnectionManager:185 - Exec Failure: HTTP 404, Status: 404 - 404 page not found java.net.ProtocolException: Expected HTTP 101 response but was '404 Not Found' at okhttp3.internal.ws.RealWebSocket.checkResponse(RealWebSocket.java:219) [cluster-operator-0.9.0.jar:0.9.0] at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:186) [cluster-operator-0.9.0.jar:0.9.0] at okhttp3.RealCall$AsyncCall.execute(RealCall.java:153) [cluster-operator-0.9.0.jar:0.9.0] at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) [cluster-operator-0.9.0.jar:0.9.0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_191] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_191] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_191] 2019-01-07 12:49:29 INFO WatchConnectionManager:379 - Current reconnect backoff is 1000 milliseconds (T0) 2019-01-07 12:49:29 ERROR Main:141 - Cluster Operator verticle in namespace msw failed to start io.fabric8.kubernetes.client.KubernetesClientException: 404 page not found at io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager$2.onFailure(WatchConnectionManager.java:189) ~[cluster-operator-0.9.0.jar:0.9.0] at okhttp3.internal.ws.RealWebSocket.failWebSocket(RealWebSocket.java:546) ~[cluster-operator-0.9.0.jar:0.9.0] at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:188) ~[cluster-operator-0.9.0.jar:0.9.0] at okhttp3.RealCall$AsyncCall.execute(RealCall.java:153) ~[cluster-operator-0.9.0.jar:0.9.0] at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) ~[cluster-operator-0.9.0.jar:0.9.0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_191] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_191] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_191] --- It seems to try to open a websocket connection on a url which does not exists. I don’t know if this is connected to the outdated version of kubernetes (1.9.1) or if this might be a configuration error of some sort, any hint will be appreciated. I could not find any kubernetes/openshift version requirements for strimzi. Thanks! Markus </div> <a href="http://www.prosoz.de" target="_blank"><img width="555" height="264" style="border: 0px solid;" src="cid:168289e0084772e90ff1"></a> prosoz-herten-footer </div> _______________________________________________ Strimzi mailing list <a href="mailto:Strimzi@redhat.com" target="_blank">Strimzi@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/strimzi" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/strimzi</a> </blockquote></div>