kustomize-controller kustomize build failed: accumulating resources: ... no such file or directory
Bug
Description
Describe the problem, what were you doing when you noticed the bug?
Provide any steps possible used to reproduce the error (ideally in an isolated fashion).
This is our initial deployment of big-bang following the steps in the template for 2.0.1. After applying the bigbang.yaml (kubectl apply -f bigbang.yaml
) we see a successfull connection to the gitrepository, but the kustomization is failing with the following error (base url redacted)
Message: kustomize build failed: accumulating resources: accumulation err='accumulating resources from '../base': read /tmp/kustomization-2774358445/base: is a directory': recursed accumulation of path '/tmp/kustomization-2774358445/base': accumulating resources: accumulation err='accumulating resources from 'git::https://<URL-REDACTED>/big-bang/bigbang.git//base?ref=2.0.1': open /tmp/kustomization-2774358445/base/git::https:/<URL-REDACTED>/big-bang/bigbang.git/base?ref=2.0.1: no such file or directory': git cmd = '/usr/bin/git fetch --depth=1 origin 2.0.1': exit status 128
Here is the contents of the dev/kustomization.yaml:
bases:
- ../base
configMapGenerator:
- name: environment
behavior: merge
files:
- values.yaml=configmap.yaml
## Comment out the next two lines below if a secrets.enc.yaml is created in this directory
#patchesStrategicMerge:
# - secrets.enc.yaml
here is the contents of the base/kustomization.yaml
bases:
- "git::https://<URL-REDACTED>/big-bang/bigbang.git//base?ref=2.0.1"
configMapGenerator:
- name: common
behavior: merge
files:
- values.yaml=configmap.yaml
patchesStrategicMerge:
- secrets.enc.yaml
that git url format is the same format we used when deploying flux:
resources:
- git::https://<URL-REDACTED>/big-bang/bigbang.git/base/flux?ref=2.0.1
images:
- name: registry1.dso.mil/ironbank/fluxcd/helm-controller
newName: <URL-REDACTED>/fluxcd/helm-controller
newTag: v0.32.1-1
- name: registry1.dso.mil/ironbank/fluxcd/kustomize-controller
newName: <URL-REDACTED>/fluxcd/kustomize-controller
newTag: v0.35.1-1
- name: registry1.dso.mil/ironbank/fluxcd/notification-controller
newName: <URL-REDACTED>/fluxcd/notification-controller
newTag: v0.33.0-1
- name: registry1.dso.mil/ironbank/fluxcd/source-controller
newName: <URL-REDACTED>/fluxcd/source-controller
newTag: v0.36.1-1
The private-git secret does exist in the bigbang namespace (this is why gitrepositories is true):
kubectl get secrets -n bigbang
NAME TYPE DATA AGE
private-git Opaque 2 24h
sops-gpg Opaque 1 24h
We are preparing for an environment that will not have access to repo1 or registry1 so all repos are cloned locally.
Any recommendations for how to troubleshoot this issue?
BigBang Version
What version of BigBang were you running? 2.0.1 (though it isn't even deployed yet :) )