Fabric8-Arquillian - Can it run against Vanilla Kubernetes?
16 views
Skip to first unread message
Yong Kim
Mar 16, 2016, 12:30:08 PM3/16/16
to fabric8
Hello,
We are trying to use Fabric8-Arquillian for Integration testing and it works fine with the Fabric8 Vagrant image which includes OpenShift, but we're having problems running it against a Vanilla Kubernetes cluster. The problem is that the io.fabric8.arquillian.kubernetes.SessionListener tries to create routes for services (line 261) and then fails when the SessionListener uses the io.fabric8.kubernetes.api.Controller to apply the routes. Is there any way to do run this against Vanilla Kubernetes or is OpenShift actually needed? Also, why does it need to create routes? Isn't everything running inside K8s, so it doesn't need to create them?
Thanks!
Yong Kim
James Strachan
Mar 16, 2016, 12:42:35 PM3/16/16
to Yong Kim, fabric8
On 16 March 2016 at 16:30, Yong Kim <yong...@gmail.com> wrote:
Hello,We are trying to use Fabric8-Arquillian for Integration testing and it works fine with the Fabric8 Vagrant image which includes OpenShift, but we're having problems running it against a Vanilla Kubernetes cluster. The problem is that the io.fabric8.arquillian.kubernetes.SessionListener tries to create routes for services (line 261) and then fails when the SessionListener uses the io.fabric8.kubernetes.api.Controller to apply the routes.
Sorry about that!
I've raised an issue to fix this
should be an easy fix to only do the Route thing on OpenShift!
Is there any way to do run this against Vanilla Kubernetes or is OpenShift actually needed? Also, why does it need to create routes? Isn't everything running inside K8s, so it doesn't need to create them?
The reason for creating the routes is purely to work around a limitation in OpenShift...
really the Route should created automatically and we should be able to define a Service once and it can then be ran on Kubernetes or OpenShift and it'd just work. However to get an external URL for a service on OpenShift you unfortunately need to create a Route - and we don't want to put Routes inside our kubernetes resources since they are OpenShift specific.
Medium: https://medium.com/@jstrachan/
Blog: http://macstrac.blogspot.com/
fabric8: http://fabric8.io/
Blog: http://macstrac.blogspot.com/
fabric8: http://fabric8.io/
Yong Kim
Mar 16, 2016, 1:41:40 PM3/16/16
to fabric8
Thanks for the explanation and quick response, James! I'll keep an eye out for the pull request.
Ioannis Canellos
Mar 16, 2016, 3:43:26 PM3/16/16
to Yong Kim, fabric8
Created a pull request that fixes the issue and adds itests to prevent future regressions.
--
You received this message because you are subscribed to the Google Groups "fabric8" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fabric8+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Ioannis Canellos
Yong Kim
Mar 18, 2016, 11:19:24 AM3/18/16
to fabric8
Great, thanks! Confirmed this is working for vanilla Kubernetes.
On Wednesday, March 16, 2016 at 12:30:08 PM UTC-4, Yong Kim wrote:
James Strachan
Mar 18, 2016, 11:26:32 AM3/18/16
to Yong Kim, fabric8
Awesome, thanks for letting us know!
--
You received this message because you are subscribed to the Google Groups "fabric8" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fabric8+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages