Time Machine for Containers

Time Travel your Containers Without Modifying your Container Images

Time Machine for Containers

Time Machine for Containers (TMCON) enables you to time travel your containerized applications into the future or the past with variable speed capability, for any functional tests on your date and time sensitive application logic (such as month-end/quarter-end/year-end processing, billing cycles, workflow, regulatory go live and policy life cycles).

You can time travel desired target Kubernetes/OpenShift pods/deployments by simply creating a TMCON deployment in the same namespace where your target pods are. After deploying TMCON, the only thing you need to do is to configure your application deployment(s) in three easy steps and create a virtual clock; in less than five minutes you will be time traveling your application with ease.

Benefits & Features

Saves hardware and software costs and boosts engineering team productivity to ensure large scale software projects finish on time and under budget.

No changes are made to the existing container/app images you are using. Simply add Time Machine pod/deployment to the namespace where the target pods/deployments are running.
Time Machine pod is running under non-root user, which is in line with default security restrictions in Kubernetes/OpenShift, and will adhere to any security constraints of an enterprise environment.
Using Time Machine Sync Server (see TM Sync Server Data Sheet), you can broadcast virtual clocks outside the Kubernetes/OpenShift cluster, and synchronously time travel containerized and non-containerized targets.

Container Platforms

Docker, Kubernetes, Red Hat OpenShift, Azure Kubernetes Service (AKS), Google Kubernetes Engine (GKE), Amazon Elastic Kubernetes Service (Amazon EKS), and more.



Visit Time Machine Container in the Red Hat Ecosystem Catalog:

Visit Time Machine Operator on Red Hat Marketplace.