Starting kubeless | kubeless-controller-manager in CrashLoopBackOff #1152
Comments
|
I @iamshreeram, can you get the logs of the container failing? First you need to get which one of the 3 containers is failing (you can that info from the pod description), then get the logs with |
|
@andresmgot , Thanks for looking at the issue. Below is the error for all 3 containers [kubeless-function-controller, http-trigger-controller, cronjob-trigger-controller] in all 3 pods : |
|
ah, I see the problem. You are using the manifest that doesn't include the RBAC configuration (and RBAC is now always enabled by default). Install Kubeless like this: (rather than using the |
|
@andresmgot , Thanks for response. Does this mean users can never use |
|
While it's not usual, people can disable RBAC in their clusters. If they do so, the manifest with RBAC rules will fail, that's why we offer the two options. In the documentation, we point to the other manifest but if you think of another way of making it more prominent please send a PR to help others: https://github.com/kubeless/kubeless/blob/master/docs/quick-start.md |
|
@andresmgot , I think we can just remove - Let me know. thanks! |
|
Yes, we can do that. I don't think that file is used very often. |
|
I had the same issue, and it took me a while until I found this page. I also vote for the above proposal. |
|
I am having the same issue but not due to RBAC The |
|
@shubhomoy Kubernetes +1.18 is not supported for the cronjob trigger so that may be the reason. See #1130 |
|
I got the same error as @shubhomoy on: The error (parsing position is slightly different, but the error is the same): Error pretty print{
"kind":"CustomResourceDefinition",
"apiVersion":"apiextensions.k8s.io/v1beta1",
"metadata":{
"name":"functions.kubeless.io",
"uid":"f0b89e5a-0ca7-4db2-b133-f65a50fc2566",
"resourceVersion":"2620",
"generation":1,
"creationTimestamp":"2021-07-11T19:36:54Z",
"managedFields":[
{
"manager":"kubectl-create",
"operation":"Update",
"apiVersion":"apiextensions.k8s.io/v1beta1",
"time":"2021-07-11T19:36:54Z",
"fieldsType":"FieldsV1",
"fieldsV1":{
"f:spec":{
"f:conversion":{
".":{
},
"f:strategy":{
}
},
"f:group":{
},
"f:names":{
"f:kind":{
},
"f:listKind":{
},
"f:plural":{
},
"f:singular":{
}
},
"f:preserveUnknownFields":{
},
"f:scope":{
},
"f:version":{
},
"f:versions":{
}
}
}
},
{
"manager":"kube-apiserver",
"operation":"Update",
"apiVersion":"apiextensions.k8s.io/v1",
"time":"2021-07-11T19:36:55Z",
"fieldsType":"FieldsV1",
"fieldsV1":{
"f:status":{
"f:acceptedNames":{
"f:kind":{
},
"f:listKind":{
},
"f:plural":{
},
"f:singular":{
}
},
"f:conditions":{
"k:{""type"":""Established""}":{
".":{
},
"f:lastTransitionTime":{
},
"f:message":{
},
"f:reason":{
},
"f:status":{
},
"f:type":{
}
},
"k:{""type"":""NamesAccepted""}":{
".":{
},
"f:lastTransitionTime":{
},
"f:message":{
},
"f:reason":{
},
"f:status":{
},
"f:type":{
}
},
"k:{""type"":""NonStructuralSchema""}":{
".":{
},
"f:lastTransitionTime":{
},
"f:message":{
},
"f:reason":{
},
"f:status":{
},
"f:type":{
}
}
}
}
}
}
]
},
"spec":{
"group":"kubeless.io",
"version":"v1beta1",
"names":{
"plural":"functions",
"singular":"function",
"kind":"Function",
"listKind":"FunctionList"
},
"scope":"Namespaced",
"versions":[
{
"name":"v1beta1",
"served":true,
"storage":true
}
],
"conversion":{
"strategy":"None"
},
"preserveUnknownFields":true
},
"status":{
"conditions":[
{
"type":"NonStructuralSchema",
"status":"True",
"lastTransitionTime":"2021-07-11T19:36:54Z",
"reason":"Violations",
"message":"spec.preserveUnknownFields: Invalid value: true: must be false"
},
{
"type":"NamesAccepted",
"status":"True",
"lastTransitionTime":"2021-07-11T19:36:54Z",
"reason":"NoConflicts",
"message":"no conflicts found"
},
{
"type":"Established",
"status":"True",
"lastTransitionTime":"2021-07-11T19:36:55Z",
"reason":"InitialNamesAccepted",
"message":"the initial names have been accepted"
}
],
"acceptedNames":{
"plural":"functions",
"singular":"function",
"kind":"Function",
"listKind":"FunctionList"
},
"storedVersions":[
"v1beta1"
]
}
}I have tried to add But it causes: Which makes sense. Can someone please point me, where are the object which Another question - can Links: |
|
Trivial fix ( New yaml for cronjobtriggers.kubeless.ioapiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
name: cronjobtriggers.kubeless.io
spec:
group: kubeless.io
names:
kind: CronJobTrigger
plural: cronjobtriggers
singular: cronjobtrigger
scope: Namespaced
version: v1beta1
versions:
- name: v1beta1
served: true
storage: true
schema:
openAPIV3Schema:
type: object
properties:
spec:
type: object
properties:
schedule:
type: string
jobTemplate:
type: object
- name: v1
served: false
storage: false
schema:
openAPIV3Schema:
type: object
properties:
spec:
type: object
properties:
schedule:
type: string
jobTemplateA:
type: object
preserveUnknownFields: false |
|
@eduard93 @eduard93 @shubhomoy @iamshreeram the reason of the crashbackoff is cronjob-trigger-controller version v1.0.3 dependence kubeless version define as github.com/kubeless/kubeless v1.0.0-alpha.6, the kubeless v1.0.0-alpha.6 dependece client-go version was very low (k8s.io/client-go v5.0.0+incompatible), the decode interface not compatible the high version kubernetes crd resource. how to solve this problem？ rebuild the cronjob-trigger-controller: git clone https://github.com/kubeless/cronjob-trigger.git && cd cronjob-trigger, and the modify the go.mod, change the github.com/kubeless/kubeless v1.0.0-alpha.6 to github.com/kubeless/kubeless v1.0.8, the v1.0.8 is the version which you to use kubeless’s version , and the go mod tidy , rebuild the cronjob-trigger-controller image, that will be succedded. |
Did you manage to work kubeless with this modification on k8s > 1.18? I am trying to move our clusters to 1.22 |
Is this a BUG REPORT or FEATURE REQUEST?:
BUG
What happened:
Installed kubeless with below
What you expected to happen:
Kubeless Pods being created
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version):kubeless version): v1.0.7-dirtyPod description :
The text was updated successfully, but these errors were encountered: