Automatic dependency configuration for managed services
A container-orchestration system reads specification data associated with a third-party resource used by a managed resource. Based on the specification data the system retrieves resource configuration data of the third-party resource and updates a dependency definition with the resource configuration data. The dependency definition is associated with the managed resource and the third-party resource. The system provides the dependency definition to the managed resource.
1. A method, comprising:
identifying, at a container-orchestration system, a configuration change of a third-party resource used by a managed resource of the container-orchestration system;
reading, at the container-orchestration system and in response to identifying the change of the configuration of the third-party resource, specification data included in a dependency definition associated with the third-party resource used by the managed resource;
retrieving resource configuration data of the third-party resource based on the specification data, the resource configuration data including a first environment variable;
updating, by a processing device, status data included in the dependency definition with the resource configuration data including the first environment variable, wherein the dependency definition is associated with the managed resource and the third-party resource;
transforming the first environment variable into a second environment variable for the container-orchestration system of the managed resource; and
providing the dependency definition and the second environment variable to the managed resource of the container-orchestration system.
2. The method of claim 1 , wherein the updating the dependency definition further comprises:
translating the resource configuration data into container-orchestration objects associated with the managed resource and the third-party resource, wherein the container-orchestration objects are readable by one or more managed resources of the container-orchestration system.
3. The method of claim 2 , wherein the container-orchestration objects comprise configuration data describing the third-party resource and an application programming interface (API).
4. The method of claim 2 , wherein the providing of at least a portion of the dependency definition to the managed resource comprises:
generating a configuration file associated with the managed resource, wherein the configuration file comprises the container-orchestration objects.
5. The method of claim 1 , further comprising deploying at least one container comprising the dependency definition associated with connecting to the third-party resource.
6. The method of claim 1 , wherein the providing at least a portion of the dependency definition to a managed resource causes the managed resource to mount one or more volumes associated with the third-party resource.
7. The method of claim 1 , wherein identifying the configuration change of the third-party resources is based on receiving a notification of a configuration change of the third-party resource.
8. The method of claim 1 , further comprising connecting to the third-party resource on a system external to the container-orchestration system based on the dependency definition.
9. A system, comprising:
a memory; and
a processing device, operatively coupled to the memory, to:
identify, at a container-orchestration system, a configuration change of a third-party resource used by a managed resource of the container-orchestration system;
read, in response to identification of the configuration change, specification data included in a dependency definition associated with the third-party resource used by the managed resource;
retrieve resource configuration data of the third-party resource based on the specification data, the resource configuration data including a first environment variable;
update status data included in the dependency definition with the resource configuration data including the first environment variable, wherein the dependency definition is associated with the managed resource and the third-party resource;
transform the first environment variable into a second environment variable for the container-orchestration system of the managed resource; and
provide the dependency definition and the second environment variable to the managed resource.
10. The system of claim 9 , wherein to update the dependency definition, the processing device is further to:
translate the resource configuration data into container-orchestration objects associated with the managed resource and the third-party resource, wherein the container-orchestration objects are readable by one or more managed resources of the container-orchestration system.
11. The system of claim 10 , wherein the container-orchestration objects comprise configuration data describing the third-party resource and an application programming interface (API).
12. The system of claim 10 , wherein to provide at least a portion of the dependency definition to the managed resource, the processing device is further to:
generate a configuration file associated with the managed resource, wherein the configuration file comprises the container-orchestration objects.
13. The system of claim 9 , wherein the processing device is further to deploy at least one container comprising the dependency definition associated with connecting to the third-party resource.
14. The system of claim 9 , wherein the processing device is further to provide at least a portion of the dependency definition to a managed resource causes the managed resource to mount one or more volumes associated with the third-party resource.
15. The system of claim 9 , wherein the processing device is further to identify the configuration change of the third-party resource based on receipt of a notification of the configuration change of the third-party resource.
16. The system of claim 9 , wherein the processing device is further to connect to the third-party resource on a system external to the container-orchestration system based on the dependency definition.
17. A non-transitory computer-readable storage medium including instructions that, when executed by a processing device, cause the processing device to:
identify, at a container-orchestration system, a configuration change of a third-party resource used by a managed resource of the container-orchestration system;
read, in response to identification of the configuration change, specification data included in a dependency definition associated with the third-party resource used by the managed resource;
retrieve resource configuration data of the third-party resource based on the specification data, the resource configuration data including a first environment variable;
update, by the processing device, status data included in the dependency definition with the resource configuration data including the first environment variable, wherein the dependency definition is associated with the managed resource and the third-party resource;
transform the first environment variable into a second environment variable for the container-orchestration system of the managed resource; and
provide the dependency definition and the second environment variable to the managed resource.
18. The non-transitory computer-readable storage medium of claim 17 , wherein the processing device is further to:
translate the resource configuration data into container-orchestration objects associated with the managed resource and the third-party resource, wherein the container-orchestration objects are readable by one or more managed resources.
19. The non-transitory computer-readable storage medium of claim 18 , wherein the processing device is further to:
generate a configuration file associated with the managed resource, wherein the configuration file comprises the container-orchestration objects.
20. The non-transitory computer-readable storage medium of claim 17 , wherein the processing device is further to:
deploy at least one container comprising the dependency definition associated with connecting to the third-party resource.