B
Beryl Mandrill
Allow the Git fetch type (branch or tag) and version to be selected at runtime for manifests defined in a Kubernetes service.
Problem
Teams deploy lower environments from branches and production from tags. Today, the fetch type is static, making it difficult to use a single service definition across environments.
Requested Capability
  • Runtime input to choose branch or tag
  • Ability to pass the version dynamically (for example via pipeline input)
  • Optional fallback logic such as defaulting to tag, then branch if not found
Value
Enables environment-specific promotion strategies while maintaining a single reusable service definition.
Created by Gino Orvieto
·