BUG: unable to remote build kustomization

[MagnusRef]

Problem Description

Kustomization looks to be requiring the git binary if you want to reference remote kustomization inside of a flux kustomization.

Git command is not available in the addon-controller image, however it would be preferable to find a way to fix this without having to add the binary to the distroless image.

more info in slack convo:
https://projectsveltos.slack.com/archives/C046P825BBL/p1714399969297979

System Information

CLUSTERAPI VERSION: v1.6.4
SVELTOS VERSION: v1.27.0
KUBERNETES VERSION: 1.29.3

Logs

│ I0429 14:02:40.560837       1 worker.go:238] "added to result with err accumulating resources: accumulation err='accumulating resources from '../../base': '/tmp/kustomization-latest@sha256:0911cb337523b37159115 │
│ d6cd83d99672cbcb1e860813b52d848b17fd15967ab238178723/base' must resolve to a file': recursed accumulation of path '/tmp/kustomization-latest@sha256:0911cb337523b37159115d6cd83d99672cbcb1e860813b52d848b17fd15967 │
│ ab238178723/base': accumulating components: accumulateDirectory: \"recursed accumulation of path '/tmp/kustomization-latest@sha256:0911cb337523b37159115d6cd83d99672cbcb1e860813b52d848b17fd15967ab238178723/compo │
│ nents/pods-security-standards': accumulating resources: accumulation err='accumulating resources from 'https://github.com/kyverno/policies/pod-security?ref=release-1.12&timeout=120s': URL is a git repository':  │
│ no 'git' program on path: exec: \\\"git\\\": executable file not found in $PATH\"" logger="deployer" worker="8" key="erst-azure-workload:::<REDACTED-CLUSTER-NAME>:::Capi:::kyverno-policies-capi-<REDACTED-CLUSTER-NAME>:::Ku │
│ stomize:::false"                                                                                                                                                                                                   │

[gianlucam76]

Image to use is projectsveltos/addon-contoller-git:v0.30.0 (v0.30.0 is the first release where this image is available).

This image will be available in any future release. Just replace tag with future release name.