Transmitting configuration data between containers running on different computer architectures via a sidecar container
A system can instantiate a first container and a sidecar container on a first node. The system can transmit configuration data from the first container to the sidecar container. The system can then initiate a migration of the sidecar container from the first node to a second node, where the second node has a different computer architecture than the first node. The second node can provide the configuration data from the sidecar container to a second container, for example after the migration is complete.
1. A non-transitory computer-readable medium comprising instructions executable by a processor for causing the processor to:
instantiate a first container and a sidecar container on a first node;
transmit configuration data from the first container to the sidecar container; and
initiate a migration of the sidecar container from the first node to a second node that has a different computer architecture than the first node, the second node being configured to provide the configuration data from the sidecar container to a second container.
2. The non-transitory computer-readable medium of claim 1 , wherein the first container and the second container are primary containers, and wherein the sidecar container is a secondary container.
3. The non-transitory computer-readable medium of claim 2 , wherein the second node is configured to, subsequent to a completion of the migration:
promote the sidecar container to primary status and shut down the second container, such that the sidecar container serves as a replacement for the second container.
4. The non-transitory computer-readable medium of claim 1 , wherein the sidecar container is configured to store a backup copy of the first container or the second container.
5. The non-transitory computer-readable medium of claim 1 , wherein the second node is adapted to configure the second container with the configuration data during runtime of the second container.
6. The non-transitory computer-readable medium of claim 1 , wherein the second node is configured to shut down the sidecar container subsequent to transferring the configuration data to the second container.
7. The non-transitory computer-readable medium of claim 1 , wherein the second node is configured to rebuild the second container based on the configuration data conveyed via the sidecar container.
8. A method comprising:
instantiating, by a processor, a first container and a sidecar container on a first node;
transmitting, by the processor, configuration data from the first container to the sidecar container; and
initiating, by the processor, a migration of the sidecar container from the first node to a second node that has a different computer architecture than the first node, the second node being configured to provide the configuration data from the sidecar container to a second container.
9. The method of claim 8 , wherein the first container and the second container are primary containers, and wherein the sidecar container is a secondary container.
10. The method of claim 9 , wherein the second node is configured to, subsequent to a completion of the migration:
promote the sidecar container to primary status and shut down the second container, such that the sidecar container serves as a replacement for the second container.
11. The method of claim 8 , wherein the sidecar container is configured to store a backup copy of the first container or the second container.
12. The method of claim 8 , wherein the second node configures the second container with the configuration data during runtime of the second container.
13. The method of claim 8 , wherein the second node is configured to shut down the sidecar container subsequent to transferring the configuration data to the second container.
14. The method of claim 8 , wherein the second node is configured to rebuild the second container based on the configuration data conveyed via the sidecar container.
15. A system comprising:
a processor; and
a memory including instructions executable by the processor for causing the processor to:
instantiate a first container and a sidecar container on a first node;
transmit configuration data from the first container to the sidecar container; and
initiate a migration of the sidecar container from the first node to a second node that has a different computer architecture than the first node, the second node being configured to provide the configuration data from the sidecar container to a second container subsequent to a completion of the migration.
16. The system of claim 15 , wherein the processor and memory are parts of the first node, the first node and the second node are included in a distributed computing environment, and the second node is configured to execute the second container.
17. The system of claim 15 , wherein the second node is configured to rebuild the second container based on the configuration data conveyed via the sidecar container.
18. The system of claim 15 , wherein the sidecar container is configured to store a backup copy of the first container or the second container.
19. The system of claim 15 , wherein the second container is adapted to configure the second container with the configuration data during a runtime of the second container.
20. The system of claim 15 , wherein the second node is configured to shut down the sidecar container subsequent to transferring the configuration data to the second container.