Forge Container services is now in Preview, and therefore fully supported. However, it remains under active development and may be subject to shorter deprecation windows. Preview features are suitable for early adopters in production environments.
We release preview features so partners and developers can study, test, and integrate them prior to General Availability (GA). For more details, see Forge EAP, Preview, and GA.
The implementation of Forge Container services varies slightly from how traditional containerised services work. The following glossary helps clarify these subtle differences:
| Term | Definition |
|---|---|
| Container | A portable, self-contained unit of software. This unit contains all of the dependencies and configurations necessary to launch an isolated process used for providing capabilities for a containerised service. Containers are packaged in images, from which they can also be deployed.
In Forge, containers are defined in the manifest through the NOTE: During Preview, you can define up to 3 services with one container, per app. Refer to the Forge Container services roadmap for a full list of Preview limitations. |
| Container instance | The resulting process that runs when you deploy a container. A service instance is made up of one or more container instances. |
| Containerised service | A logical grouping of one or more containers that provide a specific capability. In Forge, a containerised service is defined in the manifest through the top-level service property; each service contains one or more container definitions.
Containerised services handle inbound and outbound requests via REST API. NOTE: During Preview, you can define up to 3 services with one container, per appp. Refer to the Forge Container services roadmap for a full list of Preview limitations. |
| Forge Container services | A set of tools and capabilities provided by the Forge platform for packaging, deploying, and managing containerised services for apps. Forge Container services let you run services from container images directly on Forge infrastructure. |
| Image | A read-only, immutable, and executable package containing all the code required to deploy a container. An image contains all of the code’s dependencies, including its runtime, tools, libraries, and settings. |
| Image tag | Image versions are identified by tag; in Forge, these tags are immutable. Image tags like latest won't work; we recommend using environment variables on your tagging scheme. |
| Registry | A database of container images and their different versions. In Forge, each container instance is launched from images stored on the Forge Container services registry. The Forge Container services registry is forge-registry.services.atlassian.com. |
| Repository | A dedicated space within the Forge Container services registry for storing different versions of a container’s image. Each container will have its own repository, and Forge apps can deploy specific image versions (identified by tag).Each container repository name follows this structure:forge-registry.services.atlassian.com/forge/${APP_ID}/${CONTAINER_KEY} |
| Service instance | The resulting hosted service that runs when you deploy a containerised service. A service instance is made up of one or more running container instances.
NOTE: During Preview, you can define up to 3 services with one container, per app. Refer to the Forge Container services roadmap for a full list of Preview limitations. |
Rate this page: