In this section
Platform profiles — Build, Run, and Custom
The problem this solves
Development environments and application deployment targets need different services. SmoothGlue profiles select default applications for these roles. Explicit application settings can override those defaults.
How templates work
The SmoothGlue configuration chart uses clusterType to select a profile. Zarf passes
the corresponding CLUSTER_TYPE deployment input to the chart. The chart defaults to
run, so set the intended profile explicitly. A package filename does not establish
all application or identity settings.
Package contents and enabled applications are separate choices. Enabling an application requires its content to be available in the selected package, along with the external services and configuration that the application needs.
The three profiles
Build
Use the Build profile for development and collaboration services.
GitLab, GitLab Runner, Keycloak, Mattermost, and SonarQube are enabled by their Build profile defaults. The profile also uses common platform services for networking, observability, and security.
Argo CD is not enabled by the Build profile default. Enable optional applications explicitly when the deployment requires them and the selected package provides them.
Run
Use the Run profile for an application deployment target.
Argo CD is enabled by the Run profile default. GitLab, Keycloak, Mattermost, and SonarQube are not enabled by that profile's defaults. Configure access to any external services that the deployment uses.
Installing Keycloak and enabling AutoSSO are separate settings. A Run environment that uses an external Keycloak instance also needs the corresponding connectivity, credentials, hostname, and certificate trust.
Custom
Use the Custom profile when you need explicit application selection on top of the common defaults. Custom does not mean that every application starts disabled.
Edge environments
An Edge deployment describes the site's operating constraints. It is not a separate named profile in the current configuration chart. Select the appropriate profile and prepare site-specific networking, storage, resources, and artifact delivery.
What you still own
Confirm the applications and external dependencies required at your site. A profile does not provision every external database or storage service used by those applications.
Vault is optional and disabled by its chart default. Installing a packaged component does not establish that its paid features, high availability, or recovery procedures are supported in a particular deployment.
For an installed application, use its source override objects for supported value changes. Changing the installed component set can require a package deployment as well as configuration changes.