Preview environment

As explained in Effective Platform Engineering

A preview environment is a nonproduction environment in which a software change can be evaluated before release.

A preview environment is a nonproduction environment outside a development team’s usual path to production, where software changes can be evaluated with the team’s services present. section 6.3.3 section 2.2.1

It addresses a testing gap: platform teams need isolated environments for upgrades and refactoring, but testing without real customer services misses user-impacting failures. section 6.3.3

A useful preview design should:

• Provide a namespace or equivalent environment in a preview cluster outside the normal production path. section 6.3.3
• Let platform teams observe how customer services respond to platform changes without blocking ordinary development. section 6.3.3
• Move changes from preview toward nonproduction and production only after observation and testing. section 2.2.1
• Combine status checks, functional tests, and observation of developer impact. section 8.6 section 2.2.1

Payments team

Suppose the Payments team normally moves through development, QA, and staging. Deploying a control-plane change to preview exposes failures in its services without disrupting the team’s regular delivery flow. section 6.3.3

Figure 6.9 For users of the platform, an environment in the path-to-production is a Kubernetes namespace. There will be one or more namespaces in a preproduction cluster, or eventually multiple clusters, where development teams test their application before deploying to a production cluster. Something you may not have seen before is the preview environment in the similarly named preview cluster.

Use the architecture figure to compare ordinary Kubernetes namespaces in preproduction and production with the separate preview namespace and cluster. section 6.3.3

How Effective Platform Engineering covers it

How deep it goes

Explains the architectural rationale, namespace placement, release progression, testing, and observation, but stops short of implementation configuration.

Examples

Uses a Payments team, preview and preproduction clusters, namespaces, pipeline checks, functional tests, and developer-impact observation.

What it assumes

Assumes familiarity with software delivery environments, namespaces, platform users, and production paths; distinguishes preview from ordinary nonproduction testing.

What you can do after

Evaluate platform changes with real customer services while preserving the team’s normal development flow and observing early failures.

How it connects

Connects preview environments with Kubernetes namespaces, nonproduction environments, production environments, control-plane changes, pipelines, and monitoring.

liveBookmanning.com

Read Effective Platform Engineering on liveBook Get the book at manning.com

Related concepts

• pull requestuses · A pull request is a version-control proposal to integrate changes from one branch or repository into another, typically supporting review and discussion before merging.
• infrastructure as codeproduced by · Infrastructure as code is the practice of defining, provisioning, and managing computing infrastructure through machine-readable code or configuration rather than manual procedures.
• release candidateused by · A release candidate is a software version considered complete enough for final validation and possible release.
• productioncontrasts with · A production environment is the live operational setting in which software or other systems serve real users, workloads, or business processes.
• conformance testingused by · Conformance testing is the evaluation of an implementation, artifact, or process against specified standards, interfaces, contracts, or requirements.
• test environmentkind of · A test environment is a configured computing context, including relevant software, infrastructure, data, and settings, in which software is tested.

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.