-
Notifications
You must be signed in to change notification settings - Fork 753
kubeless on Openshift/Minishift 3.6 #390
Comments
Kubeless versions prior to 0.2.0 must work for you: still uses TPR. Can you share logs of kubeless-controller? |
Thank you for your fast reply. When I deploy kubeless-rbac-v0.1.0.yaml on Minishift kubeless-controller prints following log message over and over again: |
@jberggg kubeless was only test on openshift 1.5.1 which was the release prior to 3.6. 3.6 does not include TPR afaik, and 3.7 does not include CRD yet. so you need to use minishift 1.5.0 (which has TPR) and downgrade to kubeless 0.1.0 The version numbers are confusing, the support of TPR and CRD is not yet well advertized in openshift so I know this is very confusing. We probably need to remove the openshift manifest until an openshift release that supports CRD. |
I checked with the openshift folks, 3.7 should come out late november and it should have CRD. So we should be able to run kubeless on openshift 3.7 just before kubecon :) |
I am going to leave this open and as soon as openshift 3.7 is released we should validate our release on it. |
Thank you for the investigation and the update :) |
Openshift released a RC version
All looks good, the CustomResourceDefinition is there:
But the kubeless-controller failed to deploy functions, the logs:
Is this problem rooted in Openshift or Kubeless? |
It seems to be an RBAC issue, we have not tried yet on openshift 3.7. Can you run |
@sebgoa Sure, I suppose you meant
|
GKE 1.7.8:
|
Openshift just released v3.7.0 stable today. I will give a try once the binary builds appear for 3.7.0 https://github.com/openshift/origin/releases
|
I found several issues with trying to deploy kubeless v0.3.0 over Openshift v3.7.0.
Looking at the
So the problem still persists on v3.7.0 and seems to be related to the format of the CRD: "functions.k8s.io" |
It seems that we can tackle that specific issue specifying different parameters when defining the OwnerReference:
@ngtuna do you know if we can change the Kind and APIVersion to something else? |
@andresmgot We are having issues with Kubeless deployment over Openshift too. Its a slightly different error but I think its all linked to the same issue
We are running Openshift 3.7 and kubeless-openshift-v0.2.4.yaml |
@arjunrao87 it seems that it is an issue related to the APIVersion that we are using. It is cc/ @murali-reddy |
I try to run kubeless on the latest Minishift release:
For kubeless version 0.2.3 there seems to be a compatibility issue with Openshift. As far as I understood kubeless uses a new Custom Resource Definition (of Kubernetes v1.7.0+, according to the release notes) from version 0.2.0 on. This probably breaks compatibility with Openshift because version 3.6 is based on Kubernetes 1.6. I run into this issue:
I can deploy the 0.1.0 kubeless version on the Openshift cluster without errors. However, if I then run a
kubeless function ls
command I get an...server could not find...
error. Same if I try to deploy something with kubeless.Does anyone know if/how I can make kubeless work on a minishift instance? Thank you for your help!
The text was updated successfully, but these errors were encountered: