Add rancher2_namespace_project_assignment resource

[giskou]

It would be very helpful to add a rancher2_namespace_project_assignment resource to move a namespace into a project.

For imported clusters that already have namespaces, you can't create rancher2_namespace on top of the existing ones.

[kspradheep]

+1

[gkdante]

+1

Anybody found any workaround for this? I got four K8s clusters to import with LOTS of namespaces in them.

[kspradheep]

I have used rancher cli in null_resource provisioner
`
output "cluster_id" {
value = rancher2_cluster.imported.id
}
resource "rancher2_project" "project_namespace" {
name = var.namespace
cluster_id = var.cluster_id
}

resource "null_resource" "project_namespace_assignment" {
triggers = {
policy_sha1 = "${sha1(file("${path.module}/scripts/k8s-rancher-namespace.sh"))}"
rancher_cli2json = var.rancher_cli2json
namespace = var.namespace
project_id = rancher2_project.project_namespace.id
}
provisioner "local-exec" {
command = "bash ${path.module}/scripts/k8s-rancher-namespace.sh"

environment = {
  rancher_cli2json = var.rancher_cli2json
  namespace        = var.namespace
  project_id       = rancher2_project.project_namespace.id
}

}
depends_on = [
rancher2_project.project_namespace
]
}
rancher_cli2json = base64encode(jsonencode({
Servers = {
rancherDefault = {
accessKey = local.platform_tools_secret.rancher_access_key
secretKey = local.platform_tools_secret.rancher_secret_key
tokenKey = "${local.platform_tools_secret.rancher_access_key}:${local.platform_tools_secret.rancher_secret_key}"
url = local.rancher_url
project = rancher2_cluster.imported.default_project_id
}
}
CurrentServer = "rancherDefault"
}))`

#scripts/k8s-rancher-namespace.sh
`#/bin/bash!
set -e
set -u
set -o pipefail

set -x

DIR=/tmp/$project_id
mkdir -p $DIR
FILE=$DIR/cli2.json

echo $rancher_cli2json | base64 --decode > $FILE

rancher --config $DIR namespace move $namespace $project_id

rm -rf $DIR`