-
### Description
## Issue
If you use the following command to create a cluster:
```
civo kubernetes create --applications "argocd,linkerd:Linkerd with Dashboard & Jaeger"
```
It works:
…
-
### Description
The current default rules are a little too permissive, allowing all ingress traffic.
```hcl
terraform {
required_providers {
civo = {
source = "civo/civo"
…
-
### Description
## Issue
Changing `kubernetes_version` after creation for civo_kubernetes_cluster does nothing
```hcl
provider "civo" {
region = "LON1"
}
data "civo_size" "xsma…
-
Hi @a1tan,
I wanna give your synchronizer a shot, but struggle a bit how to setup and use it correctly.
I did the two commands in the readme but there are no secrets created.
Some information h…
-
I have a k3s cluster that had a large node and I later added a node-pool with the ability to name. There are issues when doing the show command its panic'ing it looks like when it iterates over the na…
-
## Issue
By accident I forgot to set the default region to LON1 (default was NYC1) while specifying the region of the instance to LON1 and this is what happened when I applied this code:
```…
-
### Description
We need to validate the existence of the file and correct data structure of the token file provided by the user with `credentials_file`
It looks like [currently](https://github.com…
-
# Summary
Does declarative setup for ArgoCD already support creating new clusters using an existing secret containing a `kubeconfig` file?
If this isn't already supported: this is what I'm afte…
-
I've tried jetstack_oidc_proxy several times on different charts and have never been able to get spddy commands working.
**With the latest attempt and the latest charts and images gives me an int…
-
## Issues
Using a completely wrong `cidr_v4` causes terraform to keep trying to provision this resource for two minutes rather than failing straight away:
```hcl
resource "civo_network" "volume…