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 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. 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 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.