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
Specified in the webhook.secret variable (as used in the template and the chart templates) the name of the above certificate elastic-webhook-server-cert. This also contradicts the documentation which says to use webhook.certsSecret which is not used in the helm chart templates or helpers or exist in the values.yaml file so cannot be correct.
What did you expect to see?
Chart deployed and mounted with the specified TLS certificate
What did you see instead? Under which circumstances?
Pod fails to start
Describing the deployed pod we see
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 9m57s default-scheduler Successfully assigned elastic-operator/elastic-operator-0 to kind-worker2
Warning FailedMount 3m23s (x2 over 7m55s) kubelet Unable to attach or mount volumes: unmounted volumes=[cert], unattached volumes=[kube-api-access-sshpk conf cert]: timed out waiting for the condition
Warning FailedMount 104s (x12 over 9m57s) kubelet MountVolume.SetUp failed for volume "cert" : secret "elastic-operator-webhook-cert" not found
Warning FailedMount 67s (x2 over 5m38s) kubelet Unable to attach or mount volumes: unmounted volumes=[cert], unattached volumes=[conf cert kube-api-access-sshpk]: timed out waiting for the condition
This is caused by the templates using the helper function eck-operator.webhookSecretName, which doesn't look at the actual defined values. Digging through the helper functions we can see that they completely and utterly ignore the majority of settings actually set in the values.yaml.
Environment
kind v0.22.0 go1.21.7 linux/amd64
kubernetes Server Version: v1.26.14
ECK operator chart v2.12
Kubernetes information:
$ kubectl version
Client Version: v1.30.0
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.26.14
WARNING: version difference between client (1.30) and server (1.26) exceeds the supported minor version skew of +/-1
Resource definition:
See above
Logs:
See above
If we look at the values.yaml and compare to the _helpers.tpl we see that they don't line up, and when we check the statefulset.yaml template we see it use the value from the helper and as such leads in to an incorrect configuration.
Bug Report
Issues
What did you do?
Create a Certificate that looks like this
Specified in the
webhook.secret
variable (as used in the template and the chart templates) the name of the above certificateelastic-webhook-server-cert
. This also contradicts the documentation which says to usewebhook.certsSecret
which is not used in the helm chart templates or helpers or exist in thevalues.yaml
file so cannot be correct.What did you expect to see?
Chart deployed and mounted with the specified TLS certificate
What did you see instead? Under which circumstances?
Pod fails to start
Describing the deployed pod we see
This is caused by the templates using the helper function
eck-operator.webhookSecretName
, which doesn't look at the actual defined values. Digging through the helper functions we can see that they completely and utterly ignore the majority of settings actually set in thevalues.yaml
.Environment
Resource definition:
See above
Logs:
See above
If we look at the
values.yaml
and compare to the_helpers.tpl
we see that they don't line up, and when we check thestatefulset.yaml
template we see it use the value from the helper and as such leads in to an incorrect configuration.cloud-on-k8s/deploy/eck-operator/values.yaml
Lines 121 to 143 in 233cbd0
cloud-on-k8s/deploy/eck-operator/templates/_helpers.tpl
Lines 93 to 104 in 8e283b0
cloud-on-k8s/deploy/eck-operator/templates/statefulset.yaml
Lines 65 to 68 in 8e283b0
cloud-on-k8s/deploy/eck-operator/templates/statefulset.yaml
Lines 99 to 103 in 8e283b0
cloud-on-k8s/deploy/eck-operator/templates/statefulset.yaml
Lines 142 to 151 in 8e283b0
The text was updated successfully, but these errors were encountered: