feat(chart): Enable HTTPS on distributed components #2087
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for contributing to the Docker-Selenium project!
A PR well described will help maintainers to quickly review and merge it
Before submitting your PR, please check our contributing guidelines, applied for this repository.
Avoid large PRs, help reviewers by making them as simple and short as possible.
Description
Continue the feat simplify to enable HTTPS/TLS in Selenium Grid on Kubernetes
Motivation and Context
--set isolateComponents=true
, the Router could not be up due to wait for startup probe on API/readyz
- this is fixed on upstream [java] Schema HTTPS in Distributor, SessionQueue, SessionMap selenium#13413 and will be released in4.17.0
--registration-secret
needs to be added to SessionQueue, otherwise, the client gets error 401, secret doesn't match.Types of changes
Checklist