-
## Description
When there is no node in the node pool in the cluster, when we scale that node pool using Civo CLI, it's giving the error.
This functionality is working fine in the UI.
## Steps to…
-
**Description**
When creating instances, the region flag is not respected.
**Reproducing**
1. Switch to a region where the diskimage isn't available (in this case phx1)
$ civo region curre…
-
Terraform apply times out when using the default L40s node in **LON1**. The node seems 🟢 but the v1.27 Talos cluster itself never becomes available enough to pull the kube.config to troubleshoot furt…
-
### Which version of kubefirst are you using?
v2.3.5
### Which cloud provider?
Civo
### Which DNS?
Cloud ones (default)
### Which installation type?
CLI
### Which distributed Git provider?
Gi…
-
**Background:**
Currently, the CLI uses the `github.com/gookit/color` library to handle colored output in the console. While this library does its job well, it introduces an additional dependency t…
-
### Which version of kubefirst are you using?
2.4.11
### Which cloud provider?
Akamai, AWS, Civo, DigitalOcean, Google Cloud, K3s, Vultr
### Which DNS?
None specific
### Which installation type?…
-
### What is your feature idea?
The `kubefirst` CLI already offers a way to validate the user's quota in CIVO. Also, I presume there is a way to retrieve the node details via API based on the output o…
-
This issue is a:
* [x] Bug Report
* [ ] Enhancement suggestion
* [ ] Feature request
If the issue concerns an existing Marketplace application, please tag the maintainer of the application (foun…
-
### Which version of kubefirst are you using?
2.2.2
### Which cloud provider?
Civo
### Which installation type?
CLI
### Which distributed Git provider?
GitHub
### What is the issue?
Deploying…
-
## Description
Currently, there is no way of testing CLI commands (except by building the local binary and running the commands manually). We need a test suite for CLI in the same way we have one f…