Use unique user name in kubeconfig files for k3s and rke2 (#70)

Using unique names allows multiple kubeconfigs to be specified in
KUBECONFIG or merged into single kubeconfig file.

```
KUBECONFIG="$PWD/upstream.yaml:$PWD/downstream-0-0.yaml"
kubectl config view --flatten --raw > kubeconfig-all.yaml
```

Apparently the user name has no connection to the common name in the
certificate.

Co-authored-by: Mario Manno <mario.manno@suse.com>
This commit is contained in:
Mario Manno 2025-06-06 16:58:47 +02:00 committed by GitHub
parent 1cfd271de7
commit ef1758f93f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 4 additions and 4 deletions

View File

@ -192,7 +192,7 @@ resource "local_file" "kubeconfig" {
{
context = {
cluster = var.name
user : "master-user"
user = "admin@${var.name}"
}
name = var.name
}
@ -206,7 +206,7 @@ resource "local_file" "kubeconfig" {
client-certificate-data : base64encode(tls_locally_signed_cert.master_user.cert_pem)
client-key-data : base64encode(tls_private_key.master_user.private_key_pem)
}
name : "master-user"
name = "admin@${var.name}"
}
]
})

View File

@ -186,7 +186,7 @@ resource "local_file" "kubeconfig" {
{
context = {
cluster = var.name
user : "master-user"
user = "admin@${var.name}"
}
name = var.name
}
@ -200,7 +200,7 @@ resource "local_file" "kubeconfig" {
client-certificate-data : base64encode(tls_locally_signed_cert.master_user.cert_pem)
client-key-data : base64encode(tls_private_key.master_user.private_key_pem)
}
name : "master-user"
name = "admin@${var.name}"
}
]
})