Building a configMap from a remote file stored in a repo included as GitRepository.spec.include

[rcarre]

Dear community,
I am struggling to build a configMap from a file sourceFile.yaml stored in repo#1. This Gitrepository repo#1 is included in GitRepository repo#2

False   kustomize build failed: loading KV pairs: file sources: [sourceFile.yaml=source/sourceFile.yaml]: open /tmp/kustomization-2548788575/overlays/myoverlay/ssource/sourceFile.yaml: no such file or directory

Here is the kustomization.yaml file stored in repo#2 under directory overlays/myoverlay

---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

generatorOptions:
  disableNameSuffixHash: true

configMapGenerator:
  - files:
      - sourceFile.yaml=source/sourceFile.yaml
    name: sourcefile
    namespace: mynamespace

---
apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata:
  name: repo#1
  namespace: mynamespace
spec:
  interval: 15m
  ref:
    branch: main
  secretRef:
    name: mysecret
  url: https://myurl/repo1.git

---
apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata:
  name: repo#2
  namespace: mynamespace
spec:
  include:
      repository:
        name: repo#1
      toPath: overlays/myoverlay/source
  interval: 15m
  ref:
    branch: main
  secretRef:
    name: mysecret
  url: https://myurl/repo2.git

[rcarre]

I actually managed it. However, this is a solution not easy to maintain due to complexity.

[mayank-khullar]

@rcarre Heyy I am trying to solve the same problem , where i want to create a configmap from remote repo and read the values before applying the helm release...

could you please let me know how you cracked it

[rcarre]

In you current repo#2, you need to:

• setup a CR FluxGitRepo#1 pointing to repo#1 hosting the yaml file used to build up the configMap
• setup an extra CR FluxGitRepo#3 aggregating CR FluxGitRepo#2 and CR FluxGitRepo#1 with toPath set to yaml file path
• then setup a CR Flux Kustomization associated to CR FluxGitRepo#3 with path pointing to the kustomize.config.k8s.io/v1beta1 kustomization manifest depicted her above