The Argo CD "repo server" component is in charge of building Kubernetes manifests based on some source files from a Helm, OCI, or git repository. When a config management plugin is correctly configured, the repo server may delegate the task of building manifests to the plugin.

mikutas

3つのステップ

Write the plugin configuration file

以下の理由で-qをつける

The generate command runs in the Application source directory each time manifests are generated. Standard output must be ONLY valid Kubernetes Objects in either YAML or JSON. A non-zero exit code will fail manifest generation.
To write log messages from the command, write them to stderr, it will always be displayed.
Error output will be sent to the UI, so avoid printing sensitive information (such as secrets).

プラグインなしでHelmチャートを処理する場合--include-crdsはデフォルトでtrueであるため（またAppのspecでskipCrdsも使わないため）--include-crdsもつける

mikutas

Place the plugin configuration file in the sidecar

↑のvaluesで作られるConfigMapをvolumeに

volumeをvolume mount

mikutas

Register the plugin sidecar

To install a plugin, patch argocd-repo-server to run the plugin container as a sidecar, with argocd-cmp-server as its entrypoint. You can use either off-the-shelf or custom-built plugin image as sidecar image.

サイドカーにはhelmfileイメージを使う
helmfile / helm-diff / helm-git / helm-s3 / helm-secretsが最初から入っている

argocd-cmp-server as its entrypoint

repo-serverにもともと存在するinit containerでvar-files volumeにバイナリをコピーしている

なので、extra containerにvar-filesをマウントすると、

そこに置いてあるargocd-cmp-serverを起動できる