Requirement for project repository¶

The name of the project repository should consist of the following parts: <project_name>.<custom_suffix>. For example: kodjin.bootstrap.infra or kodjin.infra.
The project’s repository exists within GitLabFlow only and therefor supports the following set of static branches:
- develop
- staging
- production
Each branch corresponds to its own environment with a separately deployed K8S cluster. RMK supports these branches as well as the feature or release branches:
- A feature branch should have the following naming: feature/<issue_key>-<issue_number>-<issue_description>. For example: feature/FFS-1446-example. RMK will use <issue_key> and <issue_number> as the feature cluster name.
- A release branch should have the following naming: release/<SemVer2>-rc or release/<SemVer2> For example: release/v1.0.0. RMK will use the project name and the <SemVer2> tag as the release cluster name.

Expected repository structure:¶

etc/clusters/<provider>/<environment>/values/
  variables.auto.tfvars # Core variables for the AWS EKS cluster provider.
  worker-groups.auto.tfvars # Variables describing the resources of the AWS EKS cluster.
etc/<upstream_project_name>/<environment>/secrets/
  .sops.yaml # The public key for the current set of secrets.
  .spec.yaml.gotmpl # The secrets template for generating new or rotating current secrets.
  <release name>.yaml # Values containing release secrets for a specific environment.
etc/<upstream_project_name>/<environment>/values/
  <release name>.yaml # Values containing release configuration for a specific environment.
  <release name>.yaml.gotmpl # Values containing the release configuration for a specific environment using the Golang templates.
etc/<upstream_project_name>/<environment>/
  releases.yaml # Release specification for installation of the charts.
  globals.yaml # Set of global values within a specific scope.
  globals.yaml.gotmpl # Set of global values within a specific scope using the Golang templates.
etc/<downstream_project_name>/<environment>/secrets/
  .sops.yaml  # -//-
  .spec.yaml.gotmpl # -//-
  <release name>.yaml # -//-
etc/<downstream_project_name>/<environment>/secrets/
  <release name>.yaml # -//-
  <release name>.yaml.gotmpl # -//-
etc/<downstream_project_name>/<environment>/
  releases.yaml # -//-
  globals.yaml # - // -
  globals.yaml.gotmpl # - // -
helmfile.yaml.gotmpl # Helmfile describing the release process for specific project releases using the Golang templates.
project.yaml # Project specification for the dependencies and inventory installed via RMK.

Files for managing releases and their values at the scope level¶

Requirement for `release.yaml`¶

<release_name_foo>: # Required, release name from helmfile.yaml.gotmpl.
  enabled: true # Required, enable|disable release from helmfile.yaml.gotmpl.
  image: # Optional, needed when using a private container image with the automatic release update feature of RMK.
    repository: <full_container_images_repository_url>  
    tag: <container_images_tag>
<release_name_bar>: # -//-
  enabled: false # -//-
# ...

releases.yaml cannot be used as a template, all the values must be defined.

Requirement for `globals.yaml.gotmpl`¶

# configs - enumeration of configurations divided into sets related to the Kubernetes ConfigMaps.
configs:
  auditLog: |
    {{- readFile (printf "%s/audit-log.json" "values/configs") | nindent 4 }}
  # ...

# envs - enumeration of environment variables divided into sets related to the Kubernetes environment variables for the containers.
envs:
  # The global environment variable used by multiple releases
  FOO: false
  # ...

# hooks - enumeration of environment variables divided into sets related to the Helmfile hooks arguments.
hooks:
  <release_name>:
    common-postuninstall-hook:
      events:
         - postuninstall
      showlogs: true
      command: "{{`{{ .Release.Labels.bin }}`}}/common-postuninstall-hook.sh"
      args:
         - "{{`{{ .Release.Namespace }}`}}"
  # ...

globals.yaml.gotmpl is used in two cases:

When values, configurations or environment variables need to be declared globally for multiple releases.

When the current project is planned to be inherited by a downstream project and the overrides should be supported.

Requirement for `helmfile.yaml.gotmpl`¶

The list of the helmfile.yaml.gotmpl sections that must be defined and remained unchanged for working with RMK correctly is:

