Knative: Operator’s Handbook

Life of a KService (control plane)

When you create a KService, it creates:

Note: When we say “creates” above, we don't mean objects create other objects themselves. It's done asynchronously, by a controller watching these resources.

When you update an existing KService, if you change its spec.template section, a new Revision will be created. If you change its spec.traffic section, its Route will be updated.

When you delete a KService, Kubernetes will use finalizers and ownerReferences on these objects to garbage collect the sub-resources.

These Knative APIs are explained here.

You can also see it for yourself by exploring Kubernetes object hierarchy.