Open treblereel opened 1 week ago
+1 most probably we should add something like, during or right after cluster setup:
// Install eventing
kubectl apply -f https://github.com/knative/eventing/releases/download/knative-v1.15.1/eventing-crds.yaml
kubectl apply -f https://github.com/knative/eventing/releases/download/knative-v1.15.1/eventing-core.yaml
// Install serving
kubectl apply -f https://github.com/knative/serving/releases/download/knative-v1.15.2/serving-crds.yaml
kubectl apply -f https://github.com/knative/serving/releases/download/knative-v1.15.2/serving-core.yaml
We should not enforce Knative installation.
@treblereel as a workaround you can run:
make deploy-knative
Before running the e2e tests locally.
Describe the bug
It looks like starting
e91495
, e2e are broken, possible because of missed crds:Expected behavior
hack/local/run-e2e.sh passed
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Golang version
1.21.9
Operator-sdk version
No response
SonataFlow Operator version or git rev
No response
Additional information
No response