Protecting instances of resources of a container orchestration platform from unintentional deletion
A container orchestration platform manages a plurality of instances of resources including a first custom resource and a second custom resource. An API server of the container orchestration platform receives a request to delete an instance of the second custom resource; determines whether instance data associated with the instance of the second custom resource has a backreference identifying an instance of the first custom resource, the backreference indicating the instance of the first custom resource is dependent on the instance of the second custom resource; and in response to determining that the instance data has the backreference to the instance of the first custom resource, bypasses deletion of the instance of the second custom resource.
1. A method comprising:
receiving, by an API server of a container orchestration platform managing a plurality of instances of custom resources including a first custom resource and a second custom resource, a request to create an instance of the first custom resource;
creating, by a reconciler and for an instance of the second custom resource, instance data including a backreference identifying the instance of the first custom resource, the backreference indicating the instance of the first custom resource is dependent on the instance of the second custom resource; and
based on determining that the instance data has the backreference identifying the instance of the first custom resource, bypassing deletion of the instance of the second custom resource.
2. The method of claim 1 , further comprising:
based on determining that the instance data has the backreference identifying the instance of the first custom resource, outputting an indication of an error for the request to delete the instance of the second customer resource.
3. The method of claim 1 , wherein based on determining that the instance data does not have a backreference identifying any custom resource, deleting the instance of the second custom resource.
4. The method of claim 1 , further comprising inserting, into the backreference, a label prefix distinguishing the backreference from other types of references and an identifier of the instance of the first custom resource.
5. The method of claim 4 , further comprising:
inserting a name into the backreference; and
hashing the identifier of the instance of the first custom resource to create a hash value of the identifier, wherein inserting the identifier of the instance of the first custom resource into the backreference comprises inserting the hash value into the backreference.
6. The method of claim 4 , wherein determining that the instance data has the backreference identifying the instance of the first custom resource comprises determining whether the instance data includes the label prefix.
7. The method of claim 1 , wherein the API server comprises an extension API server for handling requests identifying the second custom resource.
8. The method of claim 1 , wherein determining that the instance data has the backreference identifying the instance of the first custom resource comprises determining, by a webhook associated with a validating admission block of the API server, that the instance data has the backreference identifying the instance of the first custom resource.
9. The method of claim 1 , wherein the backreference of the instance of the second custom resource identifies the instance of the first custom resource to indicate dependence by the first custom resource on the second customer resource.
10. The method of claim 1 , wherein the container orchestration platform comprises Kubernetes.
11. A container orchestration system configured to manage a plurality of instances of resources including a first custom resource and a second custom resource, the container orchestration system comprising:
an API server comprising processing circuitry configured to:
receive a request to create an instance of the first custom resource;
create, for an instance of the second custom resource, instance data including a backreference identifying the instance of the first custom resource, the backreference indicating the instance of the first custom resource is dependent on the instance of the second custom resource; and
based on a determination that the instance data has the backreference identifying the instance of the first custom resource, bypassing deletion of the instance of the second custom resource.
12. The container orchestration system of claim 11 , wherein the API server is further configured to, based on a determination that the instance data has the backreference identifying the instance of the first custom resource, output an indication of an error for the request to delete the instance of the second customer resource.
13. The container orchestration system of claim 11 , wherein the API server is further configured to, based on a determination that the instance data does not have a backreference identifying any custom resource, delete the instance of the second custom resource.
14. The container orchestration system of claim 11 , wherein the processing circuitry is further configured to insert, into the backreference, a label prefix distinguishing the backreference from other types of references and an identifier of the instance of the first custom resource.
15. The container orchestration system of claim 14 , wherein the processing circuitry is further configured to:
insert a name into the backreference; and
hash the identifier of the instance of the first custom resource to create a hash value of the identifier, wherein to insert the identifier of the instance of the first custom resource into the backreference comprises to insert the hash value into the backreference.
16. The container orchestration system of claim 14 , wherein to determine that the instance data has the backreference identifying the instance of the first custom resource the processing circuitry is further configured to determine whether the instance data includes the label prefix.
17. The container orchestration system of claim 11 , wherein the API server comprises an extension API server for handling requests identifying the second custom resource.
18. A non-transitory computer-readable storage medium having instructions stored thereon that cause one or more processors of a container orchestration platform managing a plurality of instances of resources including a first custom resource and a second custom resource to perform operations comprising:
receive a request to create an instance of the first custom resource;
create, for an instance of the second custom resource, instance data including a backreference identifying the instance of the first custom resource, the backreference indicating the instance of the first custom resource is dependent on the instance of the second custom resource; and
based on a determination that the instance data has the backreference identifying the instance of the first custom resource, bypass deletion of the instance of the second custom resource.