Closed yvz5 closed 4 years ago
Hi @yvz5, thanks for reporting the issue. To check if it's just a manifest issue, can you execute this?
curl -L https://github.com/kubeless/kafka-trigger/releases/download/v1.0.2/kafka-zookeeper-v1.0.2.yaml | sed 's/apiVersion: apps\/v1beta1/apiVersion: apps\/v1/g' | kubectl apply -f -
We can just fix the manifest if that's the case with the above.
I did try it but statefulset needs selector property so it doesnt work. You also need to adapt the new statefulset.
You must set the .spec.selector field of a StatefulSet to match the labels of its .spec.template.metadata.labels. Prior to Kubernetes 1.8, the .spec.selector field was defaulted when omitted. In 1.8 and later versions, failing to specify a matching Pod Selector will result in a validation error during StatefulSet creation.
Thanks for checking, I have also fixed that issue and uploaded the new manifest to the release page so you should be able to install those as usual. Let me know if you find more issues.
Is this a BUG REPORT or FEATURE REQUEST?: BUG
What happened: Tried to create the resources using the release yaml and got errors:
What you expected to happen: That the deployment, StatefulSet created.
How to reproduce it (as minimally and precisely as possible): use latest kubernetes binaries or minikube and kubectl create kafka trigger
Anything else we need to know?: maybe updating the yaml files would solve this. Check this : https://stackoverflow.com/a/58482194
Environment:
kubectl version
): Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.0",BuildDate:"2019-12-07T21:20:10Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"windows/amd64"}kubeless version
): kubeless is not installed yet