digitalocean_kubernetes_node_pool droplets not assigned to correct digitalocean_project

[Mavwarf]

Terraform Version

Terraform v0.13.0-beta3

Affected Resource(s)

digitalocean_kubernetes_node_pool

Terraform Configuration Files

resource "digitalocean_kubernetes_cluster" "tf-kubernetes-cluster" {
  name   = "tf-${var.do_cluster_name}-k8"
  region = var.do_region

  version = "1.18.6-do.0"

  node_pool {
    name       = "tf-${var.do_cluster_name}-k8-fe-node-pool"
    size       = var.do_k8_droplet_size
    node_count = 1
    tags       = ["tf-node", "tf-front-end"]
    labels = {
      "fnx.node.type" = "public"
    }
  }
}

resource "digitalocean_project_resources" "tf-kubernetes-cluster-project-resource" {
  project   = digitalocean_project.tf-project.id
  resources = ["do:kubernetes:${digitalocean_kubernetes_cluster.tf-kubernetes-cluster.id}"]
}

resource "digitalocean_kubernetes_node_pool" "tf-kubernetes-be-node-pool" {
  cluster_id = digitalocean_kubernetes_cluster.tf-kubernetes-cluster.id

  name       = "tf-${var.do_cluster_name}-k8-be-node-pool"
  size       = var.do_k8_droplet_size
  node_count = 1
  tags       = ["tf-node", "tf-back-end"]
}

Expected Behavior

I would expect that the additional k8 node pool is also added to the k8 cluster do project, but that is not the case. All droplets created in the additional node pool are assigned to the default DO project.

Actual Behavior

The droplets created within the additional digitalocean_kubernetes_node_pool are assigned to the default DO project.

Steps to Reproduce

terraform apply

Misc

Work around is to manually assign all node pool droplets 'manually'. Problem here is, that with each terrafrom apply this is done again. If I did so once, terraform 'forgets' about that the next time I apply.

# Need to manually add all droplets of node pool to project
resource "digitalocean_project_resources" "tf-kubernetes-be-node-pool-project-resource" {
  project   = digitalocean_project.tf-project.id
  resources = formatlist("do:droplet:%s", digitalocean_kubernetes_node_pool.tf-kubernetes-be-node-pool.nodes[*].droplet_id)
}

[Mavwarf]

I noticed another, I guess relating issue, as well: if I scale the default node pool, the new droplets are not assigned to the project I assign the cluster to, but to the default project.

[Mavwarf]

Personal note: I really like and appreciate your work and your dedication! It is so super simple to use terraform with DO. Until yesterday I did everything manually with the DO UI. Using TF is so simple and 'working as expected'! I am blown away!

Stay safe! Thomas

[andrewsomething]

Hi @Mavwarf. Thanks for the kind words. Unfortunately, DigitalOcean Kubernetes clusters do not fully support projects yet. I've checked in with the team, and projects support is on the near term road map. Once this is supported in the API, your initial example will work as expected without any change on the Teraform side. Though we'll export the URN so you won't need to do the formatting.

[Mavwarf]

@andrewsomething thanks for giving an update! Looking forward to the upcoming version.

[ffuentes]

Hi @andrewsomething , it's this in the roadmap or have you any recommendation regarding projects and k8s clusters? I'm doing some testing with terraform and digitalocean and really want to structure all the associated resources in their own projects.

[devurandom]

It seems the only thing missing now, after digitalocean/godo#441 is merged, is a urn attribute for the digitalocean_kubernetes_cluster resource?

[andrewsomething]

@devurandom Clusters can now be assigned to a project, but there are still some discussions going on around how best to handle individual nodes and other associated resources in a cluster. Currently individual nodes are hidden from project details, but that is being revisited.