-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Describe the bug
Existing application and kubernetes manifest setup:
- Every team has one namespace where they deploy all of their applications.
- Every team has one GitOps repository where all the application manifest live after being processed by CI's of the application.
- Every team has sub-teams each sub-team manages few of the applications.
For example: This is a sample gitops repo for reference https://github.com/suryapandian/dummy-gitops-for-namespace1
Folder structure of gitops repository
<namespace-name-folder>
-application1-manifest.yaml
-application2-manifest.yaml
-application3-manifest.yaml
Given this approach we would like to create one flux-kustomization CRD for each of our application-manifest.yaml. However, flux kustomization only supports folder path for kustomization and does not support file paths.
It would be very much useful if we could add support for filepaths for kustomization CRD. It would make kustomization
Steps to reproduce
- Create kustomization crd for the file-path development/application1-manifest.yaml
- we get the error
False open /tmp/kustomization-740342244/development/application1-manifest.yaml/kustomization.yaml: not a directory
Expected behavior
We would like flux-kustomimzation crd to be able to create kustomization crd instance to accept file-path instead of always assuming a folder path.
Screenshots and recordings
No response
OS / Distro
macos 12.4
Flux version
0.30.2
Flux check
N/A
Git provider
GitHub
Container Registry provider
NA
Additional context
No response
Code of Conduct
- I agree to follow this project's Code of Conduct
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels