How does the "garbage collection" of Kubernetes objects work with respect to "ownerReferences"?
Correct! Well done.
Incorrect.
The correct answer is B) Objects can declare an "ownerReference" pointing to another object (their owner); when the owner is deleted, the garbage collector automatically deletes dependent objects too (cascading deletion), unless an "orphan" deletion policy is specified
Correct Answer
Objects can declare an "ownerReference" pointing to another object (their owner); when the owner is deleted, the garbage collector automatically deletes dependent objects too (cascading deletion), unless an "orphan" deletion policy is specified
ownerReferences establish parent-child relationships (e.g. a ReplicaSet owns its Pods); by default, deleting the owner cascades to delete dependents, though "kubectl delete --cascade=orphan" can leave dependents behind.