| Name | Description | Type | Default | Required |
|---|---|---|---|---|
| selenium_chart_version | Selenium chart version. More info: https://github.com/helm/charts/tree/master/stable/selenium | string | 3.141.59 |
no |
| chrome_replicas | Number of selenium chrome replica | string | 1 |
no |
| firefox_replicas | Number of selenium firefox replica | string | 1 |
no |
| chrome_tag | Version of Chrome on the selenium replicas | string | latest | no |
| firefox_tag | Version of Firefox on the selenium replicas | string | latest | no |
| ui_service_type | The kubernetes service type for the UI | string | NodePort |
no |
-
Default user forbidden to perform tasks in kubernetes cluster.
I received below error when performing "terraform apply". Error: rpc error: code = Unknown desc = configmaps is forbidden: User "system:serviceaccount:kube-system:default" cannot list resource "configmaps" in API group "" in the namespace "kube-system"
Default user in kube-system namespace does not have required permissions.
To make it simple, I added cluster-admin role to default id using yaml below.
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: default
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: default
namespace: kube-system
-
Deploy does not finish.
Terraform apply shows "..still creating.." till timeout. Although the release is created and working as expected.
Helm 2 to Helm 3 migration. Terraform was creating helm 2 release. Kubernetes cluster was trying to find helm 3 release and not getting it. As a result, terraform was thinking release is not yet created and never finishing.
Follow instructions mentioned in below pages. Converting releases and cleaning up configuration willbe required. https://github.com/helm/helm-2to3 https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
-
Helm list does not show release.
helm list does not show release althogh release is deployed and pods are working.
Same as point 2.
Same as point 2.
-
Cluster out of resource.
Terraform is trying to created pods, but pods are throwing below error. 2 Insufficient cpu, 2 Insufficient memory.
Cluster has limited memory and cpu. By default, chart tries to craete with .5 cpu and 500 MiB memory. Multiple of these may exhaust cluster.
Add resource limit.