#1592 [Core feature] Simple templating for default annotations/labels/env vars Issue created by frsann Motivation: Why do you think this is important? At the moment it's possible to add hard-coded annotations/labels/env vars to all pods or on a task level, but there is no middle ground. There is no easy way configure the default annotations to have project or domain specific keys/values. One way of achieving this is by allowing simple templating in the default annotations/labels/env vars. (Another way would be to allow defining project/domain specific annotations, but that might serve a different use case) Goal: What should the final outcome look like, ideally? In the propeller config, you'd be able to define something like:

default-annotations:
      - annotationKey1: annotationValue1_{PROJECT}_{DOMAIN}   # -> annotationValue1_flytesnacks_development
      - key_{project}: True   # -> key_flytesnacks: True

The idea would be to use predefined variable names (

PROJECT

,

DOMAIN

, `WORKFLOW`(?) ) that are anyway readily available when creating task pods. Describe alternatives you've considered The alternative would be to allow defining project/domain specific keys/values, which would allow more fine-grain control (maybe all projects don't need the key/value defined?) but at the same time would be less flexible with regards to including new projects. It basically serves a slightly different use case. Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#1592 [Core feature] Simple templating for default annotations/labels/env vars Issue closed as not planned by github-actions[bot] flyteorg/flyte