-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🚀 Feature]: Manage TLS Certificate Externally #2293
Comments
@declan-fitzpatrick, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
In part of this, I am doing the refactoring on helm chart config keys to enable TLS ingress only or the secure connection in both server and ingress in front |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
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, onlyseleniumGrid.tls.fullname
needs an update, and then tls-cert-secret.yaml would need an overall toggleUsage example
To use the feature, you would manage your secret yourself, provisioning however you deem fit, for example:
And use the TLS secret in Selenium Grid.
The text was updated successfully, but these errors were encountered: