Operational consideration

Running infrastructure on Vagrant is not generally intended for production use. More frequently, localized development and testing may be achieved using k3d and other containerized k8s environments.

Production grade

However it is possible and useful to develop and test applications that are already running on near to production grade infrastructure.

We can test and prove deployments to be able to

• be tested in a safer environment
• able to cope with service interruptions due to a failing node
• work with ingress

Single containerized k8s stacks lack their fully virtualized counterparts physical attributes such as CPU, memory, storage and networks.

Configuration

From infctl’s pont of view, it creates for us a config.json file at run time if not already present that contains :

{
  "log_format": "<full|basic|none>",
  "deployment_file": "<path as specifed to this pipeline file>",
  "deployment_type": "<development|pre-production|production where development is the default>",
  "deployment_mode": "json"
}

We would logically change deployment_type to be pre-production for pipelines that have reached this stage.

It is then obvious that our code has reached a stage that has been tested close to production.