Add custom packs

Custom packs are built by users and deployed to custom registries using the Spectro Cloud CLI tool.

Steps to create a custom pack

  1. Create a directory with a suitable name for all the pack contents.

    Example: prometheus_1_0

  1. Create a metadata file named pack.json to describe the pack.


    "annotations": {
    "name": "value"
    "ansibleRoles": [],
    "displayName": "<PACK_DISPLAY_NAME>",
    "eol": "2028-04-30",
    "group": "<PACK_GROUP>",
    "kubeManifests": [
    "layer": "<LAYER>",
    "name": "<PACK_NAME>",
    "version": "<PACK_VERSION>"

    An explanation for the parameters of the JSON is given in the table below:

    Property NameData typeRequiredDescription
    nameStringTrueName of the pack
    displayNameStringTrueName of the pack as it is to be displayed on the Palette management console.
    layerStringTrueRelevant layer that this pack should be part of; such as os, k8s, cni, csi, addon
    addonTypeStringFalseAddon-type must be set for packs that have the layer set to Addon. The value must be one of the following: logging, monitoring, load balancer, authentication, ingress, security. Setting a relevant correct addon type ensures packs are organized correctly on the management console making it easy for profile authors to find packs.
    versionStringTrueA Semantic version for the pack. It is recommended that the pack version be the same as the underlying integration it is being created for. For example, the version for the pack that will install Prometheus 2.3.4, should set to 2.3.4.
    cloudTypesArrayTrueSupported cloud types are AWS, Azure, VMware. One or more types can be provided for a pack.
    groupStringFalseOptional categorization of packs. For example, LTS can be set for Ubuntu OS packs.
    annotationsArrayFalseOptional key-value pairs required during pack installation. Typically, custom packs do not need to set annotations. Some packs like the ones for OS require annotations that need to be set with an image id.
    eolStringFalseEnd of life date for integration.
    KubeManifestsArrayFalseRelative path to Kubernetes manifest yaml files.
    ansibleRolesArrayFalseRelative part to the Ansible role folders. These folders should contain all the artifacts required by Ansible. Please refer to the Ansible documentation for more details on how Ansible roles are constructed.
    In Palette, Ansible roles are used to customize the OS image used for cluster nodes. Typically, these are roles that perform tasks like hardening the OS, installing monitoring agents, etc.
    chartsArrayFalseRelative path to the helm chart archives.
  2. Create a file named values.yaml. This file consists of configurable parameters that need to be exposed to the end-users during the creation of a cluster profile.

    Parameters for all charts, manifests, and Ansible roles defined in the pack are defined in this file.

    Helm charts natively support values override. Any values defined are merged with those defined within a chart.

    Manifests and Ansible roles need to be explicitly templatized if parameter configuration is desired.

    namespace : <default namespace for charts and manifests>
    <configurable chart1 parameters>
    <configurable chart2 parameters>
    <templatized manifest1 parameters>
    <templatized manifest2 parameters>
    <templatized role1 parameters>
    <templatized role2 parameters>
  3. A pack must have the logo file named logo.png and must be copied into the pack directory.

  1. Login to the pack registry using the following command:

    spectro registry login [REGISTRY_SERVER]
  2. Push the newly defined pack to the pack registry using the following command:

    spectro pack push [PACK_DIR_LOCATION] --registry-server [REGISTRY_SERVER]
  3. To overwrite contents of a previously deployed pack, use the force option as follows:

    spectro pack push [PACK_DIR_LOCATION] -f --registry-server [REGISTRY_SERVER]

Adding an OS Pack

The OS is one of the Core Layers in a cluster profile. An OS pack can be built to use a custom OS image for cluster nodes. This might be desirable if an organization wants to use an approved hardened OS image for their infrastructure. There are typically the following two scenarios for the OS image:

  1. Pre-Installed Kubernetes - The OS image has the desired version of Kubernetes components like kubelet, kubectl, etc installed.
  1. Vanilla OS Image - Kubernetes components are not installed.

Additionally, for both scenarios additional components or packages may need to be installed at runtime to prepare the final OS image. This can be done by specifying one or more Ansible roles in the pack. The following are a few examples of building custom OS pack to cover the some of these scenarios.

A few sample pack manifests for building a custom OS pack are shown in the following examples. These are examples for images that do not have Kubernetes components pre-installed. Palette installs these components at the time of provisioning. The version of Kubernetes that gets installed depends on the Kubernetes pack configuration in the cluster profile. If Kubernetes is pre-installed in the image, set the flag skipK8sInstall to true.


AWS Custom-OS Pack

"annotations": {
"cloudRegion": "us-east-1",
"imageId": "ami-071f6fc516c53fca1",
"imageOwner": "421085264799",
"osName": "centos",
"os_spectro_version": "0",
"sshUsername": "centos",
"skipK8sInstall": "false"
"ansibleRoles": [
"cloudTypes": ["aws"],
"displayName": "CentOS",
"eol": "2024-06-30",
"group": "",
"kubeManifests": [],
"layer": "os",
"name": "golden-centos-aws",
"version": "7.7.1908"

Ansible Roles

In all the examples above, additional customization in the form of an Ansible role called harden_os is specified in the pack manifest. The tasks and other files for the implementation of this role need to be included in the pack. The final directory structure of for the pack would be as follows:


Ansible roles are optional and only required if additional runtime customization is required. Once an OS pack is constructed, push it to the pack registry using the Spectro CLI tool.

A values.yaml file is mandatory for every pack. For an OS pack, there are typically no configurable parameters, but an empty file still needs to be added to the OS pack.

During the image customization phase of a cluster deployment, failures related to missing packages or package version mismatch could occur when using a custom OS pack. These errors are presented on the console. The image needs to be updated to resolve any such issues.