Process for resizing the cluster

[ShurikAg]

We bootstrapped the cluster following these docs and created the fully-functioning deployment of the app. Eventually, it appeared that we need more nodes.

If I understand correctly, all I need to do is to update main.tf with more nodes and follow the same process of applying the changes. However, when I was trying to run: terraform plan -out priz_prod_cluster.out I got an error:

╷
│ Error: Error retrieving Kubernetes cluster: GET https://api.digitalocean.com/v2/kubernetes/clusters/f9883560-f07a-4e54-9520-97f3210cb47b: 401 Unable to authenticate you
│
│   with module.doks_flux_cd.digitalocean_kubernetes_cluster.primary,
│   on .terraform/modules/doks_flux_cd/create-doks-with-terraform-flux/main.tf line 39, in resource "digitalocean_kubernetes_cluster" "primary":
│   39: resource "digitalocean_kubernetes_cluster" "primary" {

Is that expected? Am I doing anything wrong?

[ShurikAg]

Looks like I had a wrong do_api_token. Fixed that, and not I am getting the following error:

│ Error: Get "http://localhost/api/v1/namespaces/flux-system": dial tcp [::1]:80: connect: connection refused
│
│   with module.doks_flux_cd.kubernetes_namespace.flux_system,
│   on .terraform/modules/doks_flux_cd/create-doks-with-terraform-flux/main.tf line 52, in resource "kubernetes_namespace" "flux_system":
│   52: resource "kubernetes_namespace" "flux_system" {

[v-ctiutiu]

Hi @ShurikAg

Thanks for submitting the issue.

Let me try to reproduce this scenario and get back to you. Thanks.

[v-ctiutiu]

Hi @ShurikAg

Sorry for the late response. I managed to reproduce your issue, and I'm currently working on a fix. Seems to be a bug in our Terraform module. Will let you know when it's ready.

Thanks.

[v-ctiutiu]

A fix is already in progress, via container-blueprints #25.

[v-ctiutiu]

@ShurikAg

Managed to fix the issue in the upstream repository (where the custom TF module is hosted). All you have to do in your existing TF workspace is this:

1. Fetch the updated TF module from the upstream repository:

   terraform get -update

2. Modify the doks_cluster_pool_node_count variable to suit your needs in the main.tf file from your workspace.

3. Create the plan:

   terraform plan -out priz_prod_cluster.out

At the end Terrraform should show you that it is going to modify the node count from the pool. Something similar to (in my tests, I changed to node count from 1 to 2):

# module.doks_flux_cd.digitalocean_kubernetes_cluster.primary will be updated in-place
  ~ resource "digitalocean_kubernetes_cluster" "primary" {
        id             = "70cbf156-9415-43ba-a7b7-4e8cdfc7dc66"
        name           = "fluxcd-demo"
        tags           = []
        # (14 unchanged attributes hidden)


      ~ node_pool {
            id                = "7131414a-05de-47b5-9396-7853ea2f3312"
            name              = "fluxcd-demo-pool"
          ~ node_count        = 1 -> 2
            tags              = []
            # (7 unchanged attributes hidden)
        }
        # (1 unchanged block hidden)
    }

Please test and let me know how it goes.

Thanks.

[bikram20]

@v-ctiutiu We should mark this as resolved since the PR is already merged.

[v-ctiutiu]

A PR containing the fix was already merged, and it was tested.

Users are encouraged to run terraform get -update, in order to update their local copy of the module.

Closing the issue as fixed.