Closed Hoon9901 closed 1 year ago
The problem was caused by formatting token-ttl=0
incorrectly.
helm provider had no problem and it was my mistake 😂
I solved it as follows
# Before
set {
name = "extraArgs"
value = "\"{--token-ttl=0}\""
}
# After
set {
name = "extraArgs"
value = "{--token-ttl=0}"
}
Describe pod kubernetes-dashboard
kubernetes-dashboard:
Container ID: docker://d4112be89500913371d8447761e41393611b47b52fabc66dbdd8f4ec378ed32d
Image: kubernetesui/dashboard:v2.5.1
Image ID: docker-pullable://kubernetesui/dashboard@sha256:cc746e7a0b1eec0db01cbabbb6386b23d7af97e79fa9e36bb883a95b7eb96fe2
Port: 8443/TCP
Host Port: 0/TCP
Args:
--namespace=kubernetes-dashboard
--auto-generate-certificates
--metrics-provider=none
**--token-ttl=0**
terraform apply
was successfully work.
Terraform, Provider, Kubernetes and Helm Versions
Affected Resource(s)
Terraform Configuration Files
versions.tf
main.tf
Debug Output
trace terraform apply
terraform apply
NOTE: In addition to Terraform debugging, please set HELM_DEBUG=1 to enable debugging info from helm.
Panic Output
Steps to Reproduce
terraform apply
Expected Behavior
should deploy success without issues
Actual Behavior
Deployment is aborted due to the following YAML parsing errors:
YAML parse error on kubernetes-dashboard/templates/deployment.yaml: error converting YAML to JSON: yaml: line 66: could not find expected ':'
Important Factoids
kubernetes-dashboard chart version has the same YAML parse error in 5.4.1 or 6.0.0 (latest) And it's the same problem when Helm provider's version is also used with 2.9.0
References
Community Note