You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's harder to programmatically parse yaml documents and extract markers (libraries often ignore comments)
It's not possible to write policies using tools like Open Policy Agent that check automation markers
It's harder to programmatically generate manifests (see point 1 for explanation)
Automation marker info is lost when manifests are applied to k8s. In practice this means it's impossible to expose information about automation markers via prometheus metrics or using other methods
I'd like to propose that the automation markers can be set as annotations. That way they become first class citizens in the manifest documents. They will be easy to parse programmatically, validate and expose using observability tools.
For example the following should be very easy to understand and could achieve exactly the same results as comments:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently image automation markers are configured as yaml comments, for example:
This method has some downsides:
I'd like to propose that the automation markers can be set as annotations. That way they become first class citizens in the manifest documents. They will be easy to parse programmatically, validate and expose using observability tools.
For example the following should be very easy to understand and could achieve exactly the same results as comments:
Beta Was this translation helpful? Give feedback.
All reactions