Skip to content
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.

fissile changes in 5.3.0

Jump to bottom
Jan Dubois edited this page Jun 11, 2018 · 1 revision

We have made a number of changes to fissile that are not fully backwards compatible and have therefore bumped the version number to 5.3.0.

Note that SCF always pins fissile to a specific commit (similar to a submodule, but points to a pre-compiled binary), so this will not break past or future releases.

End-user visible changes

Migrated config settings in values.yaml from sizing.* to config.*

The sizing.* section in values.yaml used to contain a few general level settings in addition to per-role sizing information:

  • sizing.HA
  • sizing.cpu.*
  • sizing.memory.*

This made it difficult to programatically filter out specific values from the sizing section.

These 3 fields have now been moved to a new config.* section, leaving only role names as the top level key under sizing.

End users will have to modify their deployment scripts (or values.yaml overrides) to adjust for this name change.

See the Restructuring of the values.yaml sizing hierarchy wiki page for more details.

Developer visibile changes

These changes are not visible to the end-user, but require changes in the rolemanifest.yml file.

Active/Passive roles

We have modified the naming an definition of role tags. The new rules are described on the Pod Management using Role Manifest Tags wiki page.

KUBERNETES_CLUSTER_DOMAIN replaces KUBE_SERVICE_DOMAIN_SUFFIX

A new KUBERNETES_CLUSTER_DOMAIN builtin environment variable has been added. It makes the old KUBE_SERVICE_DOMAIN_SUFFIX variable redundant, which has been removed. It's value can now be generated using

$KUBERNETES_NAMESPACE.svc.$KUBERNETES_CLUSTER_DOMAIN

New HELM_IS_INSTALL builtin environment variable

This variable is set directly from the Release.IsInstall helm property. This way the refactored secrets generator no longer needs to use heuristics based on the presence or absence of certain kube objects if it is running an initial install or an upgrade.

This makes the secrets generator more robust, as it can now simply delete left-over config maps and secrets during a fresh install instead of throwing an error due to an inconsistent state.

Clone this wiki locally