environments:
  local:
  develop:
    missingFileHandler: Warn
    values:
      - etc/<project_name>/{{ .Environment.Name }}/globals.yaml
      - etc/<project_name>/{{ .Environment.Name }}/globals.yaml.gotmpl
      - etc/<project_name>/{{ .Environment.Name }}/releases.yaml
      - {{ requiredEnv "PWD" }}/etc/<project_name>/{{ .Environment.Name }}/globals.yaml
      - {{ requiredEnv "PWD" }}/etc/<project_name>/{{ .Environment.Name }}/globals.yaml.gotmpl
      - {{ requiredEnv "PWD" }}/etc/<project_name>/{{ .Environment.Name }}/releases.yaml
  staging:
    missingFileHandler: Warn
    values:
      - etc/<project_name>/{{ .Environment.Name }}/globals.yaml
      - etc/<project_name>/{{ .Environment.Name }}/globals.yaml.gotmpl
      - etc/<project_name>/{{ .Environment.Name }}/releases.yaml
      - {{ requiredEnv "PWD" }}/etc/<project_name>/{{ .Environment.Name }}/globals.yaml
      - {{ requiredEnv "PWD" }}/etc/<project_name>/{{ .Environment.Name }}/globals.yaml.gotmpl
      - {{ requiredEnv "PWD" }}/etc/<project_name>/{{ .Environment.Name }}/releases.yaml
  production:
    missingFileHandler: Warn
    values:
      - etc/<project_name>/{{ .Environment.Name }}/globals.yaml
      - etc/<project_name>/{{ .Environment.Name }}/globals.yaml.gotmpl
      - etc/<project_name>/{{ .Environment.Name }}/releases.yaml
      - {{ requiredEnv "PWD" }}/etc/<project_name>/{{ .Environment.Name }}/globals.yaml
      - {{ requiredEnv "PWD" }}/etc/<project_name>/{{ .Environment.Name }}/globals.yaml.gotmpl
      - {{ requiredEnv "PWD" }}/etc/<project_name>/{{ .Environment.Name }}/releases.yaml
---

# The set of paths for the inherited Helmfiles is controlled through the project.yaml file using RMK.
# DO NOT EDIT the "helmfiles" field's values.
helmfiles: {{ env "HELMFILE_<project_name>_PATHS" }}

missingFileHandler: Warn

commonLabels:
  scope: <project_name>
  bin: {{ env "HELMFILE_<project_name>_HOOKS_DIR" }}/bin

templates:
  release:
    createNamespace: true
    labels:
      app: "{{`{{ .Release.Name }}`}}"
    missingFileHandler: Warn
    values:
      - etc/{{`{{ .Release.Labels.scope }}`}}/{{`{{ .Environment.Name }}`}}/values/{{`{{ .Release.Name }}`}}.yaml.gotmpl
      - etc/{{`{{ .Release.Labels.scope }}`}}/{{`{{ .Environment.Name }}`}}/values/{{`{{ .Release.Name }}`}}.yaml
      - {{ requiredEnv "PWD" }}/etc/{{`{{ .Release.Labels.scope }}`}}/{{`{{ .Environment.Name }}`}}/values/{{`{{ .Release.Name }}`}}.yaml.gotmpl
      - {{ requiredEnv "PWD" }}/etc/{{`{{ .Release.Labels.scope }}`}}/{{`{{ .Environment.Name }}`}}/values/{{`{{ .Release.Name }}`}}.yaml
    secrets:
      - {{ requiredEnv "PWD" }}/etc/{{`{{ .Release.Labels.scope }}`}}/{{`{{ .Environment.Name }}`}}/secrets/{{`{{ .Release.Name }}`}}.yaml

releases:
  - name: <release_name_foo>
    installed: {{ .Values | get (print " <release_name_foo>" ".enabled") false }}

You can use the rmk project generate command to view the full example of the contents of all the project files.

Last update: August 20, 2024

Requirement for project repository¶

Expected repository structure:¶

Files for managing releases and their values at the scope level¶

Requirement for release.yaml¶

Requirement for globals.yaml.gotmpl¶

Requirement for helmfile.yaml.gotmpl¶

Requirement for `release.yaml`¶

Requirement for `globals.yaml.gotmpl`¶

Requirement for `helmfile.yaml.gotmpl`¶