[FEAT] - Use flux helm release to template Plugin manifest for container image replacement

[uwe-mayer]

Priority

(Low) Something is a little off

User Story

When running the local environment we want to enable the container image overwriting/mirroring with the local registry

Description

Currently the Plugin controller pulls a helm release from it's repository to find and replace any mirrored container images. With flux the HelmRelease is already present in-cluster. We do not need to make the external call.

Acceptance Criteria

• Helm release used to template the manifest to filter mirrored container images is pulled from the in-cluster flux HelmRelease resource
• All tests stay green, this should just be an internal refactoring

Reference Issues

No response

[IvoGoman]

@uwe-mayer @abhijith-darshan is this still relevant when using zot for testing/ local kind environment?

[abhijith-darshan]

@uwe-mayer @abhijith-darshan is this still relevant when using zot for testing/ local kind environment?

local registry is out of the picture when working directly with flux artifcats in-cluster

Making flux work with local registry is already completed.

With this greenhouse controller's dependency on registry to pull helm charts can be eliminated.