Skip piped-config volume when launcher loads config from git

[kishoredurai]

What this PR does:

Only render the piped-config ConfigMap volume and volumeMount in the piped Deployment when a local ConfigMap is actually consumed. Specifically, skip them when launcher.enabled and launcher.configFromGitRepo.enabled are both true — in that mode the launcher fetches piped config from git (via --config-from-git-repo=true and the --git-* flags) and does not read /etc/piped-config/.

Why we need it:

With launcher.enabled: true + launcher.configFromGitRepo.enabled: true, the local ConfigMap is unused. Users naturally set config.create: false in that mode, but that produces an invalid Deployment (empty configMap.name) and helm upgrade fails:

Deployment.apps "piped" is invalid:
  spec.template.spec.volumes[1].configMap.name: Required value
  spec.template.spec.containers[0].volumeMounts[1].name: Not found: "piped-config"

Which issue(s) this PR fixes:

Fixes #7140

Does this PR introduce a user-facing change?:

• How are users affected by this change: Users running the launcher with configFromGitRepo can now set config.create: false and install the chart cleanly. All other modes (piped without launcher, and launcher with a local ConfigMap) render identically to before.
• Is this breaking change: No.
• How to migrate (if breaking change): N/A.

Verification — helm template in three modes:

• Default (no launcher): piped-config volume + mount present. ✓
• launcher.enabled=true, configFromGitRepo.enabled=false: piped-config still present (launcher reads from mounted ConfigMap). ✓
• launcher.enabled=true + configFromGitRepo.enabled=true + config.create=false: piped-config absent, launcher uses --git-* flags. ✓

helm lint manifests/piped passes.

[github-actions]

👋 Hi @kishoredurai, welcome to PipeCD and thanks for opening your first pull request!

We’re really happy to have you here

Before your PR gets merged, please check a few important things below.

---

Helpful resources

• Contributing guide: https://github.com/pipe-cd/pipecd/blob/master/CONTRIBUTING.md
• Development setup: https://github.com/pipe-cd/pipecd/blob/master/CONTRIBUTING.md#development

---

DCO Sign-off

All commits must include a Signed-off-by line to comply with the Developer Certificate of Origin (DCO).

In case you forget to sign-off your commit(s), follow these steps:

For the last commit:

git commit --amend --signoff
git push --force-with-lease

For multiple commits:

git rebase --signoff origin/master
git push --force-with-lease

---

Run checks locally

Before pushing updates, please run:

make check

This runs the same checks as CI and helps catch issues early.

---

💬 Need help?

If anything is unclear, feel free to ask in this PR or join us on the CNCF Slack in the #pipecd channel.
You can get your Slack invite from: https://communityinviter.com/apps/cloud-native/cncf

Thanks for contributing to PipeCD! ❤️