Add a Container as an Edge App Type

Introduction

This article describes how to add a container as an edge application type. All the types are described in the Manage an Edge Application article. This is a series of articles. You will likely follow them in this order.

1. Edge Application Overview
2. Manage an Edge App Image
3. Manage an Edge Application
   • Add a Module as an Edge App Type
   • Add a Container as an Edge App Type - You are here!
   • Add a Virtual Machine as an Edge App Type
4. Deploy an Application Instance

Prerequisites

• You have the SysManager role in your enterprise.
• Ensure the application details are stored in a place the edge node can access. Check Data Storesfor details.
• An Edge App Image is required.

Configure the identity

1. Log in to the ZEDEDA GUI.
2. Hover over Marketplace on the left side nav and click on Edge Apps.
3. Click on the icon + to create a new edge app.
4. Select Container as the Edge App Type.
5. Continue on to the identity details.

Identity details

1. Fill in the following. 
   • Edge App Logo: Upload a logo.
   • Name: This value can't be changed later.
   • Title: This value is for flexibility. You can change it at any time. 
   • Description: You can use this to help other admins understand the purpose of the app or any important details about the app.
   • Category: Select the category that best describes the app. If no category describes the app, you can type one of your own and that category is created.
   • Version: Provide the version of your edge application.
2. Select a deployment type. 
   • Standalone: Runs the application independently on the edge device without relying on any external cloud services.
   • Azure Runtime: Indicates that the application is designed to interact with Azure services.
   • K3S: Indicates that the application is designed for deploying the K3S runtime, for automated deployment of K3S clusters across selected nodes. 
   • VCE: Runs applications in a virtualized environment on edge devices that may be part of a larger cloud-native architecture.
   • TKG Attach: Indicates that the application is used to deploy a single-node Tanzu Kubernetes cluster, where the hosted workload runs alongside the control plane infrastructure on a single application instance.
   • Docker Runtime: TBD
3. Enable VNC Connection: A graphical desktop sharing system to remotely control the app interface for the purposes of remote management, development, troubleshooting, and more.
4. Add a License: Helps users understand the terms under which they can use, modify, or distribute the application. It can also affect how the application interacts with other components in the ZEDEDA ecosystem.
5. Click Next.