Skip to content
FLOW PlatformFLOW Platform

Namespace strategy

When using the pipelines, we implement a strategy for what namespaces to use for what purpose. For instance a static namespace for testing can be introduced where cleaning is disabled. Another use case can be having “sticky” namespaces for main/develop/epic branches and dynamic namespace for all other branches.

For our projects, the gitflow is used, meaning we choose the following strategy:

  • Protected branches (like main and develop) are build as “sticky” namespaces, meaning they remain on the cluster and the images are not cleaned by the pipeline.
  • All other branches (like feature/*) are build as dynamic namespaces, meaning they are cleaned after a successful deployment by the pipeline.