Testing an upgrade to a microservice in a production environment

A non-transitory machine readable medium storing instructions executable by a processing resource of a computer system, the non-transitory machine readable medium comprising instructions to:

• load a first domain specific language (DSL) program into a user space kernel that wraps an active container of a production environment of a container orchestration system within which a first version of the microservice is running, wherein the first version of the microservice represents a known working version of the microservice;
• intercept production interactions with the first version of the microservice;
• persist state information associated with the production interactions;
• load a second DSL program into a user space kernel that wraps a passive container of the production environment within which a second version of the microservice is running, wherein the second version of the microservice represents the upgrade to the microservice;
• isolate the second version of the microservice from other resources within the production environment by using the persisted state information as a source of data for all requests issued by the second version of the microservice;
• and
• compare outputs of the second version of the microservice to outputs of the first version of the microservice by replaying the production interactions to the second version of the microservice.

A system comprising:

• a processing resource;
• and
• a non-transitory computer-readable medium, coupled to the processing resource, having stored therein instructions that when executed by the processing resource cause the processing resource to:
• load a first domain specific language (DSL) program into a user space kernel that wraps an active container of a production environment of a container orchestration system within which a first version of the microservice is running, wherein the first version of the microservice represents a known working version of the microservice;
• intercept production interactions with the first version of the microservice;
• persist state information associated with the production interactions;
• load a second DSL program into a user space kernel that wraps a passive container of the production environment within which a second version of the microservice is running, wherein the second version of the microservice represents the upgrade to the microservice;
• isolate the second version of the microservice from other resources within the production environment by using the persisted state information as a source of data for all requests issued by the second version of the microservice;
• and
• compare outputs of the second version of the microservice to outputs of the first version of the microservice by replaying the production interactions to the second version of the microservice.