Edge Deployment

Go to Terms and Definitions

An Edge Deployment is an Infrastructure Deployment that deploys one or more identified deployment subjects to an Edge Environment.

Deployment subjects may include:

• Infrastructure Resources
• Virtual Machines
• Kubernetes Clusters
• Containerized Workloads
• Platform Services
• Configuration
• Security controls
• Monitoring capabilities
• Operational data

An Edge Deployment may need to account for:

• Limited network bandwidth
• Intermittent connectivity
• Restricted external connectivity
• Limited computing capacity
• Limited storage capacity
• Local security controls
• Physical access constraints
• Local operational authority
• Dependency availability
• Local update and rollback procedures

An Edge Deployment differs from a cloud deployment:

• An Edge Deployment targets an Edge Environment
• A cloud deployment targets an Infrastructure Environment supplied through cloud capabilities

An Edge Deployment may also form part of a Hybrid-Cloud Deployment when related deployment subjects operate across cloud and Edge Environments.

An Edge Deployment does not necessarily imply disconnected or air-gapped operation.

infrastructure deployment that deploys one or more identified deployment subjects to an Edge Environment

Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

The applicable deployment specification should identify:

• The target Edge Environment
• The deployment subjects
• The applicable environment constraints
• Required dependencies
• Required configuration
• Applicable Acceptance Criteria
• Required deployment validation
• Required rollback behavior

The term does not prescribe a device class, edge platform, orchestration technology, provider, network architecture, or connectivity model.

Crucible performs an Edge Deployment by deploying a Containerized Workload, its configuration, and required Platform Services to an Edge Environment located within a remote industrial facility.