Create an appsodyapplication and enable knative service spec.createKnativeService: true
Observe there is a ksvc for the appsodyapplication oc get ksvc
Delete the ksvc oc delete ksvc name
What did you expect to see?
Expect that the ksvc would be recreated by watch / reconcile
What did you see instead?
crickets
however, deleting the appsody-operator causes a re-reconcile which will re-create the ksvc
Environment
Appsody CLI version: 0.4.10
Appsody Stack: nodejs
Kubernetes version information: OCP 4.2
Client Version: v4.3.0
Server Version: 4.2.0
Kubernetes Version: v1.14.6+2e5ed54
Bug Report
What did you do?
Create an appsodyapplication and enable knative service
spec.createKnativeService: true
Observe there is a ksvc for the appsodyapplicationoc get ksvc
Delete the ksvcoc delete ksvc name
What did you expect to see?
Expect that the ksvc would be recreated by watch / reconcile
What did you see instead?
crickets
however, deleting the appsody-operator causes a re-reconcile which will re-create the ksvc
Environment
Appsody CLI version: 0.4.10
Appsody Stack: nodejs
Kubernetes version information: OCP 4.2
Client Version: v4.3.0 Server Version: 4.2.0 Kubernetes Version: v1.14.6+2e5ed54
Possible solution
Watch for owned ksvc object, example https://github.com/kabanero-io/kabanero-operator/blob/master/pkg/controller/collection/collection_controller.go#L80
Additional context
Add any other context about the problem here.