furyctl
furyctl copied to clipboard
sighupio
furyctl is the KFD (Kubernetes Fury Distribution) lifecycle manager
When create a `furyctl.yaml` file executing `furyctl create config`, there is no validation against apiVersion. E.g. As defined at [ekscluster-kfd-v1alpha2.json](https://github.com/sighupio/fury-distribution/blob/feature/furyctl-next/schemas/ekscluster-kfd-v1alpha2.json) the name of the cluster must have length beetween 1...
If I try to use a non semver value in the `--version` flag, Furyctl fails with an odd error that is not user-friendly ```console $ go run main.go create config...
This flag, maybe something like `--distro-patches` should point to a folder that contains all the files that should be replaced in the downloaded distribution
When during a download phase, something goes wrong, the downloaded cached resources can become stale. We should clean up all the cache and start again
When `--outdir` value is `.` furyctl cannot find binaries. ``` $ furyctl apply --debug --outdir . --distro-location ../../fury-distribution --dry-run DEBU logging to: .furyctl/furyctl.1713949596-73917.log DEBU Getting Home Directory Path... INFO Dry...
A flag like `--extra-phase-apply` (or a better name) could be useful when creating OnPremises cluster to re-apply the distribution phase after the plugin phase (that often contains the storage plugin)
Hi, I was experimenting with furyctl v0.27.4 and I noticed I couldn't disable the creation MinIO instances when configuring an external endpoint. Here's the snippet from my furyctl.yaml file: ```yaml...
We are caching packages and binaries on the home ~/.furyctl folder, but if we are using --outdir the `desiderata` is to have everything inside that folder. We need to change...
- chore: make GitProtocol attribute on the Downloader struct not exposed as there was no need to have it public - feat: introduce dependencies cache - feat: introduce distribution cache...
