You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved
for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Terraform Version
v1.5.7
vcd v3.12.1
Affected Resource(s)
vcd_cse_kubernetes_cluster
Terraform Configuration Files
N/A
Debug Output
N/A
Panic Output
N/A
Expected Behavior
Variable kubeconfig is flagged as a sensitive variable and is masked by terraform
Actual Behavior
terraform plan on a cluster to be destroyed output the admin kubeconfig variable
Steps to Reproduce
Rename cluster
Run terraform plan
User Access rights
N/A
Important Factoids
We are running terraform in pipelines in Gitlab so that we don't have to expose our API keys to users (gitops). However, due to this issue, anyone with access to the repository could just make an MR/PR destroying the cluster, run the pipeline which plans the destruction, and obtain the kubeconfig that provides full admin access to it.
References
N/A
The text was updated successfully, but these errors were encountered:
Hello,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved
for bug reports and feature requests. For general usage questions, please see:
https://www.terraform.io/community.html.
Terraform Version
v1.5.7
vcd v3.12.1
Affected Resource(s)
Terraform Configuration Files
N/A
Debug Output
N/A
Panic Output
N/A
Expected Behavior
kubeconfig
is flagged as a sensitive variable and is masked by terraformActual Behavior
terraform plan
on a cluster to be destroyed output the adminkubeconfig
variableSteps to Reproduce
terraform plan
User Access rights
N/A
Important Factoids
We are running terraform in pipelines in Gitlab so that we don't have to expose our API keys to users (gitops). However, due to this issue, anyone with access to the repository could just make an MR/PR destroying the cluster, run the pipeline which plans the destruction, and obtain the
kubeconfig
that provides full admin access to it.References
N/A
The text was updated successfully, but these errors were encountered: