MANAGING DEPLOYMENT OF CUSTOM RESOURCES IN A CONTAINER ORCHESTRATION SYSTEM

1 . A method of managing a custom resource in a container orchestration (CO) system, the method comprising:

receiving, from a manager at a management cluster of the CO system, an intent identifier, the management cluster including a controller configured to manage the custom resource, the management cluster storing the intent identifier in a database;

receiving, from the manager at the management cluster, a request that updates state of the custom resource;

determining, at the management cluster, a match between an intent identifier in the request and the intent identifier stored in the database; and

executing, by the controller of the management cluster, a management process for the custom resource in the CO system in response to the match and the request.

2 . The method of claim 1 , wherein the intent identifier stored in the database comprises a first intent identifier, the request comprises a first request, and the management process comprises a first management process, the method further comprising:

receiving, from the manager at the management cluster, a second intent identifier different from the first intent identifier;

replacing, by the management cluster, the first intent identifier with the second intent identifier in the database;

receiving, from the manager at the management cluster, a second request that updates the state of the custom resource;

determining, at the management cluster, another match between an intent identifier in the second request and the second intent identifier stored in the database; and

executing, by the controller of the management cluster, a second management process for the custom resource in the CO system in response to the other match and the second request.

3 . The method of claim 2 , wherein the management cluster stops the first management process in response to replacement of the first intent identifier with the second intent identifier.

4 . The method of claim 1 , wherein the manager executes in a datacenter and the management cluster executes in a site remote from the datacenter.

5 . The method of claim 4 , wherein the custom resource comprises a workload cluster configured to execute at the site or another site remote from the datacenter.

6 . The method of claim 1 , wherein the request comprises a first request, the method further comprising:

receiving, from the manager at the management cluster, a second request that updates the state of the custom resource;

determining, by the management cluster, that a difference between an intent identifier in the second request and the intent identifier stored in the database; and

dropping, by the management cluster, the second request in response to the difference.

7 . The method of claim 1 , wherein the custom resource comprises a workload cluster, wherein the management process comprises deployment of the workload cluster, wherein the CO system comprises a data center and a plurality of sites, the management cluster disposed in the data center, the workload cluster disposed in the plurality of sites, the workload cluster executing containerized network functions (CNFs).

8 . A non-transitory computer readable medium comprising instructions to be executed in a computing device to cause the computing device to carry out a method of managing a custom resource in a container orchestration (CO) system, the method comprising:

receiving, from a manager at a management cluster of the CO system, an intent identifier, the management cluster including a controller configured to manage the custom resource, the management cluster storing the intent identifier in a database;

receiving, from the manager at the management cluster, a request that updates state of the custom resource;

determining, at the management cluster, a match between an intent identifier in the request and the intent identifier stored in the database; and

executing, by the controller of the management cluster, a management process for the custom resource in the CO system in response to the match and the request.

9 . The non-transitory computer readable medium of claim 8 , wherein the intent identifier stored in the database comprises a first intent identifier, the request comprises a first request, and the management process comprises a first management process, the method further comprising:

receiving, from the manager at the management cluster, a second intent identifier different from the first intent identifier;

replacing, by the management cluster, the first intent identifier with the second intent identifier in the database;

receiving, from the manager at the management cluster, a second request that updates the state of the custom resource;

determining, at the management cluster, another match between an intent identifier in the second request and the second intent identifier stored in the database; and

executing, by the controller of the management cluster, a second management process for the custom resource in the CO system in response to the other match and the second request.

10 . The non-transitory computer readable medium of claim 9 , wherein the management cluster stops the first management process in response to replacement of the first intent identifier with the second intent identifier.

11 . The non-transitory computer readable medium of claim 8 , wherein the manager executes in a datacenter and the management cluster executes in a site remote from the datacenter.

12 . The non-transitory computer readable medium of claim 11 , wherein the custom resource comprises a workload cluster configured to execute at the site or another site remote from the datacenter.

13 . The non-transitory computer readable medium of claim 8 , wherein the request comprises a first request, the method further comprising:

receiving, from the manager at the management cluster, a second request that updates the state of the custom resource;

determining, by the management cluster, that a difference between an intent identifier in the second request and the intent identifier stored in the database; and

dropping, by the management cluster, the second request in response to the difference.

14 . The non-transitory computer readable medium of claim 8 , wherein the custom resource comprises a workload cluster, and wherein the management process comprises deployment of the workload cluster.

15 . A computer system, comprising:

a hardware platform;

software, executing on the hardware platform, configured to:

receive, from a manager, an intent identifier, the software including a controller configured to manage a custom resource of a container orchestration (CO) system, the software storing the intent identifier in a database;

receive, from the manager, a request that updates state of the custom resource;

determine a match between an intent identifier in the request and the intent identifier stored in the database; and

execute, by the controller, a management process for the custom resource in the CO system in response to the match and the request.

16 . The computer system of claim 15 , wherein the intent identifier stored in the database comprises a first intent identifier, the request comprises a first request, and the management process comprises a first management process, and wherein the software is configured to:

receive, from the manager, a second intent identifier different from the first intent identifier;

replace the first intent identifier with the second intent identifier in the database;

receive, from the manager, a second request that updates the state of the custom resource;

determine another match between an intent identifier in the second request and the second intent identifier stored in the database; and

execute, by the controller, a second management process for the custom resource in the CO system in response to the other match and the second request.

17 . The computer system of claim 16 , wherein the software stops the first management process in response to replacement of the first intent identifier with the second intent identifier.

18 . The computer system of claim 15 , wherein the manager executes in a datacenter and the software executes in a site remote from the datacenter.

19 . The computer system of claim 18 , wherein the custom resource comprises a workload cluster configured to execute at the site or another site remote from the datacenter.

20 . The computer system of claim 15 , wherein the request comprises a first request, and wherein the software is configured to:

receive, from the manager, a second request that updates the state of the custom resource;

determine that a difference between an intent identifier in the second request and the intent identifier stored in the database; and

drop the second request in response to the difference.