Which tag should be used for the OCI artifact of a configured resource?

[frewilhelm]

Description

Currently, it is unclear which tag a single layer OCI artifact, created by the configuration controller, should be tagged with.

Possible options:

• Tag of the target resource, so the configuredResource (not implemented)
• Tag of the source resource, so the resource (not implemented)
• Extra tag passed through annotations or the like

At the moment there is no way to pass the tag from the target or source resource to the configuration-controller. This would require some adjustments of the API or the content interface.

Additionally, one has to consider how to handle for example HelmCharts in OCI Artifacts that should be tagged with the HelmChart version again to be consumed by e.g. FluxCDs OCIRepository and HelmRelease.

Especially the last aspect is also relevant for the deployer, since the deployer could do some workarounds to provide meaningful tags. That is why this is a sub-task of the deployer

Done Criteria

• The single layer OCI artifact is tagged with a meaningful tag
• The e2e-tests are running with a localized and/or configured resource

[jakobmoellerdev]

This is a design question that should be answered in the Deployer ADR (#136) and not be a separate issue.

To the question: The tag of the configured and origin resource tag should align semantically. I think one could use the dns name for the tag, or even another differentiator.

Closing as such until discussed further in the ADR