-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Closed
Labels
Milestone
Description
Feature and motivation
The tls-cert-secret.yaml has limited functionality.
It only allows self signed cert generation if ingress is enabled, and tls is disabled. Alternatively, you have to pass the values of the certificate in as non-base64 literals, which causes an issue with the selenium.jks
binary.
Ideally, the helm chart would allow you to manage the secret yourself, and pass the name into a value like .Values.tls.existingSecretName
. Functionally, only seleniumGrid.tls.fullname
needs an update, and then tls-cert-secret.yaml would need an overall toggle
Usage example
To use the feature, you would manage your secret yourself, provisioning however you deem fit, for example:
./cert.sh
kubectl -n selenium-grid create secret generic ca-selenium --from-file=selenium.pem --from-file=selenium.jks --from-file=selenium.pkcs8
And use the TLS secret in Selenium Grid.
...
tls:
enabled: true
existingSecretName: "ca-selenium"
...