Open mmisztal1980 opened 3 months ago
Following up here it looks like the default installation expects Istio and when it is not installed the operator will fail with Ready=False saying the Istio resources are not present.
This halts the installation of other manifests and leaves serving in a weird state. eg. in the above example the mutating & validating webhooks are not installed. This allowed the user to create a Knative Service and it reconciled all then when it created the PodAutoscaler it didn't default a annotation required to select which autoscaler to use.
Ideally it would be good to try to apply all the resources in the manifest and then report all errors the operator installation encounters.
But since the operator did report the failure I think we could just simply document checking the installation in the docs.
I'll leave this issue open for @houshengbo close out and make a docs issue.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen
. Mark the issue as
fresh by adding the comment /remove-lifecycle stale
.
In what area(s)?
What version of Knative?
Expected Behavior
Using
kn service create 'hello-example' --image ghcr.io/knative/helloworld-go:latest --env TARGET="First"
I'm expecting to deploy a hello-wolrd example to start playing with the knative.Actual Behavior
The process starts but doesn't complete. The pod is successfully scheduled in the
default
namespace and is ready, however the kn service is notSteps to Reproduce the Problem
docker-desktop
clusteroperator-sdk
using instructions found hereoperator-sdk olm install
kubectl create -f https://operatorhub.io/install/knative-operator.yaml
or apply this manifest:kn service create 'hello-example' --image ghcr.io/knative/helloworld-go:latest --env TARGET="First"
Any addiitional details and investigation so far can be found on CNCF slack here