Use flux build internally for building fluxtomizations
#390
Comments
allenporter
added a commit
that referenced
this issue
Nov 20, 2023
Add flux dependency in development environment to prepare for calling `flux build` Issue #390
This was referenced Nov 20, 2023
Merged
allenporter
added a commit
that referenced
this issue
Nov 22, 2023
allenporter
added a commit
that referenced
this issue
Nov 22, 2023
allenporter
added a commit
that referenced
this issue
Nov 23, 2023
Remove support for multiple clusters in a single path This is a breaking change that removes the `name` and `namespace` fields from the `Cluster` object so they no longer act like fake kustomizations. Issue #390
allenporter
added a commit
that referenced
this issue
Nov 23, 2023
allenporter
added a commit
that referenced
this issue
Dec 17, 2023
Use `flux build ks` when building fluxtomizations, and remove all use
`kustomize build` as well as implicit kustomization file generation. Add
additional test coverage for a couple clusters to verify the build
output is reasonable.
This requires setting up the flux CLI in github actions:
```
- name: Setup Flux CLI
uses: fluxcd/flux2/action@v2.1.2
```
Breaking change: The python APIs for using `kustomize build` have been
removed.
Issue #390
allenporter
added a commit
that referenced
this issue
Dec 17, 2023
Update documentation examples to include flux cli Issue #390
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A command like this:
$ flux build ks cluster-apps-kubernetes-dashboard --path tests/testdata/cluster2/apps/monitoring/kubernetes-dashboard/app --dry-run --kustomization-file tests/testdata/cluster2/apps/monitoring/kubernetes-dashboard/ks.yamlcan be used to build fluxtomizations rather than having them home grown and can better support flux features.
The text was updated successfully, but these errors were encountered: