Method and system for initial secret delivery for scalable and restart-able collocated containers with shared resources

1. A computer implemented method for secure initial secret delivery for collocated containers with shared resources, comprising:

receiving, by an identity and authentication sidecar, an application type identifier and a token to access a secrets management service, wherein the identity and authentication sidecar is a container in a plurality of collocated containers with shared resources;

executing a container creation code hook on an application container, wherein the application container is a container in a plurality of collocated containers with shared resources;

requesting, by the container creation code hook, a creation of an initial secret;

continuously polling, by the identity and authentication sidecar, an in-memory volume between the identity and authentication sidecar and the application container to determine whether there exists a request for creating the initial secret;

requesting validation of the request for the creation of the initial secret when a request for creating the initial secret is found;

requesting, by the identity and authentication sidecar, an identity for the collocated containers using the application type identifier and the access token when the request for the creation of the initial secret is determined to be valid;

receiving, by the identity and authentication sidecar, a unique identity for the collocated containers with shared resources based on the application type identifier;

requesting validation of the unique identity for the plurality of collocated containers with shared resources;

requesting, by the identity and authentication sidecar, the initial secret for the application container using the validated unique identity;

starting an application instance in the application container; and

retrieving other secrets for the application instance using the initial secret;

wherein the container creation code hook is executed after the application container is created and wherein the container creation code hook sends a request for creating the initial secret to the in-memory volume or to a named pipe; and

wherein if the in-memory volume is a named pipe, then the request is a message and if the in-memory volume is not a named pipe, the request is a file.

2. The method of claim 1 , wherein the plurality of collocated containers with shared resources were created asynchronously.

3. The method of claim 1 , wherein the identity and authentication sidecar is isolated from the application container.

4. The method of claim 1 , further comprising:

mounting a sidecar in-memory volume to the identity and authentication sidecar; and

mounting the application type identifier and the access token to the sidecar in-memory volume.

5. The method of claim 1 , further comprising deleting the request for the initial secret after the request is validated.

6. The method of claim 1 , wherein validating the request for creating the initial secret comprises performing a readiness check on the application instance, wherein the request is determined to be invalid if the application instance is already started.

7. The method of claim 6 , further comprising writing the initial secret to the in-memory volume between the identity and authentication sidecar and the application container.

8. The method of claim 7 , wherein the other secrets are retrieved by an externalized configuration server from the secrets management service.

9. The method of claim 8 , further comprising deleting the initial secret.

10. A system for secure initial secret delivery for collocated containers with shared resources between devices comprises:

a plurality of collocated containers with shared resources, wherein the plurality of collocated containers comprises:

an identity and authentication sidecar wherein the identity and authentication sidecar securely obtains the identity of the collocated containers from a secrets management service, and securely obtains and delivers the initial secret from the secrets management service to an application instance in an application container;

an application container where the application instance is executed;

a sidecar in-memory volume; and

an in-memory volume between the identity and authentication sidecar and the application container;

a container orchestration and management system comprising:

a) at least one processor;

b) at least one input device; and

c) at least one storage device storing processor-executable instructions which, when executed by the at least one processor, perform a method including:

setting an application type identifier and a token for accessing a secrets management service;

creating the plurality of collocated containers with shared resources, wherein creating comprises:

starting an identity and authentication sidecar; and

starting an application container; and

a secrets management service comprising:

a) at least one processor;

b) at least one input device; and

c) at least one storage device storing processor-executable instructions which, when executed by the at least one processor, perform a method including:

generating just-in-time, a unique run-time identity for a plurality of collocated containers with shared resources;

validating the unique identity for the plurality of collocated containers with shared resources;

just-in-time generating and delivering an initial secret for the application container; and

managing one or more application secrets for the application instance;

wherein the application container executes a container creation code hook that requests a creation of an initial secret;

wherein the container creation code book is executed after the application container is created and wherein the container creation code hook sends a request for creating the initial secret to the in-memory volume or to a named pipes; and

wherein if the in-memory volume is a named pipe, then the request is a message and if the in-memory volume is not a named pipe, then the request is a file.

11. The system of claim 10 , wherein the container orchestration and management system creates the plurality of collocated containers with shared resources asynchronously.

12. The system of claim 10 , wherein creating the plurality of collocated containers with shared resources by the container orchestration and management system further comprises:

mounting a sidecar in-memory volume to the identity and authentication sidecar; and

mounting the application type identifier and the access token to the sidecar in-memory volume.

13. The system of claim 10 , wherein the identity and authentication sidecar continuously polls the in-memory volume between the identity and authentication sidecar and the application container to determine if there is a request for creating the initial secret.

14. The system of claim 10 , wherein the identity and authentication sidecar requests validation of the request for the creation of the initial secret.

15. The system of claim 10 , wherein the request for the initial secret is deleted after the request is validated.

16. The system of claim 10 , wherein validating the request for creating the initial secret comprises performing a readiness check on the application instance, wherein the request is determined to be invalid if the application instance is already started.

17. The system of claim 16 , wherein the identity and authentication sidecar writes the initial secret to the in-memory volume between the identity and authentication sidecar and the application container.

18. The system of claim 17 , further comprising an externalized configuration server for providing a configuration for the application container during bootstrapping and retrieving other secrets from the secrets management service.

19. The system of claim 18 , further comprising deleting the initial secret after the other secrets are retrieved.